Your message dated Thu, 08 Jul 2004 21:36:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Not a bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Jun 2004 04:13:24 +0000
>From [EMAIL PROTECTED] Mon Jun 28 21:13:24 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (localhost) [65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bf9zo-0001NU-00; Mon, 28 Jun 2004 21:13:24 -0700
Received: by localhost (Postfix, from userid 1000)
id 087F868C028; Mon, 28 Jun 2004 23:13:23 -0500 (EST)
Content-Type: multipart/mixed; boundary="===============1597660998=="
MIME-Version: 1.0
From: Branden Robinson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: dpkg: [S-S-D] start-stop-daemon fails to --stop
X-Mailer: reportbug 2.62
Date: Mon, 28 Jun 2004 23:13:22 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============1597660998==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: dpkg
Version: 1.10.22
Severity: normal
File: /sbin/start-stop-daemon
I have written xdm's maintainer and init scripts such that it can be
configured to not kill the daemon on package upgrade.
This works, except that if the xdm package has been upgraded since it
was last started, start-stop-daemon reports failure to stop it by
exiting with a nonzero status.
Please see the following typescript (with control sequence garbage
edited out). I added set -x to xdm's init script so it would be more
clear what's going on.
I'm also attaching xdm's init script so you can have a look at what
it's doing.
Script started on Mon Jun 28 23:00:28 2004
$TERM is "linux".
Not using UTF-8 environment.
sisyphus:~# ps -C xdm
PID TTY TIME CMD
19004 ? 00:00:00 xdm
19007 ? 00:00:00 xdm
sisyphus:~# cat /var/run/xdm.pid
19004
sisyphus:~# ls /var/run
Xprint_servers dhclient.eth0.leases lpd.pid screen utmp
apache2 dhclient.eth0.pid ntpd.pid sshd xdm.pid
atd.pid exim4 pppconfig sshd.pid xfs.pid
crond.pid inetd.pid ptal-mlcd syslogd.pid
crond.reboot klogd.pid ptal-printd usb
sisyphus:~# dpkg -i
/home/branden/packages/xfree86/4.3.0-testing2/xdm_4.3.0.dfsg..1-5+SVN_powerpc.deb
(Reading database ... 102528 files and directories currently installed.)
Preparing to replace xdm 4.3.0.dfsg.1-5+SVN (using
.../xdm_4.3.0.dfsg.1-5+SVN_powerpc.deb) ...
Unpacking replacement xdm ...
Setting up xdm (4.3.0.dfsg.1-5+SVN) ...
System startup links for /etc/init.d/xdm already exist.
sisyphus:~# ls /var/run
Xprint_servers dhclient.eth0.leases lpd.pid screen utmp
apache2 dhclient.eth0.pid ntpd.pid sshd xdm.pid
atd.pid exim4 pppconfig sshd.pid xfs.pid
crond.pid inetd.pid ptal-mlcd syslogd.pid
crond.reboot klogd.pid ptal-printd usb
sisyphus:~# ps -C xdm
PID TTY TIME CMD
19004 ? 00:00:00 xdm
19007 ? 00:00:00 xdm
sisyphus:~# cat /var/run/xdm.pid
19004
sisyphus:~# invoke-rc.d xdm stop
+ HEED_DEFAULT_DISPLAY_MANAGER=true
+ DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
+ PATH=/bin:/usr/bin:/sbin:/usr/sbin
+ DAEMON=/usr/bin/X11/xdm
+ PIDFILE=/var/run/xdm.pid
+ UPGRADEFILE=/var/run/xdm.upgrade
+ test -x /usr/bin/X11/xdm
+ '[' -e /var/run/xdm.upgrade ']'
+ SSD_ARGS=--pidfile /var/run/xdm.pid --exec /usr/bin/X11/xdm
+ echo -n 'Stopping X display manager: xdm'
Stopping X display manager: xdm+ '[' '!' -f /var/run/xdm.pid ']'
++ cat /var/run/xdm.pid
++ tr -d '[:blank:]'
+ DAEMONPID=19004
+ KILLCOUNT=1
+ '[' '!' -e /var/run/xdm.upgrade ']'
+ start-stop-daemon --stop --quiet --pidfile /var/run/xdm.pid --exec
/usr/bin/X11/xdm
+ echo -n ' not running'
not running+ '[' 1 -le 5 ']'
+ stillrunning
++ cat /proc/19004/cmdline
+ expr /usr/bin/X11/xdm : /usr/bin/X11/xdm
+ true
+ kill 19004
+ sleep 1
+ KILLCOUNT=2
+ '[' 2 -le 5 ']'
+ stillrunning
++ cat /proc/19004/cmdline
+ expr '' : /usr/bin/X11/xdm
+ rm -f /var/run/xdm.pid /var/run/xdm.upgrade
+ false
+ break
+ stillrunning
++ cat /proc/19004/cmdline
+ expr '' : /usr/bin/X11/xdm
+ rm -f /var/run/xdm.pid /var/run/xdm.upgrade
+ false
+ rm -f /var/run/xdm.upgrade
+ echo .
