[<prev] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9de22814-496a-4bbc-8c03-ca369b3c0254@gmail.com>
Date: Tue, 13 May 2025 18:08:12 +0900
From: "SHINODA, Daisuke" <dskshnd@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: sudden shutdown by overheat
On 2025/05/08 7:04, magnum wrote:
> I can't see why the firmware & driver fails to automagically adjust the
> fan as needed so it would be quiet when not under high load and run fans
> at full speed as needed. But they never did that properly, and same with
> nvidia. Recent nvidias seem to rather throttle the clock than increasing
> fan speed. It's somewhat configurable though and at least they don't
> overheat.
I believe the reason is that AMD's Radeon drivers for Linux are rather
lacking. It seems they are putting much more effort into the Windows
version.
> I must admit I never realized we could use SIGSTOP and SIGCONT like
> that. FWIW we also have this default in john.conf:
>
> # While this file exists, john will pause (uncomment to enable)
> #PauseFile = /var/run/john/pause
>
> Uncomment the second line, and perhaps change the path (you can use a
> path like $JOHN/abort for using the directory where eg. john.conf is
> located without using full path). Then a script (or some user) can just
> create an empty file named "pause" in said path, and in a couple of
> seconds John will pause until the file is deleted. This method does not
> send the john process to the background like SIGSTOP does. Also, the
> user who wants to pause doesn't need to own the john process, write
> access to the pause file directory is enough.
I didn't know this. It might help improving my script. Thank you.
Regards,
Dai
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.
