Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41877 - shutdown kills fetchmail and does not try with terminate signal first
Summary: shutdown kills fetchmail and does not try with terminate signal first
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Reported: 2004-02-17 03:17 UTC by Tero Knuutila
Modified: 2004-10-03 11:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Tero Knuutila 2004-02-17 03:17:45 UTC
I start fetchmail in daemon mode everytime I log in to my user (not root) account.
Commandline is "fetchmail --keep -d 500". Before system update everything went well and fetchmail was terminated on logout. With term signal fetchmail cleans after itself removing ~/

Now I have sys-apps/baselayout- and I can see that on shutdown fetchmail is terminated 
with kill --> lockfile is not removed.

I have tried this with several commandlines. Here are results:
- Command "reboot" works and fetchmail is cleanly terminated
- Command "shutdown -r now" does NOT work --> fetchmail is harshly killed and it has no time to clean up.
- Command "halt" does NOT work, same as above

Problem started when I updated my system and sys-apps/baselayout- got

Reproducible: Always
Steps to Reproduce:
1.As normal user: "fetchmail --keep -d 500" 
3."shutdown -r now"

Actual Results:  
After machine boots and I try to start fetchmail it stops because there is
old, obsolete lockfile ~/ After I remove this file I can again
start fetchmail.

I tested with kill how fetchmail works. I learned that when killing with -9 it
does not clean lockfile (this is the case here). When killing with term signal
-15 it cleans lockfile nicely.

I think that other programs are as well killed with -9 on shutdown. But I can't 
prove it. Anyway I think this is a bug anyway. Of course shutdown should try
terminate before harsh killing. 

Expected Results:  
Terminate running programs on shutdown, NOT kill them.

emerge info
Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.0-test11)
System uname: 2.6.0-test11 i686 AMD Duron(tm) processor
Gentoo Base System version
Autoconf: sys-devel/autoconf-2.58
Automake: sys-devel/automake-1.7.7
CFLAGS="-Os -mcpu=i686 -pipe"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-Os -mcpu=i686 -pipe"
FEATURES="autoaddcvs ccache sandbox"
USE="X alsa apm arts avi berkdb bonobo cdr crypt cups encode esd foomaticdb gdbm
gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif
mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt
quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype x86 xml2
xmms xv zlib"
Comment 1 Martin Schlemmer (RETIRED) gentoo-dev 2004-02-19 12:51:10 UTC
Prob the bootsplash related changes.
Comment 2 SpanKY gentoo-dev 2004-10-03 02:12:34 UTC
please try latest baselayout
Comment 3 SpanKY gentoo-dev 2004-10-03 11:04:40 UTC
contacted via e-mail; user has lost his linux

if you have have occassion to test this again, please re-open