Date: Wed, 7 Aug 1996 13:35:45 +0000 (GMT) From: Gabor Zahemszky <zgabor@CoDe.hu> To: freebsd-questions@freebsd.org Cc: richardc@csua.berkeley.edu Subject: Re: tcpwrapper logs Message-ID: <199608071335.NAA01627@CoDe.CoDe.hu> In-Reply-To: <Pine.PTX.3.95.960807021618.17642C-100000@soda.CSUA.Berkeley.EDU> from "Veggy Vinny" at Aug 7, 96 02:17:40 am
next in thread | previous in thread | raw e-mail | index | archive | help
>
>
>
> On Wed, 7 Aug 1996, Khetan Gajjar wrote:
>
> > On Wed, 7 Aug 1996, Veggy Vinny wrote:
> >
> > > Hmmm, I meant I killed it with -9 and then type syslogd and it
> > > just exits out a second later...
> >
> > Weird. I dunno what it is.
>
> I thought kill -HUP didn't work on syslogd.
It's a bit annoying:
>>>>> ... ``I kill -9'd, restarted, exited''
>>>> ... I don't know, but ...
>>> ... I typed ``kill -9 ..., after it restarted, but it exited
>> ... I dunno, but kill
> ... I killed with KILL signal, restarted, exited
.
.
.
I don't know tcp-wrapper, but:
a) so many daemons (init, inetd, etc) use SIGHUP to re-read their
configuration files. So kill -HUP `cat /var/run/syslog.pid` isn't kill
it, only send an alert: ``Read your files, something was changed!''
b) I think, tcpd makes it's pid file like this:
------------------------------------+
v
open( PIDFILE, O_RDWR | O_CREAT | O_EXCL );
And because with kill -9, he/she/it hasn't any time to remove it, at next
start, exiting. Try kill -9, remove /var/run/syslog.pid, and start it over.
If it exits, sorry.
--
Gabor Zahemszky <zgabor@CoDe.hu>
-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
Earth is the cradle of human sense, but you can't stay in the cradle forever.
Tsiolkovsky
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608071335.NAA01627>