-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
nonroot: systemctl --user enable scylla-server.service failed on Ubuntu 18 #7288
Comments
syuu1228
added a commit
to syuu1228/scylla
that referenced
this issue
Sep 28, 2020
On some environment, systemctl enable <service> fails when we use symlink. So just directly copy systemd units to ~/.config/systemd/user, instead of creating symlink. Fixes scylladb#7288
syuu1228
added a commit
to syuu1228/scylla-jmx
that referenced
this issue
Sep 28, 2020
On some environment, systemctl enable <service> fails when we use symlink. So just directly copy systemd units to ~/.config/systemd/user, instead of creating symlink. See scylladb/scylladb#7288
avikivity
pushed a commit
to scylladb/scylla-jmx
that referenced
this issue
Sep 29, 2020
On some environment, systemctl enable <service> fails when we use symlink. So just directly copy systemd units to ~/.config/systemd/user, instead of creating symlink. See scylladb/scylladb#7288
avikivity
added a commit
that referenced
this issue
Sep 29, 2020
* tools/jmx 45e4f28...25bcd76 (1): > install.sh: stop using symlinks for systemd units on nonroot mode Fixes #7288.
This is for systemd user mode. Already on 4.3, not backporting further. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like
systemctl --user enable scylla-server.service
failed because of symbolic link:Even though, symlink seems working:
Maybe we should stop using symlink for this, we can just copy these unit files.
The text was updated successfully, but these errors were encountered: