X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17849.1407.613000.987904@alum.mit.edu>
Date: Thu, 25 Jan 2007 14:31:11 -0500
From: Steve Rowley <sgr AT alum DOT mit DOT edu>
To: cygwin AT cygwin DOT com
Subject: Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2
In-Reply-To: <45B8F5C9.7BD69603@dessent.net>
References: <uwt3eznym DOT fsf AT sanofi-aventis DOT com> 	<45B545C3 DOT DF70C019 AT dessent DOT net> 	<17845 DOT 36409 DOT 265000 DOT 733500 AT sanofi-aventis DOT com> 	<009501c73f02$d6383200$3e0010ac AT wirelessworld DOT airvananet DOT com> 	<uirexzerl DOT fsf AT sanofi-aventis DOT com> 	<45B67293 DOT C9A30FBC AT dessent DOT net> 	<17848 DOT 61838 DOT 799000 DOT 494617 AT alum DOT mit DOT edu> 	<45B8F5C9 DOT 7BD69603 AT dessent DOT net>
X-Mailer: VM 7.19 under Emacs 21.3.1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

>Date: Thu, 25 Jan 2007 10:24:09 -0800
>From: Brian Dessent <brian AT dessent DOT net>
>
>Steve Rowley wrote:
>> I'm gonna need a bit more guidance here; I found this script:
>> 
>> http://www.cygwin.com/ml/cygwin/2003-09/msg01860/sysbash
>
>Here I meant just run ordinary commands like ls, less, whatever.  Pretty
>much anything you do from a shell prompt causes a fork, so really I was
>just curious if you got tons of error messages when trying to do
>anything or not.

Ok, easy enough.  The hardest part was not giggling at the way sysbash
goes over the hill and through the woods to launch a SYSTEM owned
shell...  So when the SYSTEM owned shell popped up, it could easily
fork an ls process:

    >SYSTEM@... /
    >$ ls
    >bin cygdrive cygwin.bat cygwin.ico etc lib proc sbin srv tmp usr var

>You could also try starting cron as SYSTEM from the prompt, as
>"/usr/sbin/cron -D" and see what happens there.

Another good idea.  So I tried that:

  >SYSTEM@... /
  >$ /usr/sbin/cron -D
  >[4076] cron started

and all my cron jobs started up beautifully.  (Dunny WHY, of
course...)  So before the Muse looked elsewhere, I quickly tried to
run cron-config back in an ordinary shell.  No luck; same problem:

  >Do you want to start the cron daemon as a service now? (yes/no) yes
  >cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1053:
  >The service did not respond to the start or control request in a timely fashion.

So I think we've ruled out my crontab and the cron program itself as
potential causes.  I believe that leaves some interaction between
cygrusrv and the OS or other antivirus/spyware/firewall stuff, no?

>I meant a development snapshot of the DLL, which you get at
><http://cygwin.com/snapshots/>.  The stuff you get with setup.exe are
>only released versions which change relatively rarely.  There's
>instructions in either the FAQ or users guide on using a snapshot, I
>think.

Fair enough.  In that case, I have the latest release version.
-- 
Steve Rowley <sgr AT alum DOT mit DOT edu> http://alum.mit.edu/www/sgr/ Skype: sgr000
It is very dark & after 2000.  If you continue, you are likely to be eaten by a bleen.



--
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/