From: Ben Collins <bcollins@debian.org>
To: Steven Micallef <steven.micallef@world.net>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: chroot() breaks syslog() ?
Date: Mon, 4 Aug 2003 01:19:27 -0400 [thread overview]
Message-ID: <20030804051927.GA31092@phunnypharm.org> (raw)
In-Reply-To: <6416776FCC55D511BC4E0090274EFEF5080024A9@exchange.world.net>
> 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/
next prev parent reply other threads:[~2003-08-04 5:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 5:27 chroot() breaks syslog() ? Steven Micallef
2003-08-04 5:19 ` Ben Collins [this message]
2003-08-04 7:23 ` Torsten Foertsch
2003-08-04 5:49 Steven Micallef
2003-08-04 5:34 ` Ben Collins
2003-08-04 6:12 ` David Lang
2003-08-04 8:40 ` Wichert Akkerman
2003-08-04 13:33 ` Herbert Pötzl
2003-08-04 20:19 ` Olaf Titz
2003-08-04 7:30 Steven Micallef
2003-08-06 8:42 Oliver Pitzeier
2003-08-06 11:08 ` Herbert Pötzl
2003-08-06 13:34 Oliver Pitzeier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030804051927.GA31092@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.micallef@world.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).