problems with 'periodic' in 4.11 p-24

[Bill Vermillion]

On or about Thu, Sep 13, 2007 at 06:25 , while attempting a 
Zarathustra emulation Luke Hollins thus spake:

> Can you post your crontab? Maybe one line has the username twice .

Boy - that was the hint that helped me find the problem.

How I did this I do not know, but the /etc/crontab was
duplicated in /var/cron/tabs/root.

That was why the 'root: not found' message occured as the 
normal cron doesn't use that.

I still don't know how I did this - particularly after admining
FreeBSD systems since 1995.

Maybe I did it in my sleep.

But thanks for the comment as that put me on the correct track.

Bill
> 
> Bill Vermillion wrote:
> > I just updated a 4.11 machine to patch level 24.  Somehow I had
> > overlooked that machine earlier as it's so stable and only
> > is handling web pages, secondary dns and secondary mail.
> >
> > I've checked everthing I can think of but now all the scripts
> > that are run from the root crontab - with the user of 'root' as
> > shipped in the distrubution now give me error messages.
> >
> > The messages are from the atrun daemon.
> >
> > Here is the message I'm getting just as I bounced it to this
> > account.
> >
> > Theone difference I see in this is that the Subject line
> > when viewed in mutt on the original machine has
> > root?/usr/libexec/atrun.
> >
> > ----------------------------------
> > Message-Id: <200709121250.l8CCo0fB051558 at iserv.wanlogistics.net>
> > From: root at iserv.wanlogistics.net (Cron Daemon)
> > To: root at iserv.wanlogistics.net
> > Subject: Cron <root at iserv> root	/usr/libexec/atrun
> > X-Cron-Env: <SHELL=/bin/sh>
> > X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
> > X-Cron-Env: <HOME=/root>
> > X-Cron-Env: <MAILTO=root at iserv.wanlogistics.net>
> > X-Cron-Env: <LOGNAME=root>
> > X-Cron-Env: <USER=root>
> > X-UIDL: EO^"!?>h"!Y(@"!+&N"!
> >
> > root: not found
> >
> > ----------------------------------
> >
> > I've checked everywhere I can think of.  I've even added
> > the MAILTO line in the crontab with an FQDN address.  That didn't
> > help either.
> >
> > It must be something simple I've overlooked or else I'd have seen
> > reports of this before.
> >
> > The cvsup is only for the RELEASE - so nothing is there that
> > would be added after the last security update to that last year.
> >
> > I'm sorry this is so late in time frame of 4.11 - but as I said -
> > for some reason this is one server I inadvertantly overlooked.
> > Normally the OS gets updated the day any security changes are made.
> >
> > Thanks
> >
> > Bill
> >
> >   
> 

-- 
Bill Vermillion - bv @ wjv . com