|
Hello,
I am wondering, if it is normal, that systemd is restarting a service, which I as root did stop. In may case it is laptools-mode.
See the output of syslog:
Jul 20 12:16:47 localhost laptop-mode: enabled, not active
Jul 20 12:16:47 localhost laptop_mode[24185]: enabled, not active
Jul 20 12:16:47 localhost systemd[1]: Started Session c34 of user xxxxxxxx.
Jul 20 12:16:48 localhost console-kit-daemon[4349]: console-kit-daemon[4349]: GLib-CRITICAL: Source
ID 642 was not found when attempting to remove it
Jul 20 12:16:48 localhost console-kit-daemon[4349]: GLib-CRITICAL: Source ID 642 was not found when
attempting to remove it
Jul 20 12:16:48 localhost laptop_mode[24185]: /usr/sbin/laptop_mode: 23: /usr/share/laptop-mode-too
ls/modules/lcd-brightness: cannot create /proc/acpi/video/VID/LCD/brightness: Directory nonexistent
Jul 20 12:16:48 localhost laptop-mode: The configured LCD brightness command of the lcd-brightness
module failed.
Jul 20 12:16:48 localhost laptop_mode[24185]: The configured LCD brightness command of the lcd-brig
htness module failed.
Jul 20 12:16:48 localhost laptop-mode: Please check your configuration in /etc/laptop-mode/conf.d/l
cd-brightness.conf.
Jul 20 12:16:48 localhost laptop_mode[24185]: Please check your configuration in /etc/laptop-mode/c
onf.d/lcd-brightness.conf.
Jul 20 12:16:48 localhost laptop-mode: Command failed.
Jul 20 12:16:48 localhost laptop_mode[24185]: Command failed.
Jul 20 12:16:48 localhost systemd[1]: Started Laptop Mode Tools.
Jul 20 12:17:01 localhost CRON[24731]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
I know, I can force systemd, not to start demons at boot, but this behaviour is looking strange. Strange philosophy, I mean.
Maybe it is a bug?
Best regards
Hans
|