daca e redmuci, pune-i si userul sub care sa ruleze respectivul script, poate i se face greatza oricum, chiar daca ai declarat path, e preferabil sa pui toata calea in orice comenzi sau scripturi (e mai mult de scris, dar orice script care se respecta face la fel, si mie unuia nu mi-e lene)
Alex On Tue, 10 Feb 2004 16:19:57 +0200 Vali Lungu <[EMAIL PROTECTED]> wrote: > Fisierul meu crontab arata asa: > > # cat /etc/crontab > SHELL=/bin/bash > PATH=/sbin:/bin:/usr/sbin:/usr/bin > MAILTO=root > HOME=/ > > # run-parts > 01 * * * * root run-parts /etc/cron.hourly > 02 4 * * * root run-parts /etc/cron.daily > 22 4 * * 0 root run-parts /etc/cron.weekly > 42 4 1 * * root run-parts /etc/cron.monthly > > Adaug un job cu cron -e, de forma: > > # crontab -l > # DO NOT EDIT THIS FILE - edit the master and reinstall. > # (/tmp/crontab.7316 installed on Tue Feb 10 16:09:04 2004) > # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie > # Exp $) > 15 16 10 2 * tmpwatch /Valika/tmp/choy >>/Valika/tmp_del.log > > Dupa ce trece timpul pt executarea job-ului, primesc un mail de forma: > > >From [EMAIL PROTECTED] Tue Feb 10 16:15:00 2004 > Date: Tue, 10 Feb 2004 16:15:00 +0200 > From: [EMAIL PROTECTED] (Cron Daemon) > To: [EMAIL PROTECTED] > Subject: Cron <[EMAIL PROTECTED]> tmpwatch /Valika/tmp/choy > >>/Valika/tmp.del.log > X-Cron-Env: <SHELL=/bin/sh> > X-Cron-Env: <HOME=/root> > X-Cron-Env: <PATH=/usr/bin:/bin> > X-Cron-Env: <LOGNAME=root> > > /bin/sh: line 1: tmpwatch: command not found > > De unde trag concluzia ca degeaba am setat io variabilele PATH si > SHELL in /etc/crontab ca el face tot ce vrea el. > > Unde gresesc? Thanks in advance. > > > --- > Detalii despre listele noastre de mail: http://www.lug.ro/ > > --- Detalii despre listele noastre de mail: http://www.lug.ro/
