[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 May 2013 18:46:21 -0400
From: <jfoug@....net>
To: john-dev@...ts.openwall.com
Subject: Re: --fork under Cygwin
I would REALLY like someone else that has worked with this look at it, before I poopoo it. I have never used fork before, and simply tried to run with a 1 hash file, and -fork -inc:all. It wrote some fork messages out (4 of them, I think). There were numerous johns running, some listed as <defunct> some said they were running. Also numerous bashes. It 'appeared' like what I would expect for a forking process. However, things were not running, and were NOT killable. The processes would not even go away with a kill from another shell, or any amount of ^C's or ^D's I had to use a win32 process manager to clean up the mess.
Jim.
---- Solar Designer <solar@...nwall.com> wrote:
> Off-list, Jim wrote:
>
> On Mon, May 06, 2013 at 06:14:25PM -0400, jfoug@....net wrote:
> > Fork is evil under cygwin. I had to use process explorer to kill cygwins bash, and johns, trying to clean up. The cygwin shell (even from another shell), would not kill the processes spawned.
> >
> > It should be #defined out in options.c in a cywiin build, IMHO
>
> That's a pity. I was hoping it'd work better. I vaguely recall Rich
> reporting --fork almost working on contest edition under Cygwin, with
> only some caveats, and I was hoping I had addressed those now.
>
> Rich, maybe you could give the current code a try before we give up on it?
>
> Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
