Re: iSCSI initiator: iscontrol cannot be stopped or killed

Xin LI wrote:
> Try procstat -kk <pid> to find the calling stack, as a start?
> This could be very useful when tracking down problems.
> Also the 'D' flag from ps(1) output in most times are not quite useful
> and ps -o wchan would tell you what exactly it was waiting for, just FYI.

Posted both a few days ago, you must have missed it.

Ivan Voras wrote:
> You should probably ask at the freebsd-scsi@ mailing list. From looking 
> at the code it looks like "ffp" is used for LUN scan timeout.

Done, posted to freebsd-scsi@ mailing list.
Thanks for the suggestion.

  Mark
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"