tap-vsockd: make sure the service daemonizes properly

This tells start-stop-daemon to run tap-vsockd as a daemon, and tells
tap-vsockd not to daemonize itself. This seems to work more reliably
than when tap-vsockd self-daemonizes.

Signed-off-by: David Scott <dave.scott@docker.com>
This commit is contained in:
David Scott 2016-06-14 15:16:56 +01:00
parent e1ca7e5ab1
commit e99d36784b

View File

@ -21,11 +21,11 @@ start()
ebegin "Starting VPN proxy" ebegin "Starting VPN proxy"
PIDFILE=/var/run/tap-vsockd.pid PIDFILE=/var/run/tap-vsockd.pid
start-stop-daemon --start --quiet \ start-stop-daemon --start \
--exec /sbin/tap-vsockd \ --exec /sbin/tap-vsockd \
--background \
--pidfile ${PIDFILE} \ --pidfile ${PIDFILE} \
-- \ -- \
--daemon \
--pidfile "${PIDFILE}" \ --pidfile "${PIDFILE}" \
--listen --listen