linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Steve French <smfltc@us.ibm.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: filesystem signal handling
Date: Wed, 28 Apr 2004 20:28:35 +0100	[thread overview]
Message-ID: <20040428192835.GA2836@mail.shareable.org> (raw)
In-Reply-To: <1083173539.2856.90.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> As for SIGINT vs SIGKILL - the only difference I can see is that the
> former can be generated directly from the keyboard.

The other difference is that SIGINT can be intercepted by the
application to do cleanups or whatever; SIGKILL cannot.

-- Jamie

  reply	other threads:[~2004-04-28 19:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 16:20 filesystem behavior when low on memory and PF_MEMALLOC Steve French
2004-04-27 19:09 ` Bryan Henderson
2004-04-27 20:29   ` filesystem signal handling Steve French
2004-04-28 15:14     ` David Woodhouse
2004-04-28 17:05       ` Trond Myklebust
2004-04-28 17:14         ` David Woodhouse
2004-04-28 17:32           ` Trond Myklebust
2004-04-28 19:28             ` Jamie Lokier [this message]
2004-04-28 19:43               ` Trond Myklebust
2004-04-28 19:47                 ` Jamie Lokier
2004-04-28 20:31                   ` Trond Myklebust
2004-04-29  2:18               ` David Woodhouse
2004-04-29  2:53                 ` Trond Myklebust
2004-04-29  6:41                   ` David Woodhouse
2004-04-29 17:41                     ` Bryan Henderson
2004-04-28 21:46       ` Bryan Henderson
2004-04-29  2:34         ` David Woodhouse

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=20040428192835.GA2836@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfltc@us.ibm.com \
    --cc=trond.myklebust@fys.uio.no \
    /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;
as well as URLs for NNTP newsgroup(s).