ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014031ClearOSapp-user-dropbox - Dropbox for Userspublic2017-03-25 01:242017-04-06 10:43
Reportertrialanderror 
Assigned Tobchambers 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionunable to reproduce 
PlatformOSOS Version
Product Version7.3.1 
Target VersionFixed in Version 
Summary0014031: dropbox does not start on boot
Descriptiondropbox does not start on boot

/etc/init.d/dropbox missing therefore all links under /etc/rc_.d point to nothing.

systemctl list-all-unit-files does not list the per user services therefore they cannot be (re-)started with systemctl restart dropbox@*

Might concern Issue # 0006241, 0012911



Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-03-25 01:24trialanderrorNew Issue
2017-03-25 10:59bchambersNote Added: 0005211
2017-04-06 10:42bchambersNote Added: 0005241
2017-04-06 10:43bchambersStatusnew => closed
2017-04-06 10:43bchambersAssigned To => bchambers
2017-04-06 10:43bchambersResolutionopen => unable to reproduce

Notes
(0005211)
bchambers   
2017-03-25 10:59   
Hmm...the correct unit files for individual Dropbox-enabled users gets created here:

/etc/systemd/system/multi-user.target.wants

and symlinked to the Dropbox unit file.

I guess I'm misunderstanding something on how systemd works...

Can confirm, though...Dropbox will not start up individual user accounts on reboot.
(0005241)
bchambers   
2017-04-06 10:42   
Update...I actually cannot confirm this bug. All tests after checking my home server shows Dropbox @user.service instances start on boot.