Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 15 Mar 2006 09:35:32 +0000
From: Hari Sekhon <harisekhon@...il.com>
To:  john-users@...ts.openwall.com
Subject: Re: john the ripper output

special thanks to Hendrik for the solution... this turns out to be the 
best way of mimicking the tail -f standard unix way of doing it...

Hendrik May wrote:
> Hari Sekhon schrieb:
>> I've tried that but the same problem occurs which is why I stopped using
>> nohup.
>>
>> The output file nohup.out is also empty until john the ripper 
>> finishes at
>> which time it fills up with the output of what it cracked. But this 
>> defeats
>> the purpose, if it's cracking tonnes of passwords, I don't want to 
>> have to
>> wait days or weeks to actually see the results of the ones it's already
>> cracked.
>>
>>
>> On 14/03/06, John Smith <vun.list@...il.com> wrote:
>>  
>>> Hari Sekhon wrote:
>>>
>>>    
>>>> Can anybody tell me how to do this?
>>>>
>>>>       
>>> I find the command "nohup" (man nohup) useful. It detaches the process
>>> from the terminal and logs everything to a default file of nohup.out.
>>>
>>> -J.S.
>>>
>>> -- 
>>> To unsubscribe, e-mail john-users-unsubscribe@...ts.openwall.com and 
>>> reply
>>> to the automated confirmation request that will be sent to you.
>>>
>>>
>>>     
>>
>>   
> im not really sure if john writes the john.pot while its running, but 
> you could try running another instance of john with the option -show. 
> like this:
> john -show passfile
>

Powered by blists - more mailing lists

Your e-mail address:

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