Date: Tue, 03 May 2011 14:42:38 -0400 From: Glenn Sieb <ges+lists@wingfoot.org> To: Janos Dohanics <web@3dresearch.com> Cc: freebsd-questions@freebsd.org, Robert Bonomi <bonomi@mail.r-bonomi.com> Subject: Re: /etc/newsyslog.conf and denyhosts Message-ID: <4DC04C9E.7050802@wingfoot.org> In-Reply-To: <20110503143244.81861e46.web@3dresearch.com> References: <20110503124037.a4469206.web@3dresearch.com> <201105031803.p43I3Px8067589@mail.r-bonomi.com> <20110503143244.81861e46.web@3dresearch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/3/11 2:32 PM, Janos Dohanics wrote:
>> Denyhosts has to be informed that the logfile has changed, so that
>> it can close and re-open the logfile. It may be possible by
>> sending it a 'signal', or you may have to kill/restart it. See
>> the documentation for denyhosts.
>>
>> Newsyslog itself does _not_ notify/restart any daemons you have
>> to do this yourself.
>From the man page for newsyslog.conf:
path_to_pid_file
This optional field specifies the file name containing a daemon's
process ID or to find a group process ID if the U flag was speci-
fied. If this field is present, a signal_number is sent the
process ID contained in this file. If this field is not present,
then a SIGHUP signal will be sent to syslogd(8), unless the N
flag has been specified. This field must start with `/' in order
to be recognized properly.
signal_number
This optional field specifies the signal number that will be sent
to the daemon process (or to all processes in a process group, if
the U flag was specified). If this field is not present, then a
SIGHUP signal will be sent.
--Glenn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DC04C9E.7050802>