Gnus development mailing list
 help / color / mirror / Atom feed
From: David Coe <davidc@debian.org>
Cc: ding@gnus.org, 200823-forwarded@bugs.debian.org
Subject: Re: gnus: apparently kills external viewers too aggressively
Date: Tue, 26 Aug 2003 13:58:50 -0400	[thread overview]
Message-ID: <86k790b8rp.fsf@someotherplace.org> (raw)
In-Reply-To: <ilusmnv7vy1.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 21 Aug 2003 01:25:58 +0200")

Simon Josefsson <jas@extundo.com> writes:

> Can you strace or gdb display to see what signal it receives?  Or
> perhaps simply start display on the command line and see if it leaves
> a shared segment around if you SIGKILL or SIGTERM it?

Yes, display does leave the segments allocated when it's SIGKILLed,
and doesn't when it's SIGTERMed.  See Debian Bug#207379 against
imagemagick ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=207379 ).  
shmctl(2) does say that the creator of a segment *must* ensure
that the segment is eventually destroyed, so this does look like a bug
in imagemagick.

I don't know whether it would be too much overhead for
gnus to try SIGTERM before SIGKILL; I leave that up to you --
as I'm sure you know, many programs don't (or can't) clean up after 
themselves as well as they should when KILLed.

Thanks for gnus!



  reply	other threads:[~2003-08-26 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 18:17 Manoj Srivastava
2003-08-20 23:25 ` Simon Josefsson
2003-08-26 17:58   ` David Coe [this message]
2003-08-27  1:47     ` Simon Josefsson
2003-08-27  4:55       ` David Coe
2003-08-27  6:03         ` Simon Josefsson

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=86k790b8rp.fsf@someotherplace.org \
    --to=davidc@debian.org \
    --cc=200823-forwarded@bugs.debian.org \
    --cc=ding@gnus.org \
    /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).