Cron sometimes act that way with complex commands. Make a script and run it in cron.
bash$ nano log.sh
=====================
#!/bin/bash
echo "test" >> $(date --date=yesterday "+%B_%d_%Y")_temp.txt
=====================
bash$ chmod +x log.sh
bash$ crontab -e
* * * * * /path/to/log.sh
that's it!
It will execute log.sh every minute (!)
On 2/22/06,
JM <[EMAIL PROTECTED]> wrote:
hmmm weird.. it does work if ill be executing it from the console.. but not as
a sched job... even if I place the absolute path of the binary...
tsk tsk tsk..
--
Mhac Janapin
PBTS SysAd
=============
http://mulingsilang.blogspot.com
=============
I'm an Open Source Enthusiast. c",)
Mozilla Firefox 1 - getfirefox.com
Mozilla Thunderbird 1 - mozilla.org
OpenOffice.org
=============
_________________________________________________ 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
