I tried crontab -u root -e and it opened the same crontab. I erased cron.allow and removed everything in cron.deny.
On 8/2/06, Michael Tinsay <[EMAIL PROTECTED]> wrote:
--- ramfree17 <[EMAIL PROTECTED]> wrote:
> can you use the actual path of the script in the
> cron job? i have experienced situations wherein
> /usr/bin is not included in the path of the user
> that executes the job. you can also check the
> permissions on the log file since the job might be
> executing but it cannot write to your log.
<snip>
Also, use absolute paths inside your script. Or set
the PATH variable very early in the script.
--- mike t.
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
--
John Peter Loh
Phone: +13602267476
Web: http://www.jploh.com/
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
