Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

systemd/user is not supported on CentOS / RHEL #131

Closed
abraunegg opened this issue Aug 18, 2018 · 2 comments
Closed

systemd/user is not supported on CentOS / RHEL #131

abraunegg opened this issue Aug 18, 2018 · 2 comments
Labels
Bug Something isn't working Fixed

Comments

@abraunegg
Copy link
Owner

abraunegg commented Aug 18, 2018 •
edited
Loading

The instructions for running the client under CentOS / RHEL are incorrect as systemd --user is not supported (see: https://drive.google.com/file/d/0B-UWEwsUY5PJS2lnUVJRMGxPZzA/view?pref=2&pli=1)

Support installing onedrive client into the correct places for RHEL / CentOS & the system service running correctly on those systems via systemd:

  • service files in correct place: /etc/systemd/system/
  • fix how config dir is being 'found' as under centos it is being detected as Using Config Dir: /.config/onedrive
  • fix how '~' is being extrapolated out under systemd on CentOS / RHEL
@abraunegg abraunegg added Bug Something isn't working In Progress Currently being worked on labels Aug 18, 2018
abraunegg added a commit that referenced this issue Aug 27, 2018
@abraunegg
Resolve systemd/user is not supported on CentOS / RHEL (Issue #131) (#…
a3f69d4 
…132)

* Resolve systemd/user is not supported on CentOS / RHEL (Issue #131)
@abraunegg
Copy link
Owner Author

PR Merged

@abraunegg abraunegg added Fixed and removed In Progress Currently being worked on labels Aug 27, 2018
@abraunegg abraunegg mentioned this issue Sep 5, 2018
Closed
3 tasks
@lock
Copy link

lock bot commented Jan 5, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Jan 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Bug Something isn't working Fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abraunegg