Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<005b01c0b067$56b2eaa0$275c100a@actfs.co.uk>
From:	"Malcolm Boekhoff" <Malcolm DOT Boekhoff AT actfs DOT co DOT uk>
To:	"Cygwin News Group" <cygwin AT sources DOT redhat DOT com>
References:	<3AB583BE DOT A03D42A1 AT travelocity DOT com>
Subject:	Re: Scheduling shell scripts under bash on NT
Date:	Mon, 19 Mar 2001 11:25:44 -0000

1. Make sure the at schedule service is running:

    net start "Task Scheduler"

    Or "net start" and look for "task scheduler" or "schedule" (it got renamed somewhere along the service pack chain).

2. Your batch file must set all the environment options, e.g. PATH, HOME, CYGWIN, etc. before invoking any Cygwin tools. You can
quickly get a list of the current set using "set".

3. You might need the /interactive switch for "at".

4. This works for me (big script to backup and build everything overnight):

    at 21:00 /every:m,t,w,th,f,s,su cmd /c "pushd e:\mcb\bin && night >d:\temp\night.log"

    Where "night.bat" is a batch file that sets up all of my environment variables before invoking any Cygwin stuff.

5. To check your settings for the job, try this (change the 15:00 to two-minutes-from-now on your clock and then wait!):

    at 15:00 cmd /c "pushd c:\temp && set >c:\temp\set.log"

    and check the contents of the "c:\temp\set.log" file to see what kind of environment your at jobs are running in.


----- Original Message -----
From: "Jon Kunert" <jon DOT kunert AT travelocity DOT com>
To: <cygwin AT sourceware DOT cygnus DOT com>
Sent: Monday, March 19, 2001 3:57 AM
Subject: RE: Scheduling shell scripts under bash on NT


> >>Trying to schedule simple shell scripts.  Currently i have a
> >>nt batch file calling a bash script which works fine,
> >>Until I schedule the batch script using the WinNT at
> >>command.  Nothing happens.
>
> >Does your batch script need to interact with the desktop?  If so, you need to
> >enable that option if running the Schedule service using the LocalSystem
> >account.
> >John
>
> Good thought but Nothing.  I even tried scheduling a simple bash script
> that echoes to a txt doc.  Still nothing.  Any other ideas out there?
> I really don't want to have rewrite this in NT batch.
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -