Use sudo in remoting init.d script to get a clean per-user environment

remoting/host/installer/linux/debian/chrome-remote-desktop.init

 #!/bin/bash
 
 ### BEGIN INIT INFO
 # Provides:             chrome-remote-desktop
 # Required-Start:       $remote_fs $syslog
 # Required-Stop:        $remote_fs $syslog
 # Default-Start:        2 3 4 5
 # Default-Stop:         0 1 6
 # Short-Description:    Chrome Remote Desktop service
 ### END INIT INFO
@@ skipping 38 matching lines @@
 run_and_ignore_error() {
   user=$1
   shift
   exec=$1
   shift
 
   set +e
   if [ "$(whoami)" = "$user" ]; then
     "$exec" "$@"
   else
     shell="$(getent passwd "$user" | cut -d: -f7)"

[Jamie, 2013/06/06 22:13:04]

Remove this line?

[Lambros, 2013/06/07 01:22:17]

Done.

-    USER="$user" LOGNAME="$user" SHELL="$shell" start-stop-daemon \
-      --chuid "$user" --exec "$exec" --start -- "$@"
+    sudo -i -b -u "$user" start-stop-daemon --exec "$exec" --start -- "$@"

[Jamie, 2013/06/06 22:13:04]

According to the man page, the command should follow -i, so please make -i the
last option on the command-line.

[Sergey Ulanov, 2013/06/06 22:22:44]

Why do you still need start-stop-daemon here? 
run_and_ignore_error() is used not only to start the daemon. E.g. do_restart()
expects it to stop service synchronously, so using -i in that case is not right
thing to do.

[Lambros, 2013/06/07 01:22:17]

Done.

[Lambros, 2013/06/07 01:22:17]

Yeah, I don't think start-stop-daemon does anything for us. The Python script
already self-daemonizes and implements the logic for looking up existing
processes.

   fi
 }
 
 do_start() {
   log_begin_msg "Starting Chrome Remote Desktop host for $1..."
   run_and_ignore_error $1 "$HOST_PATH" --start
   log_end_msg $?
 }
 
 do_stop() {
@@ skipping 38 matching lines @@
     for_each_user do_restart
     ;;
 
   *)
     log_success_msg "Usage: /etc/init.d/chrome-remote-desktop" \
         "{start|stop|reload|force-reload|restart}"
     exit 1
 esac
 
 exit 0