RE: problem of cron in cygwin xp, final solution!

[Harig, Mark]

> 
> Maybe such things should be added to Mark Harig's "cron_diagnose.sh"?

> 
> > To make the life easier for the other followers:
> > 1. Need to set the mode of cygwin1.dll
> >
> > $ chmod +x /bin/cygwin1.dll

This is a more general problem than a problem with cron's
many files.  A sanity check for cygwin might be desirable,
but I do not know all of the many files and conditions that
would need to be checked for this.  Often, when all else
fails, the solution is to uninstall cygwin and re-install it.

> > 2. Need to create another directory $ mkdir /etc/cron.d
> > Also make it accessible, by changing the permission.

The absence of this directory is already checked for, as
are the directory permissions.  If it is missing, then
the script notifies the user and halts.

> > 3. Then, follow the standard guideline to start cron service, as
> > $ cygrunsrv --stop cron
> > $ cygrunsrv --remove cron
> > $ cygrunsrv --install cron -p /usr/sbin/cron -a -D
> > $ cygrunsrv --start cron
> >

The user is notified about these commands by cron_diagnose.sh


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: problem of cron in cygwin xp, final solution!

[Andrew DeFaria]

Chunyu Liu wrote:

Igor,

This link you gave me is the final solution.  I experienced exactly 
the same problem as Andrew described. 
BTDT! Glad my troubles helped you get cron working.

To make the life easier for the other followers:
1. Need to set the mode of cygwin1.dll
$ chmod +x /bin/cygwin1.dll
2. Need to create another directory $ mkdir /etc/cron.d
Also make it accessible, by changing the permission.
3. Then, follow the standard guideline to start cron service, as
$ cygrunsrv --stop cron
$ cygrunsrv --remove cron
$ cygrunsrv --install cron -p /usr/sbin/cron -a -D
$ cygrunsrv --start cron
Hopefully, this troubling problem can be solved in the next version 
cygwin setup. 
Maybe such things should be added to Mark Harig's "cron_diagnose.sh"?
===
"Very funny, Scotty. Now beam down my clothes."


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

To create a SYSTEM-owned bash prompt (RE: problem of cron in cygwin xp)

[Hannu E K Nevalainen \(garbage mail\)]

 Feel free to include the attached script wherever it "fits".

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --
--END OF MESSAGE-- 

sysbash
Description: Binary data
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: problem of cron in cygwin xp, final solution!

[Chunyu Liu]

Igor,

Thank you for giving me the final solution for this problem too.
Yes. It works now.
I appreciate all the help.
Chunyu

Igor Pechtchanski wrote:

Chunyu,

Just to close on the "at" issue.  You were getting "invalid command"
because you needed to put the time *before* the "/interactive".  Another
problem was that you needed to add the ".exe" to "bash".  So, a command
that just worked for me (from bash) was:
at 14:51 /interactive 'c:\cygwin\bin\bash.exe' --login -i

FWIW, if you tried to run cron from the SYSTEM-owned shell, you should
have gotten the error about cygwin1.dll.  Hope this helps,
Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:

 

Igor,

This link you gave me is the final solution.  I experienced exactly the
same problem as Andrew described.
To make the life easier for the other followers:
1. Need to set the mode of cygwin1.dll
$ chmod +x /bin/cygwin1.dll
2. Need to create another directory
$ mkdir /etc/cron.d
Also make it accessible, by changing the permission.
3. Then, follow the standard guideline to start cron service, as
$ cygrunsrv --stop cron
$ cygrunsrv --remove cron
$ cygrunsrv --install cron -p /usr/sbin/cron -a -D
$ cygrunsrv --start cron
Hopefully, this troubling problem can be solved in the next version
cygwin setup.
But the "at" function still does not work:
$ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i
Invalid command.
I tried it under DOS command envn, same error.

Anyway, the cron eventually worked.
Many thanks for the help!
Chunyu

Igor Pechtchanski wrote:

   

Chunyu,

Do you Google:
?
As for the "at" problem, you need to escape the backslashes when you're
running it from a bash shell.  So, either use
$ at /interactive 12:19 'c:\cygwin\bin\bash' --login -i

or

$ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i

or run it from a command prompt.
 Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:



 

Igor,

This is a error in the application one:
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and Support for details. The following information is part of the event:
cron : PID 3248 : starting service `cron' failed: execv: 1, Operation
not permitted."
I checked system log, no error there.

For SYSTEM-owned shell, are you talking about this method?
$ at /interactive 12:19 c:\cygwin\bin\bash --login -i
Invalid command.
$ at /interactive 12:19 /cygdrive/c/cygwin/bin/bash --login -i
Invalid command.
Did I miss anything?

Chunyu

Igor Pechtchanski wrote:



   

Chunyu,

The main part of the event is "cron : PID 3248 : `cron' service stopped.",
so this is not quite what you're looking for.  Are there other events from
cron around that time in the event log?  Did you look at the system log,
or the application one?
Google allows you to restrict the search to a particular domain (see
).  So, you'd search
for something like '"at /interactive" site:cygwin.com'.
Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:





 

Igor,

