From owner-freebsd-bugs@FreeBSD.ORG Mon Jul 7 10:50:11 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3820437B40B for ; Mon, 7 Jul 2003 10:50:11 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28A3B43FA3 for ; Mon, 7 Jul 2003 10:50:08 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h67Ho5Up030747 for ; Mon, 7 Jul 2003 10:50:05 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h67Ho5xh030746; Mon, 7 Jul 2003 10:50:05 -0700 (PDT) Date: Mon, 7 Jul 2003 10:50:05 -0700 (PDT) Message-Id: <200307071750.h67Ho5xh030746@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mikhail Teterin Subject: Re: bin/11294: direct logging to other hosts (no local syslogd) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mikhail Teterin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 17:50:11 -0000 The following reply was made to PR bin/11294; it has been noted by GNATS. From: Mikhail Teterin To: Marc Perisa , 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