Svante Signell, le Wed 07 Nov 2012 16:26:50 +0100, a écrit :
> On Wed, 2012-11-07 at 16:11 +0100, Samuel Thibault wrote:
> > Svante Signell, le Wed 07 Nov 2012 08:46:36 +0100, a écrit :
> > > #> ps -feM|grep pflocal
> > > root 9 3 0:02.69 /hurd/pflocal
> > > root 881 1 0:00.01 /hurd/pflocal.new
> >
> > btw, the ppid of pflocal.new is 1, which is init, not 3, so it has not
> > been started by the root ext2fs, or at least not the one currently
> > running. So either your root ext2fs has died at some point during
> > boot, or you have another ext2 filesystem from which pflocal.new gets
> > triggered by a passive translator record, and the ext2fs running that
> > filesystem somehow got down, but leaving the pflocal.new running.
>
> Thanks, I have now killed that process and rebooted, and only the one
> at /hurd/pflocal remains, so it seemed to be an active one. Now the
> problem is that even if using the printf-modified pflocal (stdout),
> nothing is printed. Maybe I have to do as Richard proposed, write the
> output to a file instead.
That'd be more sure. Where are you looking at? passive translators have
at best their output sent to the mach console, *not* the stdout of where
you run programs using them (even if that's what triggered their start).
And you have to flush the output stream, even if it's stderr.
> A question regarding the server-client code of the translators: Is there
> an easy way to find out what is server code and what is client code?
S_foobar () {} function definition is server code and foobar() call is
client code. Just like the former is the implementation of a function,
and the latter is the caller of the function.
Samuel
