Re: 64-bit Cygwin installation is missing /usr/bin/lockfile

2013-08-15 Thread Steve Rowley
On Aug 14 16:34, Corinna Vinschen wrote: >On Aug 14 16:04, Corinna Vinschen wrote: >>On 8/13/2013 5:01 PM, Steve Rowley wrote: >>>I just installed 64-bit Cygwin on Win7, and noticed that /usr/bin/lockfile >>>is missing in my installation. [...] >> >>It

64-bit Cygwin installation is missing /usr/bin/lockfile

2013-08-14 Thread Steve Rowley
> On 8/13/2013 6:49 PM, Christopher Faylor wrote: >> On Tue, Aug 13, 2013 at 05:29:46PM -0400, Larry Hall (Cygwin) wrote: >>> On 8/13/2013 5:01 PM, Steve Rowley wrote: >>> I just installed 64-bit Cygwin on Win7, and noticed that >>> /usr/bin/lockfile is missing

64-bit Cygwin installation is missing /usr/bin/lockfile

2013-08-13 Thread Steve Rowley
I just installed 64-bit Cygwin on Win7, and noticed that /usr/bin/lockfile is missing in my installation. Does anyone else have this problem, or is it a problem with my installation? If the latter, what package should I reinstall in an attempt to get lockfile installed? Tnx. ___ Steve

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-29 Thread Steve Rowley
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]> > >>

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-25 Thread Steve Rowley
1004:1004: >HelpServicesGroup:S-1-5-21-473916646-3257906905-3362627345-1001:1001: >Domain Users:S-1-5-32-545:10545: But cron-config still stalls out in the same place. -- Steve Rowley http://alum.mit.edu/www/sgr/ Skype: sgr000 It is very dark & after 2000. If you continue, you are lik

RE: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-25 Thread Steve Rowley
>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 domai

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-25 Thread Steve Rowley
>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 jus

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-25 Thread Steve Rowley
relevant that has changed. It's still worth doing >though if you can't get it working. I have the latest version as of this morning, which is the last time I ran setup.exe. If it's changed since then, I'll get it tomorrow morning. :-) -- Steve Rowley <[EMAIL PROTECTED]

RE: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-25 Thread Steve Rowley
mantec, no? However, see previous reply to Pierre in which it turned out that Microsoft's Windows Defender was strangling cygrunsrv. That was a definite problem, but when I uninstalled Windows Defender the underlying problem still remained. Definitely looks to me like something is preve

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-23 Thread Steve Rowley
essage DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: cron: PID 4388: starting service `cron' failed: fork: 11, Resource tempora

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-23 Thread Steve Rowley
[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 > >

Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-22 Thread Steve Rowley
.txt'. > >Please include the generated file 'cygcheck.txt' *as an attachment*, >and NOT in the body of the mail message. So basically it didn't find any obvious bogosity. (e) At this point, I realized I'd be asking for help and so did cygcheck -srv &