windows event log does contain something, but I can't understand them.
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and Support for details. The following information is part of the event:
cron : PID 3248 : `cron' service stopped.".
I don't know how to search "at /interactive" on "cygwin.com".  In
cygwin.com, no search engine is provided.
Chunyu

Igor Pechtchanski wrote:





   

Chunyu,

Does the Windows event log contain any clues?

Cron from the command line wouldn't start a service -- it'll start the
application itself...  Which should be enough to ascertain whether your
crontab works.
The instructions for getting a system-owned shell can easily be found by
searching Google for "system-owned shell cygwin".
 Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:





 

Igor,

Thank you for the help.

I tried to follow your instruction, but no luck to get it work.
1. cron_diagnosis.sh does not find any problem.
2. the cygcheck is attached.
3. The only error message I got is:
$ cygrunsrv --start cron
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error
1062:
The service has not been started.
4. cron.log is fine.

[1732] cron started
[1652] cron started
[1920] cron started
[3668] cron started
[264] cron started
[3668] cron started
[2284] cron started
5. cron from the command line  looks fine, does not report any error,
but does not start the service either.
6. How to ge

Re: problem of cron in cygwin xp, final solution!

[Igor Pechtchanski]

Chunyu,

Just to close on the "at" issue.  You were getting "invalid command"
because you needed to put the time *before* the "/interactive".  Another
problem was that you needed to add the ".exe" to "bash".  So, a command
that just worked for me (from bash) was:

at 14:51 /interactive 'c:\cygwin\bin\bash.exe' --login -i

FWIW, if you tried to run cron from the SYSTEM-owned shell, you should
have gotten the error about cygwin1.dll.  Hope this helps,
Igor

On Tue, 30 Sep 2003, Chunyu Liu wrote:

> Igor,
>
> This link you gave me is the final solution.  I experienced exactly the
> same problem as Andrew described.
> To make the life easier for the other followers:
> 1. Need to set the mode of cygwin1.dll
>
> $ chmod +x /bin/cygwin1.dll
> 2. Need to create another directory
> $ mkdir /etc/cron.d
> Also make it accessible, by changing the permission.
> 3. Then, follow the standard guideline to start cron service, as
> $ cygrunsrv --stop cron
> $ cygrunsrv --remove cron
> $ cygrunsrv --install cron -p /usr/sbin/cron -a -D
> $ cygrunsrv --start cron
>
>
> Hopefully, this troubling problem can be solved in the next version
> cygwin setup.
>
> But the "at" function still does not work:
> $ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i
> Invalid command.
>
> I tried it under DOS command envn, same error.
>
> Anyway, the cron eventually worked.
> Many thanks for the help!
>
> Chunyu
>
> Igor Pechtchanski wrote:
>
> >Chunyu,
> >
> >Do you Google:
> >?
> >
> >As for the "at" problem, you need to escape the backslashes when you're
> >running it from a bash shell.  So, either use
> >
> >$ at /interactive 12:19 'c:\cygwin\bin\bash' --login -i
> >
> >or
> >
> >$ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i
> >
> >or run it from a command prompt.
> >   Igor
> >
> >On Tue, 30 Sep 2003, Chunyu Liu wrote:
> >
> >
> >
> >>Igor,
> >>
> >>This is a error in the application one:
> >>"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
> >>The local computer may not have the necessary registry information or
> >>message DLL files to display messages from a remote computer. You may be
> >>able to use the /AUXSOURCE= flag to retrieve this description; see Help
> >>and Support for details. The following information is part of the event:
> >>cron : PID 3248 : starting service `cron' failed: execv: 1, Operation
> >>not permitted."
> >>
> >>I checked system log, no error there.
> >>
> >>For SYSTEM-owned shell, are you talking about this method?
> >>$ at /interactive 12:19 c:\cygwin\bin\bash --login -i
> >>Invalid command.
> >>
> >>$ at /interactive 12:19 /cygdrive/c/cygwin/bin/bash --login -i
> >>Invalid command.
> >>
> >>Did I miss anything?
> >>
> >>Chunyu
> >>
> >>Igor Pechtchanski wrote:
> >>
> >>
> >>
> >>>Chunyu,
> >>>
> >>>The main part of the event is "cron : PID 3248 : `cron' service stopped.",
> >>>so this is not quite what you're looking for.  Are there other events from
> >>>cron around that time in the event log?  Did you look at the system log,
> >>>or the application one?
> >>>
> >>>Google allows you to restrict the search to a particular domain (see
> >>>).  So, you'd search
> >>>for something like '"at /interactive" site:cygwin.com'.
> >>>  Igor
> >>>
> >>>On Tue, 30 Sep 2003, Chunyu Liu wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
> Igor,
> 
> windows event log does contain something, but I can't understand them.
> "The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
> The local computer may not have the necessary registry information or
> message DLL files to display messages from a remote computer. You may be
> able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> cron : PID 3248 : `cron' service stopped.".
> 
> I don't know how to search "at /interactive" on "cygwin.com".  In
> cygwin.com, no search engine is provided.
> 
> Chunyu
> 
> 
> Igor Pechtchanski wrote:
> 
> 
> 
> 
> 
> >Chunyu,
> >
> >Does the Windows event log contain any clues?
> >
> >Cron from the command line wouldn't start a service -- it'll start the
> >application itself...  Which should be enough to ascertain whether your
> >crontab works.
> >
> >The instructions for getting a system-owned shell can easily be found by
> >searching Google for "system-owned shell cygwin".
> >   Igor
> >
> >On Tue, 30 Sep 2003, Chunyu Liu wrote:
> >
> >
> >
> >
> >
> >>Igor,
> >>
> >>Thank you for the help.
> >>
> >>I tried to follow your instruction, but no luck to get it work.
> >>1. cron_diagnosis.sh does not find any problem.
> >>2. the cygcheck is attached.
> >>

Re: problem of cron in cygwin xp, final solution!

[Chunyu Liu]

Igor,

This link you gave me is the final solution.  I experienced exactly the 
same problem as Andrew described.
To make the life easier for the other followers:
1. Need to set the mode of cygwin1.dll

$ chmod +x /bin/cygwin1.dll
2. Need to create another directory 
$ mkdir /etc/cron.d
Also make it accessible, by changing the permission.
3. Then, follow the standard guideline to start cron service, as
$ cygrunsrv --stop cron
$ cygrunsrv --remove cron
$ cygrunsrv --install cron -p /usr/sbin/cron -a -D
$ cygrunsrv --start cron

Hopefully, this troubling problem can be solved in the next version 
cygwin setup.

But the "at" function still does not work:
$ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i
Invalid command.
I tried it under DOS command envn, same error.

Anyway, the cron eventually worked. 
Many thanks for the help!

Chunyu

Igor Pechtchanski wrote:

Chunyu,

Do you Google:
?
As for the "at" problem, you need to escape the backslashes when you're
running it from a bash shell.  So, either use
$ at /interactive 12:19 'c:\cygwin\bin\bash' --login -i

or

$ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i

or run it from a command prompt.
Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:

 

Igor,

This is a error in the application one:
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and Support for details. The following information is part of the event:
cron : PID 3248 : starting service `cron' failed: execv: 1, Operation
not permitted."
I checked system log, no error there.

