Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3F79D4EE.8000902@yoda.bsd.uchicago.edu>
Date: Tue, 30 Sep 2003 14:09:34 -0500
From: Chunyu Liu <cliu AT yoda DOT bsd DOT uchicago DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: problem of cron in cygwin xp, final solution!
References: <3F78F297 DOT 7020800 AT yoda DOT bsd DOT uchicago DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0309300021150 DOT 3193 AT slinky DOT cs DOT nyu DOT edu> <3F79A42B DOT 2090906 AT yoda DOT bsd DOT uchicago DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0309301151190 DOT 3193 AT slinky DOT cs DOT nyu DOT edu> <3F79AE98 DOT 8060807 AT yoda DOT bsd DOT uchicago DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0309301243200 DOT 3193 AT slinky DOT cs DOT nyu DOT edu> <3F79BC86 DOT 4050607 AT yoda DOT bsd DOT uchicago DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0309301343330 DOT 26607 AT slinky DOT cs DOT nyu DOT edu> <3F79CF21 DOT 3020909 AT yoda DOT bsd DOT uchicago DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0309301449280 DOT 26607 AT slinky DOT cs DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.56.0309301449280.26607@slinky.cs.nyu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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 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
>>>>>>>>><http://cygwin.com/problems.html>.
>>>>>>>>>    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/