[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-misc
Subject:    Re: newsyslog errors
From:       Bryan Irvine <sparctacus () gmail ! com>
Date:       2004-12-30 17:03:33
Message-ID: 53d70630041230090388d759d () mail ! gmail ! com
[Download RAW message or body]

this is solved.  As it turned out cron had 2 seperate instances running.  

Thanks for the help.

--Bryan


On Tue, 28 Dec 2004 17:34:19 -0500, Garance A Drosihn <drosih@rpi.edu> wrote:
> At 2:12 PM -0800 12/28/04, Bryan Irvine wrote:
> >Info from the 2PM (PSD) run of newsyslog.
> >
> >first off, the errors that I received from the system via email
> >
> >email1:
> >newsyslog: can't chmod /var/cron/log.3.gz: No such file or directory
> >newsyslog: can't chown /var/cron/log.3.gz: No such file or directory
> >            [...etc...]
> >
> >email2:
> >newsyslog: can't chmod /var/cron/log.0: No such file or directory
> >newsyslog: can't chown /var/cron/log.0: No such file or directory
> >            [...etc...]
> >
> >Yup, I got *2* emails, and this is pretty normal.  Does this mean
> >newsyslog is running itself twice?  simultaneously?  I see that the
> >daemon and the cron log is listed in both of them.
> 
> That does seem pretty likely.  And if you're getting two emails, that
> probably means that there are two crontab entries which are running
> newsyslog (either directly, or indirectly).  It might be that you
> only get two copies running at certain times of the day.  That's
> where I would start looking, if I were you.  Check for the root-
> specific crontab, and check to see if any /etc/crontab entries are
> scripts which themselves will run newsyslog.
> 
> The first thing you might want to do is to replace the real
> newsyslog with a simple script which just saves a timestamp,
> and then runs the real newsyslog.  Something like:
> 
> #!/bin/sh
> echo "Started  newsyslog pid=$$ at `/bin/date`" >> /var/log/newsyslog
> /usr/bin/newsyslog.real "$@"
> echo "Finished newsyslog pid=$$ at `/bin/date`" >> /var/log/newsyslog
> 
> You might also toss in a:
> 
> /bin/ps -p$$ -o pid,ppid,uid,command    >> /var/log/newsyslog
> 
> before running newsyslog.real, just to see what the parent-pid is.
> 
> --
> Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
> Senior Systems Programmer           or  gad@freebsd.org
> Rensselaer Polytechnic Institute    or  drosih@rpi.edu

[prev in list] [next in list] [prev in thread] [next in thread]