For SYSTEM-owned shell, are you talking about this method?
$ at /interactive 12:19 c:\cygwin\bin\bash --login -i
Invalid command.
$ at /interactive 12:19 /cygdrive/c/cygwin/bin/bash --login -i
Invalid command.
Did I miss anything?

Chunyu

Igor Pechtchanski wrote:

   

Chunyu,

The main part of the event is "cron : PID 3248 : `cron' service stopped.",
so this is not quite what you're looking for.  Are there other events from
cron around that time in the event log?  Did you look at the system log,
or the application one?
Google allows you to restrict the search to a particular domain (see
).  So, you'd search
for something like '"at /interactive" site:cygwin.com'.
 Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:



 

Igor,

windows event log does contain something, but I can't understand them.
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and Support for details. The following information is part of the event:
cron : PID 3248 : `cron' service stopped.".
I don't know how to search "at /interactive" on "cygwin.com".  In
cygwin.com, no search engine is provided.
Chunyu

Igor Pechtchanski wrote:



   

Chunyu,

Does the Windows event log contain any clues?

Cron from the command line wouldn't start a service -- it'll start the
application itself...  Which should be enough to ascertain whether your
crontab works.
The instructions for getting a system-owned shell can easily be found by
searching Google for "system-owned shell cygwin".
  Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:



 

Igor,

Thank you for the help.

I tried to follow your instruction, but no luck to get it work.
1. cron_diagnosis.sh does not find any problem.
2. the cygcheck is attached.
3. The only error message I got is:
$ cygrunsrv --start cron
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error
1062:
The service has not been started.
4. cron.log is fine.

[1732] cron started
[1652] cron started
[1920] cron started
[3668] cron started
[264] cron started
[3668] cron started
[2284] cron started
5. cron from the command line  looks fine, does not report any error,
but does not start the service either.
6. How to get the SYSTEM-owned shell?

I've spent hours trying to find the answer to all the problems in the
sea of questions & answers, and can't make it.
It's really a headache.
Chunyu

Igor Pechtchanski wrote:



   

Chunyu,

Please do not send Cygwin questions in personal mail unless specifically
requested.  All discussion of cygwin-related topics should happen on the
Cygwin list unless specifically requested otherwise.  One of the benefits
is that the discussion ends up in the list archives.  Another is that you
have access to the expertise of many people instead of just one.
For your convenience, I'm redirecting this query to the Cygwin list.  More
replies below.
On Mon, 

Re: problem of cron in cygwin xp

[Igor Pechtchanski]

Chunyu,

Do you Google:
?

As for the "at" problem, you need to escape the backslashes when you're
running it from a bash shell.  So, either use

$ at /interactive 12:19 'c:\cygwin\bin\bash' --login -i

or

$ at /interactive 12:19 c:\\cygwin\\bin\\bash --login -i

or run it from a command prompt.
Igor

On Tue, 30 Sep 2003, Chunyu Liu wrote:

> Igor,
>
> This is a error in the application one:
> "The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
> The local computer may not have the necessary registry information or
> message DLL files to display messages from a remote computer. You may be
> able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> cron : PID 3248 : starting service `cron' failed: execv: 1, Operation
> not permitted."
>
> I checked system log, no error there.
>
> For SYSTEM-owned shell, are you talking about this method?
> $ at /interactive 12:19 c:\cygwin\bin\bash --login -i
> Invalid command.
>
> $ at /interactive 12:19 /cygdrive/c/cygwin/bin/bash --login -i
> Invalid command.
>
> Did I miss anything?
>
> Chunyu
>
> Igor Pechtchanski wrote:
>
> >Chunyu,
> >
> >The main part of the event is "cron : PID 3248 : `cron' service stopped.",
> >so this is not quite what you're looking for.  Are there other events from
> >cron around that time in the event log?  Did you look at the system log,
> >or the application one?
> >
> >Google allows you to restrict the search to a particular domain (see
> >).  So, you'd search
> >for something like '"at /interactive" site:cygwin.com'.
> >   Igor
> >
> >On Tue, 30 Sep 2003, Chunyu Liu wrote:
> >
> >
> >
> >>Igor,
> >>
> >>windows event log does contain something, but I can't understand them.
> >>"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
> >>The local computer may not have the necessary registry information or
> >>message DLL files to display messages from a remote computer. You may be
> >>able to use the /AUXSOURCE= flag to retrieve this description; see Help
> >>and Support for details. The following information is part of the event:
> >>cron : PID 3248 : `cron' service stopped.".
> >>
> >>I don't know how to search "at /interactive" on "cygwin.com".  In
> >>cygwin.com, no search engine is provided.
> >>
> >>Chunyu
> >>
> >>
> >>Igor Pechtchanski wrote:
> >>
> >>
> >>
> >>>Chunyu,
> >>>
> >>>Does the Windows event log contain any clues?
> >>>
> >>>Cron from the command line wouldn't start a service -- it'll start the
> >>>application itself...  Which should be enough to ascertain whether your
> >>>crontab works.
> >>>
> >>>The instructions for getting a system-owned shell can easily be found by
> >>>searching Google for "system-owned shell cygwin".
> >>>Igor
> >>>
> >>>On Tue, 30 Sep 2003, Chunyu Liu wrote:
> >>>
> >>>
> >>>
> Igor,
> 
> Thank you for the help.
> 
> I tried to follow your instruction, but no luck to get it work.
> 1. cron_diagnosis.sh does not find any problem.
> 2. the cygcheck is attached.
> 3. The only error message I got is:
> 
> $ cygrunsrv --start cron
> cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error
> 1062:
> The service has not been started.
> 
> 4. cron.log is fine.
> 
> [1732] cron started
> [1652] cron started
> [1920] cron started
> [3668] cron started
> [264] cron started
> [3668] cron started
> [2284] cron started
> 
> 5. cron from the command line  looks fine, does not report any error,
> but does not start the service either.
> 
> 6. How to get the SYSTEM-owned shell?
> 
> I've spent hours trying to find the answer to all the problems in the
> sea of questions & answers, and can't make it.
> It's really a headache.
> 
> Chunyu
> 
> 
> Igor Pechtchanski wrote:
> 
> 
> 
> >Chunyu,
> >
> >Please do not send Cygwin questions in personal mail unless specifically
> >requested.  All discussion of cygwin-related topics should happen on the
> >Cygwin list unless specifically requested otherwise.  One of the benefits
> >is that the discussion ends up in the list archives.  Another is that you
> >have access to the expertise of many people instead of just one.
> >
> >For your convenience, I'm redirecting this query to the Cygwin list.  More
> >replies below.
> >
> >On Mon, 29 Sep 2003, Chunyu Liu wrote:
> >
> >
> >
> >>Dear Igor Pechtchanski,
> >>
> >>I noticed that you've been trying discussed this problem in the forum.
> >>But I don't know whether you had the conclusion on this.
> >>Would you mind helping me?
> >>
> >>I have tried
> >>cygrunsrv -I cron 

Re: problem of cron in cygwin xp

[Chunyu Liu]

Igor,

This is a error in the application one:
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found. 
The local computer may not have the necessary registry information or 
message DLL files to display messages from a remote computer. You may be 
able to use the /AUXSOURCE= flag to retrieve this description; see Help 
and Support for details. The following information is part of the event: 
cron : PID 3248 : starting service `cron' failed: execv: 1, Operation 
not permitted."

