Thanks for the suggestions so far.
However, after trying all the suggestions, I'm still unable to launch
cron. Is there anything further to try before looking for
alternatives to cron?
Date: Thu, 25 Jan 2007 15:05:01 -0500
From: Steve Rowley [EMAIL PROTECTED]
Date: Thu, 25 Jan 2007 19:55:35
On Jan 25 19:55, DePriest, Jason R. wrote:
mkgroup_l_d:S-1-5-32-545:10545:
A Google search for
GID 10545
implies that this is 'Domain Users'.
Not that it should make a big difference, but you might want to edit
your /etc/group and change
mkgroup_l_d:S-1-5-32-545:10545:
to
Domain
--- Corinna Vinschen [EMAIL PROTECTED] ha
scritto:
Actually the SID S-1-5-32-545 is the Users group on
the local machine.
If you need the SID for the Domain Users group you
have to retrieve
it using `mkgroup -d -g Domain Users', which gives
you something
like this:
$ mkgroup -d -g
On 26 January 2007 09:34, Corinna Vinschen wrote:
once in a while? It's outdated (Dave?)
Hi, haven't forgotten but got a bit overloaded. I'll try and finish a first
draft this weekend.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info:
On Jan 26 12:00, Dave Korn wrote:
On 26 January 2007 09:34, Corinna Vinschen wrote:
once in a while? It's outdated (Dave?)
Hi, haven't forgotten but got a bit overloaded. I'll try and finish a first
draft this weekend.
Cool, thanks!
Corinna
--
Corinna Vinschen
On Fri, 26 Jan 2007, Marco Atzeri wrote:
--- Corinna Vinschen [EMAIL PROTECTED] ha scritto:
http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks.
Actually the SID S-1-5-32-545 is the Users group on
the local machine.
If you need the SID for the Domain Users group you
have to retrieve
Date: Tue, 23 Jan 2007 16:23:19 -
From: Dave Korn dave dot korn at artimi dot com
Seems like you don't have a valid /etc/groups file. You should fix that first.
My /etc/group file was made by:
$ mkgroup -lc /etc/group
Here are its current contents; if you can spot anything wrong, I'd be
Date: Tue, 23 Jan 2007 12:39:47 -0800
From: Brian Dessent brian at dessent dot net
cron: PID 4388: starting service `cron' failed: fork: 11, Resource
temporarily unavailable.
The problem is that the fork call is failing when cygrunsrv tries to
launch cron. There are a number of reasons that
Steve Rowley wrote:
If *that* fails, then I'd try getting a SYSTEM-owned bash shell and
seeing if you see general fork failures there. The method to do this is
a little silly, but I think there is a simple script available to
automate it if you search the archives for sysbash.
I'm gonna
On 25 January 2007 18:03, Steve Rowley wrote:
Date: Tue, 23 Jan 2007 16:23:19 -
From: Dave Korn dave dot korn at artimi dot com
Seems like you don't have a valid /etc/groups file. You should fix that
first.
My /etc/group file was made by:
$ mkgroup -lc /etc/group
Here are
Date: Thu, 25 Jan 2007 10:24:09 -0800
From: Brian Dessent [EMAIL PROTECTED]
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
Date: Thu, 25 Jan 2007 19:17:52 +
From: Dave Korn [EMAIL PROTECTED]
On 25 January 2007 18:03, Steve Rowley wrote:
[...]
mkgroup_l_d:S-1-5-32-545:10545:
^^
You are in a domain and you didn't use the -d option, hence the following
output in your
On 1/25/07, Steve Rowley wrote:
Date: Tue, 23 Jan 2007 16:23:19 -
From: Dave Korn dave dot korn at artimi dot com
Seems like you don't have a valid /etc/groups file. You should fix that first.
My /etc/group file was made by:
$ mkgroup -lc /etc/group
Here are its current contents; if
Date: Thu, 25 Jan 2007 19:55:35 +
From: DePriest, Jason R. [EMAIL PROTECTED]
mkgroup_l_d:S-1-5-32-545:10545:
A Google search for
GID 10545
implies that this is 'Domain Users'.
Not that it should make a big difference, but you might want to edit
your /etc/group and change
--- Steve Rowley [EMAIL PROTECTED] ha scritto:
Date: Mon, 22 Jan 2007 15:16:19 -0800
From: Brian Dessent brian at dessent dot net
Steve Rowley wrote:
In case of problem, examine the log file for
cron,
/var/log/cron.log, and the Windows event log
for information about the
[Summary: no significant directory permission problems; after fixing
even what looked like small problems, the cron daemon still will not
start. Any more suggestions? I'm willing to try just about anything.]
Date: Tue, 23 Jan 2007 10:38:29 +0100 (CET)
From: Marco Atzeri marco_atzeri at yahoo
- Original Message -
From: Steve Rowley
To: cygwin
Sent: Monday, January 22, 2007 11:25 PM
Subject: ***[Possible UCE]*** Re: Can't start cron daemon in Cygwin 1.5.23
under WinXP SP2
| Date: Mon, 22 Jan 2007 15:16:19 -0800
| From: Brian Dessent brian at dessent dot net
|
| Steve
On 23 January 2007 04:25, Steve Rowley wrote:
Output from C:\packages\cygwin\bin\id.exe (nontsec)
UID: 421382(nm67644) GID: 547(Power Users)
544(Administrators) 547(Power Users) 545(Users)
10545(mkgroup_l_d)
Output from C:\packages\cygwin\bin\id.exe (ntsec)
UID:
[Did we make each other's acquaintance @ MIT LIDS in the 1980's?]
Date: Tue, 23 Jan 2007 10:26:20 -0500
From: Pierre A dot Humblet Pierre dot Humblet at ieee dot org
It's not clear if the problem is in cron, cygrunsrv, cygwin or your XP setup.
So here are two suggestions:
1) run cron as
Steve Rowley wrote:
cron: PID 4388: starting service `cron' failed: fork: 11, Resource
temporarily unavailable.
It's starting to look to me as though the problem is either at the
cygrunsrv level or the WinXP level.
The problem is that the fork call is failing when cygrunsrv tries to
Steve Rowley wrote:
(1) Starting it via the cron-config script produces this:
Normally this is the only thing you have to do.
In case of problem, examine the log file for cron,
/var/log/cron.log, and the Windows event log
for information about the problem cron is having.
This
21 matches
Mail list logo
