On Fri, Nov 15, 2013 at 11:22:59AM +0100, David Herrmann wrote: > Syscalls may fail for a lot of reasons, but most times these errors are > unexpected (we cannot recover). Especially when dealing with device nodes > that can be revoked asynchronously, a series of syscalls may start failing > at any point. Normally, we can silently ignore errors and just bail out, > but for debugging purposes log messages are quite helpful. I'm not sold of the idea of completely generic message. If I'm sitting in front of a failed boot, seeing only "Syscall failed unexpectedly: no such file or directory", I'm going to be pretty frustrated. Maybe there should be a custom message argument like "ioctl AUTOFS_DEV_IOCTL_VERSION". This isn't going to increase the footprint too much, but will help undertand bug reprots. Or if you thyink it's too annoying to write, than maybe just print the file name and line automatically.
Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