I checked system log, no error there.

For SYSTEM-owned shell, are you talking about this method?
$ at /interactive 12:19 c:\cygwin\bin\bash --login -i
Invalid command.
$ at /interactive 12:19 /cygdrive/c/cygwin/bin/bash --login -i
Invalid command.
Did I miss anything?

Chunyu

Igor Pechtchanski wrote:

Chunyu,

The main part of the event is "cron : PID 3248 : `cron' service stopped.",
so this is not quite what you're looking for.  Are there other events from
cron around that time in the event log?  Did you look at the system log,
or the application one?
Google allows you to restrict the search to a particular domain (see
).  So, you'd search
for something like '"at /interactive" site:cygwin.com'.
Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:

 

Igor,

windows event log does contain something, but I can't understand them.
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and Support for details. The following information is part of the event:
cron : PID 3248 : `cron' service stopped.".
I don't know how to search "at /interactive" on "cygwin.com".  In
cygwin.com, no search engine is provided.
Chunyu

Igor Pechtchanski wrote:

   

Chunyu,

Does the Windows event log contain any clues?

Cron from the command line wouldn't start a service -- it'll start the
application itself...  Which should be enough to ascertain whether your
crontab works.
The instructions for getting a system-owned shell can easily be found by
searching Google for "system-owned shell cygwin".
   Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:

 

Igor,

Thank you for the help.

I tried to follow your instruction, but no luck to get it work.
1. cron_diagnosis.sh does not find any problem.
2. the cygcheck is attached.
3. The only error message I got is:
$ cygrunsrv --start cron
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error
1062:
The service has not been started.
4. cron.log is fine.

[1732] cron started
[1652] cron started
[1920] cron started
[3668] cron started
[264] cron started
[3668] cron started
[2284] cron started
5. cron from the command line  looks fine, does not report any error,
but does not start the service either.
6. How to get the SYSTEM-owned shell?

I've spent hours trying to find the answer to all the problems in the
sea of questions & answers, and can't make it.
It's really a headache.
Chunyu

Igor Pechtchanski wrote:

   

Chunyu,

Please do not send Cygwin questions in personal mail unless specifically
requested.  All discussion of cygwin-related topics should happen on the
Cygwin list unless specifically requested otherwise.  One of the benefits
is that the discussion ends up in the list archives.  Another is that you
have access to the expertise of many people instead of just one.
For your convenience, I'm redirecting this query to the Cygwin list.  More
replies below.
On Mon, 29 Sep 2003, Chunyu Liu wrote:

 

Dear Igor Pechtchanski,

I noticed that you've been trying discussed this problem in the forum.
But I don't know whether you had the conclusion on this.
Would you mind helping me?
I have tried
cygrunsrv -I cron -p /usr/sbin/cron -a -D
cygrunsrv -S cron
and set /var/run/cron.pid to a+rw,

At the "-S cron" step, I can even see the new record in the log file at
/var/log, saying
[1652] cron started
But cygwin pompts:
"cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
The service has not been started."
And "ps" does not show job of cron running. The cron does not do any
scheduled work either.
I checked Windows Services control panel, the cron is associated with
cygrunsrv there. But whenever it's "started", it stopped immediately.
Any help would be greatly appreciated!
Chunyu Liu
   

Is there any information in the log on why the cron program couldn't run?
Can you run cron from the command line?  ...From a SYSTEM-owned shell?
Did you search the list archives for a similar problem?  Did you run Mark
Harig's "cron_diagnose.sh"?
Also, please read and follow the Cygwin problem reporting guidelines at
.
 Igor
 

 



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/prob

Re: problem of cron in cygwin xp

[Igor Pechtchanski]

Chunyu,

The main part of the event is "cron : PID 3248 : `cron' service stopped.",
so this is not quite what you're looking for.  Are there other events from
cron around that time in the event log?  Did you look at the system log,
or the application one?

Google allows you to restrict the search to a particular domain (see
).  So, you'd search
for something like '"at /interactive" site:cygwin.com'.
Igor

On Tue, 30 Sep 2003, Chunyu Liu wrote:

> Igor,
>
> windows event log does contain something, but I can't understand them.
> "The description for Event ID ( 0 ) in Source ( cron ) cannot be found.
> The local computer may not have the necessary registry information or
> message DLL files to display messages from a remote computer. You may be
> able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> cron : PID 3248 : `cron' service stopped.".
>
> I don't know how to search "at /interactive" on "cygwin.com".  In
> cygwin.com, no search engine is provided.
>
> Chunyu
>
>
> Igor Pechtchanski wrote:
>
> > Chunyu,
> >
> > Does the Windows event log contain any clues?
> >
> > Cron from the command line wouldn't start a service -- it'll start the
> > application itself...  Which should be enough to ascertain whether your
> > crontab works.
> >
> > The instructions for getting a system-owned shell can easily be found by
> > searching Google for "system-owned shell cygwin".
> > Igor
> >
> > On Tue, 30 Sep 2003, Chunyu Liu wrote:
> >
> >> Igor,
> >>
> >> Thank you for the help.
> >>
> >> I tried to follow your instruction, but no luck to get it work.
> >> 1. cron_diagnosis.sh does not find any problem.
> >> 2. the cygcheck is attached.
> >> 3. The only error message I got is:
> >>
> >> $ cygrunsrv --start cron
> >> cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error
> >> 1062:
> >> The service has not been started.
> >>
> >> 4. cron.log is fine.
> >>
> >> [1732] cron started
> >> [1652] cron started
> >> [1920] cron started
> >> [3668] cron started
> >> [264] cron started
> >> [3668] cron started
> >> [2284] cron started
> >>
> >> 5. cron from the command line  looks fine, does not report any error,
> >> but does not start the service either.
> >>
> >> 6. How to get the SYSTEM-owned shell?
> >>
> >> I've spent hours trying to find the answer to all the problems in the
> >> sea of questions & answers, and can't make it.
> >> It's really a headache.
> >>
> >> Chunyu
> >>
> >>
> >> Igor Pechtchanski wrote:
> >>
> >> >Chunyu,
> >> >
> >> >Please do not send Cygwin questions in personal mail unless specifically
> >> >requested.  All discussion of cygwin-related topics should happen on the
> >> >Cygwin list unless specifically requested otherwise.  One of the benefits
> >> >is that the discussion ends up in the list archives.  Another is that you
> >> >have access to the expertise of many people instead of just one.
> >> >
> >> >For your convenience, I'm redirecting this query to the Cygwin list.  More
> >> >replies below.
> >> >
> >> >On Mon, 29 Sep 2003, Chunyu Liu wrote:
> >> >
> >> >>Dear Igor Pechtchanski,
> >> >>
> >> >>I noticed that you've been trying discussed this problem in the forum.
> >> >>But I don't know whether you had the conclusion on this.
> >> >>Would you mind helping me?
> >> >>
> >> >>I have tried
> >> >>cygrunsrv -I cron -p /usr/sbin/cron -a -D
> >> >>cygrunsrv -S cron
> >> >>
> >> >>and set /var/run/cron.pid to a+rw,
> >> >>
> >> >>At the "-S cron" step, I can even see the new record in the log file at
> >> >>/var/log, saying
> >> >>[1652] cron started
> >> >>But cygwin pompts:
> >> >>"cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
> >> >>The service has not been started."
> >> >>
> >> >>And "ps" does not show job of cron running. The cron does not do any
> >> >>scheduled work either.
> >> >>
> >> >>I checked Windows Services control panel, the cron is associated with
> >> >>cygrunsrv there. But whenever it's "started", it stopped immediately.
> >> >>
> >> >>Any help would be greatly appreciated!
> >> >>Chunyu Liu
> >> >
> >> >Is there any information in the log on why the cron program couldn't run?
> >> >Can you run cron from the command line?  ...From a SYSTEM-owned shell?
> >> >Did you search the list archives for a similar problem?  Did you run Mark
> >> >Harig's "cron_diagnose.sh"?
> >> >
> >> >Also, please read and follow the Cygwin problem reporting guidelines at
> >> >.
> >> >   Igor

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor

Re: problem of cron in cygwin xp

[Chunyu Liu]

Igor,

windows event log does contain something, but I can't understand them.
"The description for Event ID ( 0 ) in Source ( cron ) cannot be found. 
The local computer may not have the necessary registry information or 
message DLL files to display messages from a remote computer. You may be 
able to use the /AUXSOURCE= flag to retrieve this description; see Help 
and Support for details. The following information is part of the event: 
cron : PID 3248 : `cron' service stopped.".

