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

2003-10-01 Thread 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!

2003-09-30 Thread 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:
http://www.google.com/search?q=%22%60cron%27+failed%3A+execv%3A+1%2C+Operation+not+permitted.%22+cygwin?
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
http://www.google.com/help/refinesearch.html#domain).  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 

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

2003-09-30 Thread 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:
 http://www.google.com/search?q=%22%60cron%27+failed%3A+execv%3A+1%2C+Operation+not+permitted.%22+cygwin?
 
 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
 http://www.google.com/help/refinesearch.html#domain).  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 

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

2003-09-30 Thread 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:
http://www.google.com/search?q=%22%60cron%27+failed%3A+execv%3A+1%2C+Operation+not+permitted.%22+cygwin?
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
http://www.google.com/help/refinesearch.html#domain).  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 

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

2003-09-30 Thread 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/