0000770: start-stop-daemon not working without a pidfile

BusyBox Bug and Patch Tracking

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000770

[BusyBox] New Features

minor

always

03-04-06 15:29

02-26-08 08:00

Reporter

ramack

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

unable to reproduce

Status

closed

Product Version

1.01

Summary

0000770: start-stop-daemon not working without a pidfile

Description

if you call
start-stop-daemon --start --exec /sbin/syslogd
syslogd will not be startet. /sbin/syslogd is a softlink to busybox. I guess, stat("/proc/%d/exe", &sb) leads to file statistics equal to stat(name, &exec_stat), in function pid_is_exec of start_stop_deamon.c.
start-stop-deamon is an instance of busybox binary and should start another busybox - the same executable, but with another applet, but it finds itself already running -> start-stop-daemon without --pidfile option doesn't work.

Additional Information

Attached Files

Relationships

Notes
(0001420) bernhardf 06-11-06 11:12	Sounds like fun. Do you by chance have a patch for this at hand?

(0001601) bernhardf 09-02-06 06:55	Ncopa suggests this patch, please test and report back. TIA! http://busybox.net/lists/busybox/2006-August/023949.html [^]

(0005374) vda 02-26-08 08:00	Works for me: # start-stop-daemon --start --exec /bin/syslogd -- --help BusyBox v1.9.0.svn (2007-12-20 23:47:50 GMT) multi-call binary Usage: syslogd [OPTION]... ... pid_is_exec() in svn does not compare stat() data - it compares /proc/PID/exe target with supplied --exec NAME.

Issue History
Date Modified	Username	Field	Change
03-04-06 15:29	ramack	New Issue
03-04-06 15:29	ramack	Status	new => assigned
03-04-06 15:29	ramack	Assigned To	=> BusyBox
06-11-06 11:12	bernhardf	Note Added: 0001420
09-02-06 06:55	bernhardf	Note Added: 0001601
02-26-08 08:00	vda	Status	assigned => closed
02-26-08 08:00	vda	Note Added: 0005374
02-26-08 08:00	vda	Resolution	open => unable to reproduce