From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu,  6 Mar 2014 12:55:32 -0500
To: 9fans@9fans.net
Message-ID: <16669181b9e3008bbff2f219e23f5948@mikro.quanstro.net>
In-Reply-To: <5318A8F7.4000405@mail.com>
References: <5318A8F7.4000405@mail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] How to kill a process
Topicbox-Message-UUID: c4f1c386-ead8-11e9-9d60-3106f5b1d025

On Thu Mar  6 12:34:27 EST 2014, adriano.verardo@mail.com wrote:
> Hi, all.
>
> Five years ago I wrote the manager for a USB barcode reader.
> Basically a derivative of the keyboard mngr, but not embedded in usbd.
> Recently has been noted that after a unplug-plug of the reader, the
> kernel recognizes
> the reader (apparently) as usual but the mounted root of the manager is
> empty.
>
> The reason seems to be a spuriuos instance of the manager, impossible to
> kill
> with kill and slay too. In fact, after a reboot all works again.
> Both manager and application have been never changed while the
> kernel stuff is updated weekly (replica/pull).
>
> IMHO something changed in the interface between usbd and external managers.
>
>   Is it possible ?
>
> In what condition a process started by usbd becomes not killable ?

recommend a little debugging.  first
	eve; acid $pid
	acid; lstk()

then
	eve; acid -l kernel -k $pid /path/to/kernel
	acid; lstk()

the idea here is to figure out what this rogue process is doing.
and why it's not killable.

- erik