-
Notifications
You must be signed in to change notification settings - Fork 121
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
Support for systemd #29
Comments
Would it be preferred to use the user's systemd instance (via the user's config), or is it meant to be installed system-wide? (When installing it system-wide, it could also be put into |
An alternative might be to install a script/symlink into |
I use autorandr from my user home and frankly never put too much thought into this.. just go ahead and create a pull request with your start scripts, I'll merge it. However I'd like to organize the additional scripts/files a bit better. How about moving
and adjusting the makefile to auto-detect the system type and adjust the hotplug-target accordingly?! (We could rename |
👍 |
Are you using udev rules then? AFAIK these cannot be configured in local/user config? |
I have my own udev rule in place, that calls a script from my home, just not the one from the repo ☺ |
👍 |
I've included the service file from this bug now. |
Just curious why there is no
? Does sleep.target include the suspend.target? |
@Konfekt |
systemd does not use pm-utils, so autorandr is not being run after resuming.
The following could be installed into /etc/systemd/system/autorandr-resume.service:
It would also be possible to use the user's systemd instance instead, but
that part seems to in flux currently, with regard to having $DISPLAY and $XAUTHORITY available in there (https://wiki.archlinux.org/index.php/Systemd/User#Environment_variables).
The text was updated successfully, but these errors were encountered: