Package: radicale
Version: 3.0.6-3

This bug also affects Devuan (using OpenRC in my case).

Both Radicale's /etc/default/radicale and /etc/init.d/radicale files shipped 
with the respective package are broken. One can't start the daemon using the 
default scripts and settings through the init script.

The patch posted above is not sufficient:

/etc/default/radicale contains a non-existant command line option, and 
starting as well as stopping as well as restarting the daemon through the init 
script doesn't work.

I attached two patches fixing those problems and making Radicale's init script 
and default config work (tested on my OpenRC machine).

It would be very nice if you fixed this! Thanks in advance!
--- /etc/default/radicale.orig	2022-11-16 19:50:24.728659643 +0100
+++ /etc/default/radicale	2022-11-16 19:06:34.394933196 +0100
@@ -5,7 +5,7 @@
 
 # Options for radicale on startup
 # Note that most options can be specified in /etc/radicale/config
-RADICALE_OPTS="--daemon"
+RADICALE_OPTS=""
 
 # Make initscript verbose, override system default
 # (Note: This is ONLY about the initscript!)
--- /etc/init.d/radicale.orig	2022-11-16 19:06:50.714274017 +0100
+++ /etc/init.d/radicale	2022-11-16 19:33:49.998867023 +0100
@@ -68,10 +68,10 @@
 	fi
 
 	start-stop-daemon --start --quiet --startas $DAEMON \
-		--name $NAME --test > /dev/null \
+		--exec $DAEMON --test > /dev/null \
 		|| return 1
-	start-stop-daemon --start --quiet --startas $DAEMON \
-		--name $NAME --umask 0027 --chuid $DAEMON_UID:$DAEMON_GID -- \
+	start-stop-daemon --start --quiet --startas $DAEMON --background \
+		--exec $DAEMON --umask 0027 --chuid $DAEMON_UID:$DAEMON_GID -- \
 		$RADICALE_OPTS \
 		|| return 2
 }
@@ -86,7 +86,7 @@
 	#   1 if daemon was already stopped
 	#   2 if daemon could not be stopped
 	#   other if a failure occurred
-	start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
+	start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --user $DAEMON_UID
 }
 
 case "$1" in

Reply via email to