iSCSI initiator: iscontrol cannot be stopped or killed

Ryan Stone rysto32 at
Thu Nov 24 00:35:30 UTC 2011

On Wed, Nov 23, 2011 at 7:26 PM, Mark Martinec
<Mark.Martinec+freebsd at> 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).

More information about the freebsd-current mailing list