[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: active translators stdout/stderr

From: Ludovic Courtès
Subject: Re: active translators stdout/stderr
Date: Mon, 22 Feb 2016 00:05:02 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Richard Braun <rbraun@sceen.net> skribis:

> On Sun, Feb 14, 2016 at 10:09:37PM +0100, Samuel Thibault wrote:
>> Hello,
>> We have various issues with the active translators' stdout/stderr:
>> - When mounting /proc from /etc/init.d/rc, stdout/stderr is closed, and
>>   thus as soon as e.g. mtab reports a warning, it gets SIGLOST and dies.
>> - When mounting the cdrom image from debian installer scripts, the
>>   script is not considered finished since the isofs translator is still
>>   running and possibly emitting output.
>> So, what should we do about stdout/stderr output?  Do we require their
>> output to be explicitly redirected by callers of mount and settrans?
>> In the mount case, people used to Linux will not think of doing it, so
>> perhaps we need it to do it for the user?
> I think we could have a default log server for that. We could make it
> a gsoc project. It should make a good entry project.

In the meantime I suppose /dev/null would make for a good log server,
and it’s presumably a simple fix?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]