Hi all,

i am planning to implement log parsing on my kannel application server for easy log searching for me.

one of our developer gave me log parsing script as per my need which is written in perl & the script is doing its job perfectly.

I am facing the issue only at the time of Log rotation which happens at every night at 12 am.

my log get write in "/var/log/kannel/kannel_access.log" file & at the time of log rotation yesterdays log file gets rename to "kannel_access.log.1" & new "kannel_access.log" file gets created. more than 1 days old file gets archive in .gz format.

when my log parsing script (logparser.pl) is running in background & keeps watch on "kannel_access.log" file what ever logs get written in that file it take required values from the file & stores it in database tables.

issue that i am facing is at the log rotation i run prerotate script like below.

==============
kill -ABRT `ps auxf | grep "[p]erl logparser.pl" | awk '{print $2}'`
==============

after i run postrotate script as below.

==============
killall -HUP bearerbox smsbox wapbox || true > /dev/null 2> /dev/null
cd /root/logparser/
/usr/bin/perl logparser.pl log_parsing_configuration_rxkannel.conf &
==============

but my perl script (logparser.pl) keeps on running. after log rotation it should write log in newly created "/var/log/kannel/kannel_access.log" file but it keeps on writing in yesterday log file which now became "/var/log/kannel/kannel_access.log.1" after log rotation.

I simply want at the time of log rotation the log parsing script (logparser.pl) should get pause till my log rotation happens & till new log file get created. after the log rotation & after creation of new "kannel_access.log" file it should start writing logs in the newly created "kannel_access.log" file.

hope i mentioned my issue properly.

please if you have any suggestion on above or if i made any mistake or missed something kindly let me know.

You need to get the programmer to add signal handlers for eg SIGUSR1 to stop reading (ie close handle on that 'old' file), & SIGUSR2 to start reading (open handle on new file).
If a prog doesn't have an explicit SIG handler, it'll do nothing or whatever the system default is (if anything), which usually only applies to things like SIGKILL, SIGTERM etc.