Pino Toscano, le Fri 26 Oct 2012 18:30:39 +0200, a écrit : > Alle venerdì 26 ottobre 2012, Samuel Thibault ha scritto: > > Svante Signell, le Fri 26 Oct 2012 08:03:43 +0200, a écrit : > > > On Thu, 2012-10-25 at 19:47 +0200, Samuel Thibault wrote: > > > > Roland McGrath, le Thu 25 Oct 2012 09:49:51 -0700, a écrit : > > > > > We don't generally handle MIG_BAD_ID. That error indicates a > > > > > server not implementing the protocol for which it's being > > > > > used, which is a server bug. > > > > > > > > Pino, in which case did you actually get MIG_BAD_ID precisely? > > with sample.c: > int main() > { > fsync(STDOUT_FILENO) > } > $ ./sample | less
Oh? I wonder how that produces MIG_BAD_ID: libtrivfs (used by pflocal) is supposed to be returning EOPNOTSUPP when there is no underlying node, which should be the case here. > > (even if it's probably not right in going crazy if it doesn't return > > EINVAL). > > Well, one could note throwing an error value which is not even a POSIX > errno does not sound correct to send to userland. AIUI, POSIX says there can be other, implementation-defined errors. Samuel