Date: Fri, 4 Nov 2016 14:59:10 +0100 From: matlink <matlink@...link.fr> To: john-users@...ts.openwall.com Subject: Re: John does not fork as many times as I want I've omitted to tell something: after these missing forks, the main process returns me: 1:Fork: cannot allocate memory which explains why all forks are not poped. However it seems that I still have plenty of available memory (about 200GB free). Can this error come from another situation than lack of memory? Le 04/11/2016 à 14:34, matlink a écrit : > I'm using john-1.8.0-jumbo-1 to crack Linkedin password on a > 64-core/512GB ram server. > I want john to fork many times, I'm then using the following command: > > |$ john --fork=40 --format=Raw-SHA1-Linkedin > ../UNZIPPED/linkedin/passwords.txt > linkedin.log| > > After approx 5 minutes, john starts to fork and outputs: > > |Node numbers 1-40 of 40 (fork)| > > Even after waiting dozens of minutes, process monitoring only display 4 > john forks: > > |$ ps -ef | grep john | wc -l| > |5| > > Is that an expected behavior or I am missing something? > -- Matlink - Sysadmin matlink.fr Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/ XMPP/Jabber : matlink@...link.fr Clé publique PGP : 0x186BB3CA Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2
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.