Re: chroot() breaks syslog() ?

From: Ben Collins (bcollins@debian.org)
Date: Mon Aug 04 2003 - 00:19:27 EST

Next message: Brandon Stewart: "Hang after "Freeing unused kernel memory" with 2.6 test2"
Previous message: Steve French: "Re: do_div considered harmful"
In reply to: Steven Micallef: "chroot() breaks syslog() ?"
Next in thread: Steven Micallef: "RE: chroot() breaks syslog() ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

Next message: Brandon Stewart: "Hang after "Freeing unused kernel memory" with 2.6 test2"
Previous message: Steve French: "Re: do_div considered harmful"
In reply to: Steven Micallef: "chroot() breaks syslog() ?"
Next in thread: Steven Micallef: "RE: chroot() breaks syslog() ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:22 EST