summaryrefslogtreecommitdiff
path: root/units/systemd-backlight@.service.in
Commit message (Collapse)AuthorAge
* units: so far we defaulted to 90s as default timeout for most things, let's ↵Lennart Poettering2015-02-02
| | | | | | do so for our oneshot services too Fewer surprises, and stuff...
* units: set TimeoutSec on some oneshot servicesZbigniew Jędrzejewski-Szmek2015-02-01
| | | | | | | | | | Services which are not crucial to system bootup, and have Type=oneshot can effectively "hang" the system if they fail to complete for whatever reason. To allow the boot to continue, kill them after a timeout. In case of systemd-journal-flush the flush will continue in the background, and in the other two cases the job will be aborted, but this should not result in any permanent problem.
* readahead: wipe out readaheadDaniel Buch2014-09-25
|
* units: Do not unescape instance name in systemd-backlight@.serviceThomas Bächler2014-03-07
| | | | | | | The instance name is never escaped in the udev rule, but unescaped in the unit. This results in the following error message on Asus boards: Failed to get backlight or LED device 'backlight:eeepc/wmi': No such file or directory
* fix lingering references to /var/lib/{backlight,random-seed}Dave Reisner2013-10-02
| | | | This should have been part of ef5bfcf668e6029faa78534dfe.
* backlight: instead of syspath use sysname for identifying backlight devicesLennart Poettering2013-08-14
| | | | This makes the description string of the backlight service a bit nicer.
* backlight: add minimal tool to save/restore screen brightness across rebootsLennart Poettering2013-08-14
As many laptops don't save/restore screen brightness across reboots, let's do this in systemd with a minimal tool, that restores the brightness as early as possible, and saves it as late as possible. This will cover consoles and graphical logins, but graphical desktops should do their own per-user stuff probably. This only touches firmware brightness controls for now.