Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.Hawaii.Edu!ames!enews.sgi.com!EU.net!howland.erols.net!feed1.news.erols.com!insync!uunet!in1.uu.net!204.238.120.21!jump.net!grunt.dejanews.com!not-for-mail
Date: Mon, 30 Dec 1996 11:11:02 -0600
From: mcglynn@netjet.com
Subject: cron daemon cores; UNSAFE appears in log
Newsgroups: comp.unix.bsd.bsdi.misc
Message-ID: <851965143.30607@dejanews.com>
Organization: Deja News Usenet Posting Service
X-Article-Creation-Date: Mon Dec 30 16:59:49 1996 GMT
X-Originating-IP-Addr: 204.162.88.23 ()
X-Http-User-Agent: Mozilla/3.01 (Macintosh; I; PPC)
X-Authenticated-Sender: mcglynn@netjet.com
Lines: 41
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:5496
Some of the questions in this post will undoubtedly paint me as a beginner of
sorts... so be it. I'm stuck.
I've recently taken over the management of a BSDI BSD/OS 2.0.1 web server, which
for unknown reasons had all sorts of web log rotating and analysis scripts
called from /etc/crontab.
I used crontab -eu root to create a new cron tab file for the root user, and
moved the web log stuff (and some other miscellaneous stuff) there. Nearly
everything works fine...
except for the things that don't. The problem in a nutshell is that the call to
the web log analyser apparently fails. Two things happen that I haven't seen
happen before:
1) a core file is created in /var/cron, time-stamped at the
time the web log analyser was supposed to run
2) a line is written to /var/log/cron with the word "UNSAFE" in
the place where "CMD" usually appears. I haven't found any
reference to UNSAFE in the man pages for cron or crontab (or
dejanews, or www.bsdi.com, etc.).
Here's a sample of the log:
Dec 29 00:01:01 nice cron[25927]: (root) CMD
(/usr/ns-home/client1/pwebstats/pwebstats -c
/usr/ns-home/client1/pwebstats/conf/pwebstats.conf >>&
/tmp/client1_stats)
Dec 29 00:01:01 nice cron[25925]: (root) UNSAFE (netjet.com)
I'm confident that the call to the log analyser is syntactically correct, as
I can copy the line to a command line and run it without incident.
Can anyone explain the CMD and UNSAFE business? Or why cron is dumping core?
Thanks.
--
matt.
mcglynn@netjet.com
-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet