On 25.08.2009 22:21, Nicolas Bigaouette wrote:
Would your script needs a shebang?
2009/8/25 Sven-Hendrik Haase <sh@lutzhaase.com>
On 25.08.2009 12:51, solsTiCe d'Hiver wrote:
the crond log tells me that cron actually runs this command every
minute without a problem i think you mis-read your log. and it should tell you that cron is looking for changes in /etc/cron.d every minute. may be, if you change you first * * * in your lol then may be it will work. assuming you're using the good cron. because fcron does not support /etc/cron.d but there is other ways to achieve the same thing.
check crond man page or its documentation
I'm using dcron and also I didn't misread. Also, dcron doesn't look for changes in said directory without restarting from what I have found out. It actually tells me what it is going to execute and that is my /etc/cron.d/lol file. It would report and error otherwise. The thing that strikes me is that the command doesn't actually do anything. echo is a shell built-in of sh, bash, any shell really so env vars shouldn't be an issue.
Any ideas?
No, stuff in /etc/cron.d/ looks just like stuff in your crontab and gets executed by the shell mentioned in $SHELL. Still, it wouldn't matter because I'm using a built-in here. I'm really baffled by this.