RE: starting cron

2003-06-24 Thread Harig, Mark
> -Original Message- > From: Pierre A. Humblet [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 22, 2003 3:07 PM > To: [EMAIL PROTECTED] > Subject: Re: starting cron > > (text deleted) > P.S.: perhaps testing for uid=400 and gid=401 could be added > to the cr

Re: starting cron

2003-06-22 Thread Pierre A. Humblet
On Sun, Jun 22, 2003 at 05:49:47PM +, [EMAIL PROTECTED] wrote: > hello: > > cron diagnostic did not find any problems. but cron still does not work in my > machine. > I am attaching the cron diagnostic files as suggested. d:\cygwin\bin\id.exe output (nontsec) UID: 400(ckumar) GID: 401(mkpas

RE: starting cron

2003-06-22 Thread kumarchi
s*, > not as inline text. > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 20, 2003 6:07 PM > > To: Harig, Mark > > Subject: RE: starting cron > > > > > > I ran the scri

Re: starting cron

2003-06-21 Thread Thorsten Kampe
* [EMAIL PROTECTED] (2003-06-20 15:50 +0200) > I am unable to start the cron. I followed the instruction in > /usr/doc/Cygwin/README_cron and used cygrunsrv to start the service > But the services in my windows it was unable to start the cron. > Any suggextions? /var/log/cron.log and "Event Vie

RE: starting cron

2003-06-20 Thread Harig, Mark
Please run the attached script. It will attempt to diagnose your problem with cron. It will not modify any files on your computer. You might need to run the script several times. Each time that it finds a problem, it stops and displays a descriptive message. > -Original Message- > From