Please check your C:\WINNT40 for other utilities,
such as 'cron.exe'. Consider deleting these
programs, or moving them to another directory
in your PATH.
3. Please examine your /var/log/cron.log to see
if it provides any useful messages.
4. Please provide a copy of your crontab:
$ crontab -
1. From your cygcheck.txt:
>...
> Found: C:\WINNT40\grep.exe
> Found: d:\cygwin\bin\grep.exe
> Warning: C:\WINNT40\grep.exe hides d:\cygwin\bin\grep.exe
>...
Please check your C:\WINNT40 for other utilities,
such as 'cron.exe'. Consider deleting these
programs, or moving them to another dire
"Harig, Mark" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Here is a new version of the cron
diagnostic script. It contains another
test suggested and provided by Pierre
Humblet.
The new test checks to see if there
is a password entry that corresponds
to the values in the environm
Here is a new version of the cron
diagnostic script. It contains another
test suggested and provided by Pierre
Humblet.
The new test checks to see if there
is a password entry that corresponds
to the values in the environment
variables $USERNAME and $USERDOMAIN
cron_diagnose.sh
Description: cr
> > If none of this fixes the problem, then report your problem
> > to [EMAIL PROTECTED] Please include a copy of your crontab,
> > ('crontab -l') and the output of 'cygcheck -srv > cygcheck.txt'.
> >
> > PLEASE include the generated files 'cygcheck.txt' *as an
> attachment*,
> > and NOT in the b
"Harig, Mark" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> If none of this fixes the problem, then report your problem
> to [EMAIL PROTECTED] Please include a copy of your crontab,
> ('crontab -l') and the output of 'cygcheck -srv > cygcheck.txt'.
>
> PLEASE include the generate
>
> If none of this fixes the problem, then report your problem
> to [EMAIL PROTECTED] Please include a copy of your crontab,
> ('crontab -l') and the output of 'cygcheck -srv > cygcheck.txt'.
>
> PLEASE include the generated files 'cygcheck.txt' *as an attachment*,
> and NOT in the body of the
"Harig, Mark" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Please run the attached diagnostic script.
It will attempt to determine whether there
are any problems with the various files
needed by cron. It does NOT modify any
files (which you can verify for yourself
by reading the sc
gidson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 23, 2003 1:23 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Cannot Start Cron
>
>
> >
> > Look in the Windows "Application" event log for the exact error.
> > Igor
> > --
>
>
> The d
>
> Look in the Windows "Application" event log for the exact error.
> Igor
> --
The description for Event ID ( 0 ) in Source ( cron ) could not be found. It
contains the following insertion string(s): cron : PID 495 : `cron' service
stopped.
Thanks, Igor. Any clues here? Permissions on /va
On Thu, 23 Oct 2003, Buck Turgidson wrote:
> I am trying to start cron on a new installation of Cygwin on NT. My start
> script looks like this:
>
> cygrunsrv --stop cron
> cygrunsrv --remove cron
> cygrunsrv --install cron -p /usr/sbin/cron -a -D
> cygrunsrv --start cron
>
> But I get the follow
I am trying to start cron on a new installation of Cygwin on NT. My start
script looks like this:
cygrunsrv --stop cron
cygrunsrv --remove cron
cygrunsrv --install cron -p /usr/sbin/cron -a -D
cygrunsrv --start cron
But I get the following error. If anyone recognizes it, and has any
suggestions
Hi gurus,
After installing cron, I did 'ps -ef' and found that cron was
not started. So I checked /usr/doc/Cygwin/cron.README, and I
tried to start the Windows service using:
cygrunsrv -I cron -p /usr/sbin/cron -a -D
Then I checked Windows processes, and no cron.exe was there, so
I tried to start
13 matches
Mail list logo