Date: Thu, 22 Feb 2001 18:37:55 +0200 (EET) From: diman <diman@asd-g.com> To: mouss <usebsd@free.fr> Cc: diwil@eis.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: warning in free(): Message-ID: <Pine.BSF.4.21.0102221832130.322-100000@portal.none.ua> In-Reply-To: <4.3.0.20010222164121.0594c510@pop.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Feb 2001, mouss wrote: > Now having free() write to stdout/stderr isn't necessarily a good thing > for daemons. If the message goes through a socket, it'll be hard to > debug, which was the original intent. > > I suggest having some way so that when a program becomes a daemon, > it can set some "silent-libc" or "libc messages go to logs" instead of > using stdout/stderr. > > Wouldn't it not be cool if err() and warn() had the capability of using syslog > instead of a file or std* when needed. err_set_file allows one to use a file > instead. How about allowing the use of syslog? Open AF_UNIX socket to syslogd and then use err_set_file() to redirect all err/warn messages to syslogd instead of stdin/stdout. That should help you debug daemons. Best Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0102221832130.322-100000>