I don't know how to search "at /interactive" on "cygwin.com".  In 
cygwin.com, no search engine is provided.

Chunyu

Igor Pechtchanski wrote:

Chunyu,

Does the Windows event log contain any clues?

Cron from the command line wouldn't start a service -- it'll start the
application itself...  Which should be enough to ascertain whether your
crontab works.
The instructions for getting a system-owned shell can easily be found by
searching Google for "system-owned shell cygwin".
Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:

Igor,

Thank you for the help.

I tried to follow your instruction, but no luck to get it work.
1. cron_diagnosis.sh does not find any problem.
2. the cygcheck is attached.
3. The only error message I got is:
$ cygrunsrv --start cron
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 
1062:
The service has not been started.

4. cron.log is fine.

[1732] cron started
[1652] cron started
[1920] cron started
[3668] cron started
[264] cron started
[3668] cron started
[2284] cron started
5. cron from the command line  looks fine, does not report any error,
but does not start the service either.
6. How to get the SYSTEM-owned shell?

I've spent hours trying to find the answer to all the problems in the
sea of questions & answers, and can't make it.
It's really a headache.
Chunyu



Igor Pechtchanski wrote:

>Chunyu,
>
>Please do not send Cygwin questions in personal mail unless 
specifically
>requested.  All discussion of cygwin-related topics should happen on 
the
>Cygwin list unless specifically requested otherwise.  One of the 
benefits
>is that the discussion ends up in the list archives.  Another is 
that you
>have access to the expertise of many people instead of just one.
>
>For your convenience, I'm redirecting this query to the Cygwin 
list.  More
>replies below.
>
>On Mon, 29 Sep 2003, Chunyu Liu wrote:
>
>
>
>>Dear Igor Pechtchanski,
>>
>>I noticed that you've been trying discussed this problem in the forum.
>>But I don't know whether you had the conclusion on this.
>>Would you mind helping me?
>>
>>I have tried
>>cygrunsrv -I cron -p /usr/sbin/cron -a -D
>>cygrunsrv -S cron
>>
>>and set /var/run/cron.pid to a+rw,
>>
>>At the "-S cron" step, I can even see the new record in the log 
file at
>>/var/log, saying
>>[1652] cron started
>>But cygwin pompts:
>>"cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 
error 1062:
>>The service has not been started."
>>
>>And "ps" does not show job of cron running. The cron does not do any
>>scheduled work either.
>>
>>I checked Windows Services control panel, the cron is associated with
>>cygrunsrv there. But whenever it's "started", it stopped immediately.
>>
>>Any help would be greatly appreciated!
>>Chunyu Liu
>>
>>
>
>Is there any information in the log on why the cron program couldn't 
run?
>Can you run cron from the command line?  ...From a SYSTEM-owned shell?
>Did you search the list archives for a similar problem?  Did you run 
Mark
>Harig's "cron_diagnose.sh"?
>
>Also, please read and follow the Cygwin problem reporting guidelines at
>.
>   Igor




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: problem of cron in cygwin xp

