Date: Tue, 08 Apr 2003 18:13:27 -0400 From: Christopher Nehren <apeiron@comcast.net> To: freebsd-questions@freebsd.org Subject: Return values of the syslog(3) family Message-ID: <1049840007.685.79.camel@prophecy.dyndns.org>
next in thread | raw e-mail | index | archive | help
--=-PXfHlY7Jpsvguk0lsGrK Content-Type: text/plain Content-Transfer-Encoding: quoted-printable ... or rather, lack thereof. I'm not quite sure whom to ask about this, so please redirect me if this isn't the appropriate forum. I've looked at the prototypes of various BSD and Linux systems' syslog(3) calls, and they all have 'void' as the return type. Now, logically, since a log file is being written, wouldn't it be nice to know whether that call executed successfully? Yes, I've already thought of the "If you can't write to syslog, then you have larger problems than this" ... but how would one -know- they have these problems? I admit that I'm probably missing something about the Nature of Programming; but at least to this newbie, it seems like it defeats part of the point of calling the functions in the first place. TIA for any information about this. --=-PXfHlY7Jpsvguk0lsGrK Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+k0mHUdqurN0fljsRAietAKC/KvFYouiEKnnJ/GJ4Fi0O+DBN1ACeIuka ZwXDs0Ck6rxrO28Mgaszw3Q= =v7YY -----END PGP SIGNATURE----- --=-PXfHlY7Jpsvguk0lsGrK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1049840007.685.79.camel>