Re: iSCSI initiator: iscontrol cannot be stopped or killed

From: Ryan Stone <rysto32_at_gmail.com>
Date: Wed, 23 Nov 2011 19:35:28 -0500
On Wed, Nov 23, 2011 at 7:26 PM, Mark Martinec
<Mark.Martinec+freebsd_at_ijs.si> wrote:
> Problem: the iscontrol process starts normally and establishes
> a session and brings up a device, but it cannot be stopped.
> It does not react to a HUP signal, and neither to KILL.

If you can get it back into this state, a procstat -k -k <iscontrol
pid> would be very helpful.
(the second -k is not a typo).
Received on Wed Nov 23 2011 - 23:35:30 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:21 UTC