Date: Thu, 7 Sep 1995 17:08:50 +0100 (BST) From: Paul Richards <paul@netcraft.co.uk> To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Subject: syslogd nasty bug Message-ID: <199509071608.RAA07936@server.netcraft.co.uk>
next in thread | raw e-mail | index | archive | help
syslogd has a very nasty feature, if you use the -p option to specify an alternate local domain socket it unlinks the filename. A really good way to screw things completely is to do syslogd -p . and be in some important directory. It also unlinks the file on a fatal exit too which can be just as serious. Is there any purpose to these unlink's? Just commenting out the first one does what I'd expect, i.e if the file already exists it'll abort when it fails to create the socket. Perhaps what it should do is skip the local domain socket and continue which is what it does for the internet socket. I guess the second unlink is to clean up if it created the socket but if the socket creation failed, i.e. the filename already existed, then the unlink at exit will clobber the filename again. Anyway, DON'T USE -p with syslogd until this gets fixed. Screwed myself badly finding this little bug. -- Paul Richards, Bluebird Computer Systems. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509071608.RAA07936>