mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] init 1 kill khubd on 2.6.11
Date: Sun, 01 May 2005 17:21:41 -0400	[thread overview]
Message-ID: <1114982502.23614.1.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0505011659130.19155-100000@netrider.rowland.org>

On Sun, 2005-05-01 at 17:01 -0400, Alan Stern wrote:
> On Sun, 1 May 2005, Andrey Borzenkov wrote:
> 
> > Hub driver is using SIGKILL to terminate khubd. Unfortunately on a number of 
> > distributions switching init levels implicitly does "killall -9", killing 
> > khubd. The only way to restart it is to reload USB subsystem.
> > 
> > Is signal usage in this case really needed? What about replacing it with 
> > simple flag (i.e. will patch be accepted)?
> 
> IMO the problem lies in those distributions.  They should not
> indiscrimately kill processes when switching init levels.

It's probably not indiscriminate, all the init scripts I have seen only
resort to kill -9 if the process fails to terminate in an orderly
fashion via the /etc/rcX.d/Kfoo script.


  reply	other threads:[~2005-05-01 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 16:21 Andrey Borzenkov
2005-05-01 21:01 ` [linux-usb-devel] " Alan Stern
2005-05-01 21:21   ` Lee Revell [this message]
2005-05-01 22:30   ` Andrew Morton
2005-05-01 22:46     ` Nish Aravamudan
2005-05-01 22:55       ` Andrew Morton
2005-05-02  0:42         ` Nish Aravamudan
2005-05-02  0:31       ` Dmitry Torokhov
2005-05-02  8:00     ` Andrey Borzenkov
2005-05-02  9:30       ` Andrew Morton
2005-05-02 12:18         ` Andrey Borzenkov
2005-05-02 17:58           ` Andrey Borzenkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1114982502.23614.1.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome