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

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

Index: remoting/host/installer/linux/debian/chrome-remote-desktop.init
diff --git a/remoting/host/installer/linux/debian/chrome-remote-desktop.init b/remoting/host/installer/linux/debian/chrome-remote-desktop.init
index 4230632e8131f5880f32e0c1aa366dc4ff1a2be7..a424824061fabfa55046602a4b8500940f8e3c59 100755
--- a/remoting/host/installer/linux/debian/chrome-remote-desktop.init
+++ b/remoting/host/installer/linux/debian/chrome-remote-desktop.init
@@ -57,8 +57,7 @@ run_and_ignore_error() {
     "$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
 }