[Igor Pechtchanski]

Chunyu,

Does the Windows event log contain any clues?

Cron from the command line wouldn't start a service -- it'll start the
application itself...  Which should be enough to ascertain whether your
crontab works.
The instructions for getting a system-owned shell can easily be found by
searching Google for "system-owned shell cygwin".
Igor
On Tue, 30 Sep 2003, Chunyu Liu wrote:

Igor,

Thank you for the help.

I tried to follow your instruction, but no luck to get it work.
1. cron_diagnosis.sh does not find any problem.
2. the cygcheck is attached.
3. The only error message I got is:
$ cygrunsrv --start cron
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
The service has not been started.
4. cron.log is fine.

[1732] cron started
[1652] cron started
[1920] cron started
[3668] cron started
[264] cron started
[3668] cron started
[2284] cron started
5. cron from the command line  looks fine, does not report any error,
but does not start the service either.
6. How to get the SYSTEM-owned shell?

I've spent hours trying to find the answer to all the problems in the
sea of questions & answers, and can't make it.
It's really a headache.
Chunyu



Igor Pechtchanski wrote:

>Chunyu,
>
>Please do not send Cygwin questions in personal mail unless specifically
>requested.  All discussion of cygwin-related topics should happen on the
>Cygwin list unless specifically requested otherwise.  One of the benefits
>is that the discussion ends up in the list archives.  Another is that you
>have access to the expertise of many people instead of just one.
>
>For your convenience, I'm redirecting this query to the Cygwin list.  More
>replies below.
>
>On Mon, 29 Sep 2003, Chunyu Liu wrote:
>
>
>
>>Dear Igor Pechtchanski,
>>
>>I noticed that you've been trying discussed this problem in the forum.
>>But I don't know whether you had the conclusion on this.
>>Would you mind helping me?
>>
>>I have tried
>>cygrunsrv -I cron -p /usr/sbin/cron -a -D
>>cygrunsrv -S cron
>>
>>and set /var/run/cron.pid to a+rw,
>>
>>At the "-S cron" step, I can even see the new record in the log file at
>>/var/log, saying
>>[1652] cron started
>>But cygwin pompts:
>>"cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
>>The service has not been started."
>>
>>And "ps" does not show job of cron running. The cron does not do any
>>scheduled work either.
>>
>>I checked Windows Services control panel, the cron is associated with
>>cygrunsrv there. But whenever it's "started", it stopped immediately.
>>
>>Any help would be greatly appreciated!
>>Chunyu Liu
>>
>>
>
>Is there any information in the log on why the cron program couldn't run?
>Can you run cron from the command line?  ...From a SYSTEM-owned shell?
>Did you search the list archives for a similar problem?  Did you run Mark
>Harig's "cron_diagnose.sh"?
>
>Also, please read and follow the Cygwin problem reporting guidelines at
>.
>   Igor
--
http://cs.nyu.edu/~pechtcha/
 |\  _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
