[syslog-ng]Not writing to new logfile after rotate and restar t

[Livens Wim]

> On Mon, Feb 18, 2002 at 01:00:27PM +0100, Livens Wim wrote:
> > 
> > I have a rather straightforward syslog-ng.conf.  I write 
> all messages from
> > the local host to /var/adm/messages and things that come 
> from the net to a
> > separate (customer specific file) filtered on the source 
> host.  All works
> > well except that I can't rotate the customer specific 
> logfiles.  I can
> > rotate /var/adm/messages.  
> > 
> > doing:
> > # mv /var/adm/messages /var/adm/messages.0 
> > # kill -HUP `cat /etc/syslog-ng/syslog-ng.pid`
> > 
> > and new log are written to /var/adm/messages
> > 
> > BUT:
> > # mv /data/customer-logs/491 /data/customer-logs/491.0
> > # kill -HUP `cat /etc/syslog-ng/syslog-ng.pid`
> > 
> > and new messages are still written to data/customer-logs/491.0
> > 
> > I also tried stopping and starting syslog-ng and moving the 
> file somewhere
> > completly different.  
> > It still magically remembers the old file.
> 
> hmm.. are you HUP-ping the correct pid? you could possibly 
> truss syslog-ng
> while sending the HUP to see whether it closes and reopens 
> its files. (it
> should do so)