Bug 351 – newsyslog does not start one of the jobs specified in the command column in newsyslog.conf

Bug 351 - newsyslog does not start one of the jobs specified in the command column in newsyslog.conf


Summary:	newsyslog does not start one of the jobs specified in the command column in n...

Status:	NEW

Product:	Newsyslog
Classification:	Unclassified
Component:	Newsyslog
Version:	1.1
Hardware:	Other OpenBSD

Importance:	normal normal
Assigned To:	Todd C. Miller

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-30 16:01 MDT by yifeng
Modified:	2009-04-30 16:01 MDT (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description yifeng 2009-04-30 16:01:27 MDT

I have installed newsyslog program on my system configured my newsyslog.conf with one of the following line,

/var/log/mylogdir/messages 644 5 30 24 Z "/bin/kill -HUP `cat /var/run/syslog.pid`; /myexecuteable/bin/emrsjob -s elog0 & ;"

And newsyslog is started as cron job every hour. The problem is that the job, "/bin/kill -HUP 'cat /var/run/syslog.pid'" is always started every time when newsyslog rolltate the log file, but it does not always start the second job, "/myexecuteable/bin/emrsjob -s elog0 &", which is a shell script. With "does not always" I mean problem occurs in 30% of the cases.

I am wondering if there are any special known behavior of newsyslog that I am not aware of.

Thanks for the help,

yifeng