From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10661] New: /etc/init.d/S29netplug starts multiple instances of netplugd
Date: Mon, 22 Jan 2018 12:48:24 +0000 [thread overview]
Message-ID: <bug-10661-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10661
Bug ID: 10661
Summary: /etc/init.d/S29netplug starts multiple instances of
netplugd
Product: buildroot
Version: 2017.11.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mail2k at web.de
CC: buildroot at uclibc.org
Target Milestone: ---
If you execute the command "/etc/init.d/S29netplug start" multiple times, you
get multiple instances of netplugd.
This is not the desired behaviour. We should only have one running netplugd.
The change has to be made in package/netplug/S29netplug:
line 46:
- start-stop-daemon -S -q -p /var/run/netplugd.pid -x /sbin/netplugd
${NETPLUGDARGS}
+ start-stop-daemon -S -q -x /sbin/netplugd -- -p /var/run/netplugd.pid
${NETPLUGDARGS}
Reason:
If the start-stop-daemon gets the parameter -p /var/run/netplug.pid it will try
to identify a running process by this pid-file but the file doesn't exist. As a
result, every call of "/etc/init.d/S29netplug start" starts a new netplugd.
--> The parameter -p /var/run/netplug.pid must be passed to netplugd.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-01-22 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 12:48 bugzilla at busybox.net [this message]
2018-06-06 13:28 ` [Buildroot] [Bug 10661] /etc/init.d/S29netplug starts multiple instances of netplugd bugzilla at busybox.net
2018-06-06 16:35 ` bugzilla at busybox.net
2018-06-07 1:39 ` bugzilla at busybox.net
2018-06-07 14:21 ` bugzilla at busybox.net
2018-06-18 11:07 ` bugzilla at busybox.net
2018-06-21 18:07 ` bugzilla at busybox.net
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=bug-10661-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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