> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:rsyslog-
> > [EMAIL PROTECTED] On Behalf Of Raoul Bhatia [IPAX]
> > Sent: Wednesday, October 08, 2008 12:49 PM
> > To: rsyslog-users
> > Subject: Re: [rsyslog] HUP action
> >
> > Rainer Gerhards wrote:
> > > - it is considered useful to have a full daemon restart be done
via
> > HUP
> > > - we can not sufficiently simply detect whether the configuration
> > >   has changed or not
> >
> > no knowing the code, i suggest md5/sha1/... checksum the whole file
> > after integrating everything including rsyslog.d/* into one flat
> > file.
> 
> Quite honestly, I do not like the extra effort. I now have to define
> two
> signals in any case, so let the user use the right one for what he
> intends to do ;)

Sorry, I was a bit brief: doing the checksum requires interpretation of
the config files, at least as far as the $IncludeConfig statements are
concerned. This is costly, as is the whole gathering process to build
the checksum. So to be on the efficient side, I need to have a dedicated
HUP for "non-reload" in any case. Thus I think there is not much added
benefit in doing the checksumming.

Rainer
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to