On Thu, 04 Jan 2007 13:23:03 +1300
Volker Kuhlmann <[EMAIL PROTECTED]> wrote:

> > > > PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin
> > > 
> > > This in any case find your shutdown program.
> > > 
> 
> > This is incorrect. The system of cron.hourly, etc that runs using
> > /etc/crontab is totally separate to the *proper*, per user cron system
> > as set up through the crontab command. The above if from the former,
> > Roger is using the latter.
> 
> Yes he is. Which system does not have shutdown in one of the directories
> in that PATH, where it wouldn't be found? And that PATH is in effect
> until explicitly modified for per-user cron scripts as well as the
> /etc/cron.{daily,weekly etc} ones, which are in turn only called by a
> per-user cron script anyway. PATH is inherited.
> 
> Volker
> 
> -- 
> Volker Kuhlmann                       is list0570 with the domain in header
> http://volker.dnsalias.net/   Please do not CC list postings to me.

Entries in the per-user crontab are displayed using crontab -l ( + whatever 
other switches you wish ). crontab -l does not display the .weekly, etc jobs, 
whatever user you are logged in as. Also, as you stated, it it was coming from 
/etc/crontab, the PATH is set so it *will* find shutdown, and work, bad 
switches notwithstanding.

To test ( same results on FC4, Ubuntu and debian etch, example from FC4 ):

#cat /usr/local/bin/test.sh
#!/bin/bash
echo $PATH > /tmp/a

#crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.19771 installed on Fri Oct  8 09:39:06 2004)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# Take the weather from the station, and send to wu, cw and the database
0,10,20,30,40,50 * * * * /usr/local/bin/mysql2300
3,18,33,48 * * * * /usr/local/bin/cw2300 ; /usr/local/bin/wu2300
* * * * * /usr/local/bin/test.sh

#grep PATH /etc/crontab
PATH=/sbin:/bin:/usr/sbin:/usr/bin

# cat /tmp/a
/usr/bin:/bin

Also note that there are no weekly, daily entries from crontab -l ( as root ).


Please post your findings from SuSE so we can see if this is a distro specific 
bug.

Reply via email to