Dropbox and systemd issues...

Question

Hello!
I've installed Dropbox from the AUR, and am starting it for my user using sytemd (sytemctl enable [email protected]).
It works fine, but it seems that the actual dropboxd executable only executes a "local one" from my home directory (~/.dropbox-dist/dropbox).
This seems to cause systemd trying to restart it all over again, which has to fail as dropbox is already running...
In journalctl, this looks like
Apr 05 13:03:07 thorin systemd[1]: [email protected]: main process exited, code=killed, status=9/KILL
Apr 05 13:03:07 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:07 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:08 thorin dropboxd[682]: Another instance of Dropbox (592) is running!
Apr 05 13:03:09 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:09 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:09 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:10 thorin dropboxd[738]: Another instance of Dropbox (592) is running!
Apr 05 13:03:10 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:10 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:10 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:11 thorin dropboxd[768]: Another instance of Dropbox (592) is running!
Apr 05 13:03:11 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:11 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:11 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:11 thorin dropboxd[805]: Another instance of Dropbox (592) is running!
Apr 05 13:03:11 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:11 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:12 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:12 thorin dropboxd[836]: Another instance of Dropbox (592) is running!
Apr 05 13:03:12 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:12 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:13 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:13 thorin systemd[1]: [email protected] start request repeated too quickly, refusing to start.
Apr 05 13:03:13 thorin systemd[1]: Unit [email protected] entered failed state
Did I do wrong? If yes, could you help me out here and tell me what I shoud do instead? E.g. start dropboxd usint .xinitrc/.xsession?
Thanks in advance!

Answer 1

I don't know why, but on my home server systemd launch ~/.dropbox-dist/dropbox too.
I just remove all (exclude ~/.dropbox and ~/Dropbox folders) off old versions files from $HOME, /opt and /usr (include /usr/lib/systemd/system/dropbox*) and reinstall dropbox with yaourt. Then `sudo systemctl start dropbox@$USER.service` work normally
Last edited by Felixoid (2013-04-05 14:45:51)