[ITP] stress-ng 0.18.04

Brian Inglis Brian.Inglis@SystematicSW.ab.ca
Mon Apr 7 18:40:19 GMT 2025


On 2025-04-07 11:55, Christian Franke via Cygwin-apps wrote:
> Brian Inglis via Cygwin-apps wrote:
>> On 2025-04-07 09:34, Christian Franke via Cygwin-apps wrote:

>>> Tests are intentionally run separately because failing tests sometimes hang 
>>> and may even ignore SIGKILL. Therefore an external tool is used, pskill from 
>>> Sysinternals Suite is the default.
>>
>> Have you tried the Cygwin binary kill /usr/bin/kill -f PID..., which goes via 
>> Win32, or even with -W WINPID, which I have found adequate for all purposes so 
>> far, rather than the normal default shell kill commands, which are lacking.

> Yes, but it cannot kill processes by name like 'killall'. This is required 
> because a hanging stress-ng may leave many child processes behind. 'killall' 
> from psmisc lacks a -f.
> 
> An alternative would be to obtain the list of processes via ps or procps and 
> then run kill -f. Unfortunately ps may also hang when stress-ng hangs in some 
> rare cases.

True, but I use it to clean up hung cron jobs driven by procps -ae --forest to 
handle the child processes, and it has never stayed hung so far, as I run it 
from a time limited scheduled task, although procps sometimes hangs 
interactively! ;^>

As I said, /usr/bin/kill -fW WINPID... works with tasklist pids.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry


More information about the Cygwin-apps mailing list