[rsyslog] HUP restart or not - was: RE: rsyslog - what's next?

[Rainer Gerhards]

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Sayan Chowdhury
> Sent: Tuesday, July 14, 2009 5:59 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] HUP restart or not - was: RE: rsyslog - what's next?
> 
> Yes exactly, I have changed the script to do just that recently , I was
just
> wondering whether this is the reason why you get so much resistance when
you
> want to deprecate the traditional HUP processing...

I think it is maily a "tradition" argument along the lines "but I am used
to...". Still hard to beat if everybody complains ;) I don't see any
technicaly reasons, especially as a restart-type restart IS a restart
(nothing less), just carried out in the most complex way ;)

Rainer

> 
> 
> On Tue, Jul 14, 2009 at 11:55 AM, Rainer Gerhards
> <rgerhards at hq.adiscon.com>wrote:
> 
> > > -----Original Message-----
> > > From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> > > bounces at lists.adiscon.com] On Behalf Of Sayan Chowdhury
> > > Sent: Tuesday, July 14, 2009 5:53 PM
> > > To: rsyslog-users
> > > Subject: Re: [rsyslog] HUP restart or not - was: RE: rsyslog - what's
> > next?
> > >
> > > Sorry if this is out of context.
> > >
> > > > this matches the traditional use of HUP to get syslogd to release the
> > > > files it's writing to so that they can be rotated away.
> > > >
> > > > it doesn't re-read the config file due to the fact that the rsyslog
> > config
> > > > file is so complex and can significantly alter the software by
loading
> > > > modules.
> > >
> > > I am still tempted to remove the non-restart type of HUP. Actually, it
is
> > > the
> > > root cause for a lot of complexities (read performance bottlenecks)
> > inside
> > > the engine. And all this for something that is not strictly needed.
> > However,
> > > there are always many opponents when I intend to remove the traditional
> > HUP
> > > behavior.
> > >
> > >
> > > Is there any other way to make the rsyslog process reread the conf file
> > > other than a restart?
> > > This is the only reason I use the traditional SIGHUP processing, I send
> > HUP
> > > after I alter the rsyslog.conf file.
> >
> >
> > No, but I always fail to see the big difference between typing
> >
> > $ kill -HUP ´cat /var/run/rsyslog.log´
> >
> > And
> >
> > $ /etc/rc.d/rsyslogd restart
> >
> > ;)
> >
> > Use the later one, and you do not need to use sighup. Even better, you
can
> > now use HUP for a lightweight "close the files only" log rotation thing
;)
> >
> > Rainer
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > http://www.rsyslog.com
> >
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com