public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Pierre A. Humblet" <Pierre.Humblet@ieee.org>
To: "Bruno Zovich" <bzovich@gmail.com>,	<cygwin@cygwin.com>
Subject: Re: cron
Date: Wed, 19 Dec 2007 20:51:00 -0000	[thread overview]
Message-ID: <013701c8426c$9a815ed0$b40410ac@wirelessworld.airvananet.com> (raw)
In-Reply-To: <7678a5200712190936s3a7219f4na930aa9d2b27675b@mail.gmail.com>


----- Original Message ----- 
From: "Bruno Zovich" <>
To: <cygwin>
Sent: Wednesday, December 19, 2007 12:36 PM
Subject: ***[Possible UCE]*** cron


| Hello,
|
| I've tried multiple suggestions -- no luck,
| Can you point me in the right direction?

The error messages are
2007/12/12 15:50:03 [bzovich] cron: PID 2748: starting service `cron' failed: fork: 11, Resource 
temporarily unavailable

2007/12/12 16:10:24 [SYSTEM] cron: PID 2568: starting service `cron' failed: fork: 11, Resource 
temporarily unavailable


Those are messages from cygrunsrv indicating that it can't fork itself,
whether you run it as yourself or as system.
So this may have nothing to do with cron.

cygcheck reports that no Cygwin services exist.
Did you remove the cron service before running cronbug?

Can you run anything with cygrunserv? For example

~: ls -l /var/log/env.log                  [no such file yet]
ls: cannot access /var/log/env.log: No such file or directory
~: cygrunsrv -I env -p /bin/env
~: cygrunsrv -S env
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
The service has not been started.   [this is normal, the service has terminated quickly]
~: ls -l /var/log/env.log                   [now there is  a file :) ]
-rw-r--r-- 1 SYSTEM Administrators 1259 Dec 19 13:18 /var/log/env.log

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/

  reply	other threads:[~2007-12-19 18:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 18:59 cron Bruno Zovich
2007-12-19 20:51 ` Pierre A. Humblet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-10 21:27 cron Rolf Schlagenhaft
2012-01-10 21:46 ` cron Larry Hall (Cygwin)
2012-01-10 23:45 ` cron Rolf Schlagenhaft
2011-08-24 16:09 cron mramakishore
2011-08-24 16:58 ` cron Larry Hall (Cygwin)
2011-08-28 10:50   ` cron kishore
2011-08-31 18:07     ` cron Larry Hall (Cygwin)
2009-09-16  7:51 cron Μηχανογράφηση ΔΔΕ Α΄ Αθήνας
2009-09-16 16:15 ` cron Pierre A. Humblet
2008-05-15  3:13 cron Marc Kirby
2008-05-15 16:27 ` cron Pierre A. Humblet
2007-09-12 14:40 cron Alexander Polson
2007-09-12 14:58 ` cron Larry Hall (Cygwin)
2007-09-13  5:26   ` cron Pierre A. Humblet
2007-09-13  6:00     ` cron René Berber
2007-09-13 15:35       ` cron Pierre A. Humblet
2007-09-13 18:25         ` cron Larry Hall (Cygwin)
2007-08-31 15:25 cron Barry Benowitz
2007-08-31 15:50 ` cron Larry Hall (Cygwin)
2007-08-31 16:34 ` cron Pierre A. Humblet
2007-08-08 14:50 cron Kiran, Shashi
2007-08-08 16:26 ` cron Pierre A. Humblet
2007-08-09  9:44   ` cron shash
2007-04-12 16:07 cron Gary Worthy
2007-04-12 16:15 ` cron Dave Korn
2004-05-11 22:11 cron Jimmy Hayes
     [not found] ` <75EA21FE420C864D895DE6E87383D6A157EA41@exchange1.meddatahc s.com>
2004-05-11 23:11   ` cron Larry Hall
2003-05-09  1:37 cron Bill C Riemers
2003-04-01 17:27 cron! Igor Pechtchanski
2003-04-01 17:32 ` cron adam r. christopher
2003-04-01 17:42   ` cron Igor Pechtchanski
2003-04-01 17:45     ` cron Igor Pechtchanski
2003-04-01 18:37   ` cron Thorsten Kampe
2002-01-07  2:30 cron Facey Brian
2002-01-07  3:46 ` cron Gerrit P. Haase
2001-07-13 13:08 cron David G. Baur
2001-07-13 13:12 ` cron Gerrit P. Haase
2001-06-20 19:32 Cron Bob Zimmerman
2001-06-21  2:22 ` Cron Michael Schaap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='013701c8426c$9a815ed0$b40410ac@wirelessworld.airvananet.com' \
    --to=pierre.humblet@ieee.org \
    --cc=bzovich@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).