On 2/22/06, Mhac Janapin <
[EMAIL PROTECTED]> wrote:
I tried it myself and found the same results. I even included the full path in my crontab.
I found a way to work around that. What I did is wrote that down to a script, say log.sh, and then call log.sh from cron. Bulkier, but it works.
HTH--On 2/22/06, Michael Tinsay < [EMAIL PROTECTED]> wrote:
Make sure that the PATH= line includes the right
folders. Or better yet, use full path in your crontab
entry.
--- mike t.
--- JM < [EMAIL PROTECTED]> wrote:
> hi,
>
> i executed this and it works... but when I placed
> it as a scheduled task
> (cron) hmm no result..
>
>
> echo test >> `date --date=yesterday
> "+%B_%Y"`_sample.txt
>
> tia,
_________________________________________________
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
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
--
cj pangilinan
linux user, java programmer
_________________________________________________ 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
