Re: Boot Messages
On Sat, Apr 13, 2002 at 07:16:44AM -0700, Kenneth Stailey wrote:
> IIRC syslogd doesn't read from files, you use logger(1) to send files or stdout
> to syslogd. Trouble is that I can't get logger(1) to generate any messages.
The inetutils syslogd does read from the kernel log device by default.
That is, if it can find it. As we don't specify the klog path in
syslog.h, you probably need to make sure you have /dev/klog before you
configure inetutils. Then syslogd --help should show you the correct
path in the --no-klog option (which you should not use of course :)
If you don't see such an option at all, detection of PATH_KLOG failed.
> from a startup script. I'll see about getting any updates from alpha.gnu.org.
Unfortunately, there is no recent snapshot, please take the version from
CVS (either the head or the 1.4 branch). It's still time to fix any
specific small problem with it for the 1.4 release (eh, I hope ;), so it
would be cool if you could test it before that happens.
There is no need to play with logger, nor do we need a klogd like you
need for the sysklogd set of programs (they removed the support for
reading from a kernel log device directly, if I remember correctly,
while our code is closer to the original BSD code in this regard. In
fact, I merged the BSD code and the main features in the sysklogd suite
for inetutils).
Thanks,
Marcus
--
To UNSUBSCRIBE, email to debian-hurd-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: