I'd recommend using the command of bash --login -c <your script>. This way, all the paths needed by perl, mailer, etc. are set up by the .profile as it would be. You're not opening this thing load of times per minute, so the performance shouldn't matter so much.
Just my two pence. Genneth > -----Original Message----- > From: Max Bowsher [mailto:maxb@;ukf.net] > Sent: 05 November 2002 22:32 > To: Stan Horwitz; [EMAIL PROTECTED] > Subject: Re: How to schedule scripts > > Stan Horwitz <[EMAIL PROTECTED]> wrote: > > > Now, I want to schedule this [perl] script to run once a day as > > Administrator. With that in mind, I created a request under Windows' > > Task scheduler, but when the scheduled time occurred, a Cygwin shell > > window opened up, but nothing else happens. The request I scheduled > > was "cygwin daily.pl; exit" but the "daily.pl" script never executes; > > nor does "exit". As such, I end up with a Window to a Cygwin shell on > > my screen. > > "cygwin" is of course "cygwin.bat". If you look at it, you will see that > it > doesn't make any attempt to pass args on to the shell. > But you don't want a shell anyway. Just invoke perl directly: "perl > /full/path/to/daily.pl". Of course you will need C:\cygwin\bin, or the > equivalent on your system, in PATH (either the system-wide setting, or the > user the script will run as), so that perl can be found, and it in turn > can > find DLLs that it needs. > > Max. > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/