Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 May 2013 04:23:28 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: --fork under Cygwin

On Mon, May 06, 2013 at 06:46:21PM -0400, jfoug@....net wrote:
> 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.

I've just added a way to enable/disable --fork with a one-line change in
os.h, and for now I disabled --fork on Cygwin builds.  Thanks!

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