-
Notifications
You must be signed in to change notification settings - Fork 15
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
Can't invoke systemctl --user. #18
Comments
Hi @tommyvdv u guessed correct. Currently the lib does not support the parameter I will mark this as enhancement and will try to implement it asap :) |
Additional information: https://wiki.archlinux.org/index.php/Systemd/User |
Hi @icanhazstring |
@tommyvdv is just pushed a commit into dev branch
You can switch the scope with each call. Just remember to use You can check this out by using current dev branch.
Hope this works for you. I will try to finish the next milestone coming this weekend and tag the finished v1.0. |
Hi @tommyvdv can you confirm the implementation. So i can close the issue. And possibly tag a release for it. |
I've tried to test this on an ubuntu 16.04 box but can't confirm it's working. Running the commands directly I can retrieve a couple of services like
I'm probably going about this the wrong way but in case I'm not; hope this helps. |
Hm. Thanks for the feedback tho. I will look into this. |
Good news @tommyvdv. I probably found out what went wrong. Bad news tho, I discovered some minor other bugs on the way which need attention as well ;) |
I'm no expert on systemctl or its related technology, far from it.
I do know that
systemctl
andsystemctl --user
are two separated concepts on the linux distro I'm working with.At first glance it doesn't seem possible to add the option
user
to the command.Running
->getService('test')
works if the unittest
is configured as a system unit.$ systemctl status test
Running
->getService('test')
works if the unittest
is configured as a user unit but throws an (expected)UnitNotFoundException
exception.$ systemctl --user status test
I hope this is on the road map or, better yet, I'm just missing the obvious solution.
The text was updated successfully, but these errors were encountered: