On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote:
> Hi Sluggers:
>
> For some reason if I have cron setup like this the script does not do
> anything:
>
> hh mm * * * /usr/bin/perl /path_to_script/scriptname.pl > /dev/null 2>&1
>
> When I remove the "> /dev/null 2>&1" cron finally executes what I want the
> script to do.
You do know what the >/dev/null 2>&1 means don't you?
It means throw away all output from the script. If your script manipulates
some files this might be OK, if on the other hand it's purpose is to print
information on STDOUT and have it emailed to you it just doesen't make
sense to throw it away.
If on the other hand you're positive it's just not even being executed try
putting a shell script wrapper around it and also adding </dev/null to
ensure that if it's trying to read data that it will get end-of-file.
> Any clues ??
You didn't give us many yourself.
--
---<GRiP>---
Electronic Hobbyist, Former Arcadia BBS nut, Occasional nudist,
Linux Guru, SLUG/AUUG/Linux Australia member, Sydney Flashmobber,
BMX rider, Walker, Raver & rave music lover, Big kid that refuses
to grow up. I'd make a good family pet, take me home today!
Do people actually read these things?
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
