RE: cron - error starting a service
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:[EMAIL PROTECTED] Sent: Friday, 22 September 2006 00:07 To: David Rekas; Harig, Mark; cygwin@cygwin.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/
RE: cron - error starting a service
Mark & Pierre, thanks for your advice. Please see below.
Mark:
$ /usr/bin/cron_diagnose.sh: This also did not find any errors. The
displayed version of this is 1.10. The revision in the source is 1.3
2004/12/21 16:14:4. Whereas the previous "older" version I was trying
before displays 1.8. Is my /usr/bin/cron_diagnose.sh really the latest
version?
Pierre:
# /etc/crontab: Cannot remove this or entries in this, since it doesn't
exist. (Is this "normal"?)
# /etc/cron.d: This directory is empty - is this what you meant?
# /var/cron/tabs/David Rekas: removed this crontab file, followed by
"cygrunsrv --start cron", however the usual "error starting a service"
came up.
# /var/log/cron.log: Have looked for this at various stages of the cron
installation/config/attempted starts/reinstallation, but have never seen
an instance. (Is this "normal"?)
In addition (1):
# Uninstalled the entire cron-3.0.1-19
# Reinstalled the entire cron-3.0.1-19 using Cygwin setup.exe from a
different mirror site
# Edited cron-config: enclosed "${USER}" and "$cron_table" in double
quotation marks
$ crontab -e: created new crontab
# Applied chmod and chgrp to relevant files/directories
$ cron-config: answered: [service: yes; yourself: no; ntsec: yes; start
yes]. This returned the same error.
$ /usr/bin/cron_diagnose.sh: This did not find any errors.
# /var/log/cron.log: does not exist
In addition (2):
# Created a new Windows user with no spaces in the name ("cygbatch"),
with administrative privileges. Updated passwd and group files, and
logged in as this user.
$ crontab -e: created new crontab
$ cron-config: answered: [service: yes; yourself: no; ntsec: yes; start
yes]. This returned the same error.
$ /usr/bin/cron_diagnose.sh: This did not find any errors.
# /var/log/cron.log: does not exist
Again, any further input into this case would be very appreciated.
Thanks,
Dave
--
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/
