Messages in this thread | | | From | Steven Micallef <> | Subject | RE: chroot() breaks syslog() ? | Date | Mon, 4 Aug 2003 15:49:48 +1000 |
| |
You're right - my mistake, it doesn't actually work on 2.4.8 either, I think I was looking at the wrong thing when I thought it was actually working.
Is it worth considering (optionally) making /dev available to chroot()'ed environments, or would that just defeat the whole purpose of chroot()?
Regards,
Steve.
> -----Original Message----- > From: Ben Collins [mailto:bcollins@debian.org] > Sent: Monday, 4 August 2003 3:19 PM > To: Steven Micallef > Cc: 'linux-kernel@vger.kernel.org' > 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/ > __________ Information from NOD32 1.449 (20030630) __________ > > This message was checked by NOD32 for Exchange e-mail monitor. > http://www.nod32.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/
| |