Date: Thu, 22 Feb 2001 19:54:54 +0100 From: mouss <usebsd@free.fr> To: diman <diman@asd-g.com> Cc: diwil@eis.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: warning in free(): Message-ID: <4.3.0.20010222194459.0242d850@pop.free.fr> In-Reply-To: <Pine.BSF.4.21.0102221832130.322-100000@portal.none.ua> References: <4.3.0.20010222164121.0594c510@pop.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
At 18:37 22/02/01 +0200, diman wrote: >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. I agree, but one of the nice things about syslog interface is that it hides all the socket/device stuff. so getting back to the socket api is somewhat unsatisfactory. Also, I think having this directly in err() and warn() and friends would be more elegant. and this doesn't seem hard to do. something like using a function pointer to use fprintf or syslog, and an additionnal void* to use either err_file or syslog priority. Does this sound ok or is it an unuseful complication of code? cheers, mouss 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?4.3.0.20010222194459.0242d850>