[Top][All Lists]

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

Re: active translators stdout/stderr

From: Justus Winter
Subject: Re: active translators stdout/stderr
Date: Mon, 15 Feb 2016 11:56:24 +0100
User-agent: alot/0.3.8.dev

Hi ;)

Quoting Samuel Thibault (2016-02-14 22:09:37)
> 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.

eww :(

> - 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.

I'm not sure I understand.  How is that related to stdout/err?

> 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?

Maybe we can have /servers/log, that all servers can open, issue
something like log_get_file (log, "mtab[23]", &file), then install
file as stdout/err (if those were !MACH_PORT_VALID).  Any line that is
sent to file is then prefixed and sent somewhere, maybe to syslog, or
to the Mach console.


reply via email to

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