Date: Mon, 7 Jul 2003 10:50:05 -0700 (PDT) From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/11294: direct logging to other hosts (no local syslogd) Message-ID: <200307071750.h67Ho5xh030746@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/11294; it has been noted by GNATS.
From: Mikhail Teterin <mi+mx@aldan.algebra.com>
To: Marc Perisa <Marc.Perisa@networker-gmbh.de>,
freebsd-gnats-submit@FreeBSD.org, mi@aldan.algebra.com
Cc:
Subject: Re: bin/11294: direct logging to other hosts (no local syslogd)
Date: Mon, 7 Jul 2003 13:42:04 -0400
=the propossed change to logger(1) was done in version 1.6 for
=5-CURRENT. It is not yet in 4-STABLE.
=The calls for syslog(3) et al weren't updated.
=Is it still needed to send log information to a remote host without
=syslogd locally running?
My reasoning was that since the functionality will be present in the
system anyway, it would be better to place it into a library, from where
it can be used by other programs. This would benefit systems running in
embedded installations, which would prefer not to run the whole syslog
of their own, as well as others...
Locking the functionality inside a utility, while seemingly trying to
keep the libc cleaner, will only encourage ugliness like system("logger
...") :-\
-mi
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307071750.h67Ho5xh030746>