Loop
February 24th, 2004, 21:06
I'm getting the following error from cron:

[code:1:12be36fa0b]From root@doorbitch.number6 Tue Feb 24 22:00:07 2004
X-Original-To: root@doorbitch.number6
Delivered-To: loop@doorbitch.number6
From: root@doorbitch.number6 (Cron Daemon)
To: root@doorbitch.number6
Subject: Cron <root@doorbitch> /usr/bin/newsyslog
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/bin:/sbin:/usr/bin:/usr/sbin>
X-Cron-Env: <HOME=/var/log>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>

newsyslog: warning - could not send SIGHUP to daemon[/code:1:12be36fa0b]

My problem is that I don't know which daemon is not getting the SIGHUP

Here is my newsyslog.conf

[code:1:12be36fa0b]# $OpenBSD: newsyslog.conf,v 1.22 2003/02/12 19:42:59 millert Exp $
#
# configuration file for newsyslog
#
# logfilename owner:group mode ngen size time [ZB]
/var/cron/log root:wheel 600 3 10 * Z
/var/log/aculog uucp:dialer 660 7 * 24 Z
/var/log/authlog root:wheel 640 7 * 168 Z
/var/log/daemon 640 5 30 * Z
/var/log/lpd-errs 640 7 10 * Z
/var/log/maillog 600 7 * 24 Z
/var/log/messages 644 5 30 * Z
/var/log/secure 600 7 * 168 Z
/var/log/wtmp 644 7 * 168 ZB
/var/log/xferlog 640 7 250 * Z
/var/log/ppp.log 640 7 250 * Z
/var/log/pflog 600 3 250 * ZB /var/run/pflogd.pid[/code:1:12be36fa0b]

Loop
March 2nd, 2004, 04:36
Heh ... figured out which daemon newsyslog couldn't HUP ... syslogd wasn't running :oops: