delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/09/26/00:23:39

X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Subject: RE: cron - error starting a service
Date: Tue, 26 Sep 2006 14:23:21 +1000
Message-ID: <F0767510AFF7894380599F3E3BCD7325017678AE@socw2ke001.optus.com.au>
From: "David Rekas" <David DOT Rekas AT optus DOT com DOT au>
To: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>, <cygwin AT cygwin DOT com>
X-imss-version: 2.042
X-imss-result: Passed
X-imss-approveListMatch: *@optus.com.au
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k8Q4NaCi004796

Thanks Pierre, your first suggestion has got this over the line. Given
that this development is for a dedicated machine with a single generic
username I will stick with the "myself" option for the time being.

The interesting thing is I just managed to configure, successfully start
the cron service, and run scheduled tasks with my username which
contains a space.


-----Original Message-----
From: Pierre A. Humblet [mailto:Pierre DOT Humblet AT ieee DOT org] 
Sent: Friday, 22 September 2006 00:07
To: David Rekas; Harig, Mark; cygwin AT cygwin DOT com
Subject: Re: cron - error starting a service

I am stumped and can only suggest some debugging. Here are some ideas:

- Can you start cron running as yourself (option in cron-config) ?
  Remember, cron won't process users with spaces, but the daemon
  should keep running.

- Can you start anything under cygrunsrv? For example a bash script
located
  in /usr/sbin that writes into some file in /var/log, sleeps for 10 s,
then exits

- Run as SYSTEM. Ways to do that have been posted on the list. My usual
way
  is to have inetd running with telnetd enabled. Temporarily clear the
SYSTEM 
  password field in /etc/password and specify a home dir and a shell for
SYSTEM, 
  then telnet into localhost as SYSTEM.
  Try to launch cron from the shell and see if there is any error
message.

I will be away for the next 10 days, so don't expect feedback from me
past this PM.

Pierre




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


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019