From ArchWiki
Revision as of 12:18, 10 June 2013 by Fengchao (talk | contribs) (Remove closed discussions.)
Jump to: navigation, search

Explaining how to start dropbox for all users in systemd

I do not know how to do this, but I think it has to do with the User info. Could this be explained propperly? Simply removing the User= statements has some strange behaviour (as I have tried this and it makes dropbox startup together with gdm).

Can we add multiple usernames? Or disable it for root only? What would be the best way forward?

Dropbox in systemd --user

I had trouble with dropbox not starting correctly in systemd --user. There were 2 problems:

  • /usr/bin/dropboxd apparently forks off a child daemon. I couldn't find how to start the daemon without forking.
  • /usr/bin/dropboxd exits with status code 9/KILL. This makes systemd kill its control-group and thereby its child (the daemon) too.

The original dropbox@.service did not work for me because of these two issues. Stopping dropboxd with systemd also did not work before.

To fix this I have the following in $HOME/.config/systemd/user/dropbox.service:


Type=forking                                   # dropboxd forks off to a daemon and isn't itself long-running
ExecStart=/bin/sh -c '/usr/bin/dropboxd; true' # dropboxd always exists with 9, so just ignore the exit code
KillMode=process                               # Upon exiting, kill the process, not the control-group


The DISPLAY environment is already in the environment, so Environment=DISPLAY=:0 is not needed. Also, this service does not detect when dropbox exited; I'm not sure how to fix this at the moment. Input on this is appreciated.

please sign your post with ~~~~ next time
read manpage systemd.service(5), especially SuccessExitStatus and KillSignal might be useful
btw. this [1] works for me...
-- Lahwaacz (talk) 13:46, 7 June 2013 (UTC)