From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:35:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F158106566B for ; Thu, 24 Nov 2011 00:35:30 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 018B08FC08 for ; Thu, 24 Nov 2011 00:35:29 +0000 (UTC) Received: by wwg14 with SMTP id 14so3249330wwg.31 for ; Wed, 23 Nov 2011 16:35:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GZj9xLHrIu/uBiSGftdZRa7ftQAWMEoI4BlILVzQw2Y=; b=d+lX+onhh08O5b128tYs0QmDUbaEr9+qHTa/h48wPCJh9uTLIWMBO945En2EVz0lqX 0enZ1ZDBbsTaLzLue4AH4Pn4kvyuFS0mAxHEQhWij9eKWqLnpHQ36yRMdev649AGVrCX VthuYTLQTCqtR7/1ra7PptaZnifwknTRyzpKk= MIME-Version: 1.0 Received: by 10.180.109.83 with SMTP id hq19mr25367160wib.54.1322094928745; Wed, 23 Nov 2011 16:35:28 -0800 (PST) Received: by 10.180.101.102 with HTTP; Wed, 23 Nov 2011 16:35:28 -0800 (PST) In-Reply-To: <201111240126.21470.Mark.Martinec+freebsd@ijs.si> References: <201111240126.21470.Mark.Martinec+freebsd@ijs.si> Date: Wed, 23 Nov 2011 19:35:28 -0500 Message-ID: From: Ryan Stone To: Mark Martinec Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: iSCSI initiator: iscontrol cannot be stopped or killed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2011 00:35:30 -0000 On Wed, Nov 23, 2011 at 7:26 PM, Mark Martinec 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 would be very helpful. (the second -k is not a typo).