SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-22 05:10 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0014031	ClearOS	app-user-dropbox - Dropbox for Users	public	2017-03-25 01:24	2017-04-06 10:43
Reporter	trialanderror
Assigned To	bchambers
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	unable to reproduce
Platform		OS		OS Version
Product Version	7.3.1
Target Version		Fixed in Version
Summary	0014031: dropbox does not start on boot
Description	dropbox 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
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0005211) bchambers (administrator) 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 (administrator) 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.

Notes

Issue History
Date Modified	Username	Field	Change
2017-03-25 01:24	trialanderror	New Issue
2017-03-25 10:59	bchambers	Note Added: 0005211
2017-04-06 10:42	bchambers	Note Added: 0005241
2017-04-06 10:43	bchambers	Status	new => closed
2017-04-06 10:43	bchambers	Assigned To	=> bchambers
2017-04-06 10:43	bchambers	Resolution	open => unable to reproduce

Issue History