|,4-  ) )-,_. ,\ (  `'-'Igor Pechtchanski, Ph.D.
   '---''(_/--'  `-'\_) fL  a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: problem of cron in cygwin xp

[Chunyu Liu]

Igor,

Thank you for the help.

I tried to follow your instruction, but no luck to get it work.
1. cron_diagnosis.sh does not find any problem.
2. the cygcheck is attached.
3. The only error message I got is:
$ cygrunsrv --start cron
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
The service has not been started.
4. cron.log is fine.

[1732] cron started
[1652] cron started
[1920] cron started
[3668] cron started
[264] cron started
[3668] cron started
[2284] cron started
5. cron from the command line  looks fine, does not report any error, 
but does not start the service either.

6. How to get the SYSTEM-owned shell?

I've spent hours trying to find the answer to all the problems in the 
sea of questions & answers, and can't make it.
It's really a headache.

Chunyu



Igor Pechtchanski wrote:

Chunyu,

Please do not send Cygwin questions in personal mail unless specifically
requested.  All discussion of cygwin-related topics should happen on the
Cygwin list unless specifically requested otherwise.  One of the benefits
is that the discussion ends up in the list archives.  Another is that you
have access to the expertise of many people instead of just one.
For your convenience, I'm redirecting this query to the Cygwin list.  More
replies below.
On Mon, 29 Sep 2003, Chunyu Liu wrote:

 

Dear Igor Pechtchanski,

I noticed that you've been trying discussed this problem in the forum.
But I don't know whether you had the conclusion on this.
Would you mind helping me?
I have tried
cygrunsrv -I cron -p /usr/sbin/cron -a -D
cygrunsrv -S cron
and set /var/run/cron.pid to a+rw,

At the "-S cron" step, I can even see the new record in the log file at
/var/log, saying
[1652] cron started
But cygwin pompts:
"cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
The service has not been started."
And "ps" does not show job of cron running. The cron does not do any
scheduled work either.
I checked Windows Services control panel, the cron is associated with
cygrunsrv there. But whenever it's "started", it stopped immediately.
Any help would be greatly appreciated!
Chunyu Liu
   

Is there any information in the log on why the cron program couldn't run?
Can you run cron from the command line?  ...From a SYSTEM-owned shell?
Did you search the list archives for a similar problem?  Did you run Mark
Harig's "cron_diagnose.sh"?
Also, please read and follow the Cygwin problem reporting guidelines at
.
	Igor
 


Cygwin Win95/NT Configuration Diagnostics
Current System Time: Tue Sep 30 10:11:33 2003

Windows XP Professional Ver 5.1 Build 2600 Service Pack 1

Path:   C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
c:\oracle\ora81\bin
c:\Program Files\Oracle\jre\1.1.7\bin
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
"C
C:\cygwin\Program Files\Common Files\Adaptec Shared\System"
"C
C:\cygwin\PROGRA~1\ULTRAE~1"
"C
C:\cygwin\Program Files\Symantec\Norton Ghost 2003\"
d:\PROGRA~1\PYROSE~1\PSQ96M~1.0
c:\Program Files\Common Files\Roxio Shared\DLLShared
"C
C:\cygwin\Program Files\j2sdk1.4.1_02\bin"
c:\PROGRA~1\COMMON~1\MGISHA~1\Video
C:\cygwin\usr\X11R6\bin
c:\Program Files\j2sdk1.4.1_02\bin
.

Output from C:\cygwin\bin\id.exe (nontsec)
UID: 1005(cliu) GID: 513(None)
513(None)

Output from C:\cygwin\bin\id.exe (ntsec)
UID: 1005(cliu) GID: 513(None)
513(None)544(Administrators)  
545(Users)

SysDir: C:\WINDOWS\System32
WinDir: C:\WINDOWS

HOME = `C:\cygwin\home\cliu'
MAKE_MODE = `unix'
PWD = `/cygdrive/d/system_manager'
USER = `cliu'

ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\Chunyu Liu\Application Data'
CLIENTNAME = `Console'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `MOON'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
CVS_RSH = `/bin/ssh'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\Chunyu Liu'
HOSTNAME = `MOON'
LOGONSERVER = `\\MOON'
MANPATH = `:/usr/ssl/man'
NUMBER_OF_PROCESSORS = `1'
OLDPWD = `/cygdrive/d'
OS = `Windows_NT'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 7, GenuineIntel'
PROCESSOR_LEVEL = `15'
PROCESSOR_REVISION = `0207'
PROGRAMFILES = `C:\Program Files'
PROMPT = `$P$G'
PS1 = `\[\033]0;\w\007
[EMAIL PROTECTED] \[\033[33m\w\033[0m\]
$ '
PS5ROOT = `C:\Program Files\Roxio\Easy CD Creator 6\PhotoSuite\'
SESSIONNAME = `Console'
SHLVL = `1'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `c:\DOCUME~1\CHUNYU~1\LOCALS~1\Temp'
TERM = `cygwin'
TMP = `c:\DOCUME~1\CHUNYU~1\LOCALS~1\Temp'
USERDOMAIN = `MOON'
USERNAME = `Chunyu Liu'
USERPROFILE = `C:\Documents and Settings\Chunyu Liu'
WINDIR = `C:\WINDOWS'
_ = `/usr/bin/cygcheck'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_C

Re: problem of cron in cygwin xp

[Igor Pechtchanski]

Chunyu,

Please do not send Cygwin questions in personal mail unless specifically
requested.  All discussion of cygwin-related topics should happen on the
Cygwin list unless specifically requested otherwise.  One of the benefits
is that the discussion ends up in the list archives.  Another is that you
have access to the expertise of many people instead of just one.

For your convenience, I'm redirecting this query to the Cygwin list.  More
replies below.

On Mon, 29 Sep 2003, Chunyu Liu wrote:

> Dear Igor Pechtchanski,
>
> I noticed that you've been trying discussed this problem in the forum.
> But I don't know whether you had the conclusion on this.
> Would you mind helping me?
>
> I have tried
> cygrunsrv -I cron -p /usr/sbin/cron -a -D
> cygrunsrv -S cron
>
> and set /var/run/cron.pid to a+rw,
>
> At the "-S cron" step, I can even see the new record in the log file at
> /var/log, saying
> [1652] cron started
> But cygwin pompts:
> "cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
> The service has not been started."
>
> And "ps" does not show job of cron running. The cron does not do any
> scheduled work either.
>
> I checked Windows Services control panel, the cron is associated with
> cygrunsrv there. But whenever it's "started", it stopped immediately.
>
> Any help would be greatly appreciated!
> Chunyu Liu

Is there any information in the log on why the cron program couldn't run?
Can you run cron from the command line?  ...From a SYSTEM-owned shell?
Did you search the list archives for a similar problem?  Did you run Mark
Harig's "cron_diagnose.sh"?

Also, please read and follow the Cygwin problem reporting guidelines at
.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/