Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E10D1F3.90306@shinnok.com>
Date: Sun, 03 Jul 2011 23:32:51 +0300
From: Shinnok <admin@...nnok.com>
To: john-dev@...ts.openwall.com
Subject: Re: Johnny GUI interactive status from John

Hey Frank,

On 07/03/2011 10:28 PM, Frank Dittrich wrote:
> Hi Shinnok
> 
> Am 03.07.2011 16:29, schrieb Shinnok:
>> *Another issue with this one is that john updates the status in
>> john.rec as often as specified in john.conf "Save" directive, which
>> by default it is set to 600 seconds. Using this from the GUI would
>> mean to modify the configuration to something like 5s or 10s.
> 
> You can force a status update by sending a signal 1 (SUGHUP)
> to the corresponding process:
> 
> kill -s 1 <pid_of_john_instance>
> 
> May be you should update the status only if the user presses
> a "refresh status info" button.
> Another option would be to send the kill -s 1 ... command only
> if the user actually is displaying at the status information.
> The update interval could be configurable by the user.

What about Windows? I can't use signals on that.

Thanks for the feedback,
Shinnok

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.