Messages in this thread | | | Date | Mon, 4 Aug 2003 01:19:27 -0400 | From | Ben Collins <> | Subject | Re: chroot() breaks syslog() ? |
| |
> connect(3, {sin_family=AF_UNIX, path="/dev/log"}, 16) = -1 ENOENT (No such > file or directory) > > Is this intentional? If so, is there a work-around? I discovered this when > debugging 'rwhod', but I imagine there are many more utils that would be > affected too.
I don't know how it ever did work, if in fact it did for you. /dev/log is not a kernel device, it's just a normal socket created by syslogd.
Now, if you use devfs, and mount devfs under the chroot, it magically propogates /dev/log. But that's not the normal thing.
-- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |