Pour ma part, systemd fonctionne très bien. C'est :
- facile à configurer ( sudo systemctl enable/disable , et voilà! On peut faire un start/ restart/ stop ensuite si on est pressé),
- facile de surveiller (d'autant que systemctl accepte de nombreux filtres en arguments) :
> $ systemctl
> UNIT LOAD ACTIVE SUB JOB DESCRIPTION
> proc-sys…misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
[…]
> cronie.service loaded active running Periodic Command Scheduler
> cups.service loaded active running CUPS Printing Service
> dbus.service loaded active running D-Bus System Message Bus
> getty@tty1.service loaded active running Getty on tty1
> lightdm.service loaded active running LightDM Display Manager
> network.service loaded active running Legacy unit for network
> NetworkManager.service loaded active running Network Manager
> rc-local.service loaded active exited /etc/rc.local Compatibility
> syslog-ng.service loaded active running System Logger Daemon
> systemd-journald.service loaded active running Journal Service
> systemd-logind.service loaded active running Login Service
> systemd-…s-load.service loaded active exited Load Kernel Modules
> systemd-…unt-fs.service loaded active exited Remount Root and Kernel File Systems
> systemd-sysctl.service loaded active exited Apply Kernel Variables
> systemd-…-setup.service loaded active exited Recreate Volatile Files and Directories
> systemd-…rigger.service loaded active exited udev Coldplug all Devices
> systemd-udevd.service loaded active running udev Kernel Device Manager
> systemd-…ssions.service loaded active exited Permit User Sessions
> systemd-…-setup.service loaded active exited Setup Virtual Console
> udisks2.service loaded active running Storage Daemon
> upower.service loaded active running Daemon for power management
> wpa_supplicant.service loaded active running WPA supplicant
> cups.socket loaded active running CUPS Printing Service Sockets
> dbus.socket loaded active running D-Bus System Message Bus Socket
> syslog.socket loaded active running Syslog Socket
> systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
> systemd-journald.socket loaded active running Journal Socket
> systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
> systemd-…control.socket loaded active listening udev Control Socket
> systemd-…-kernel.socket loaded active running udev Kernel Socket
> arch-daemons.target loaded active active Arch Daemons
> basic.target loaded active active Basic System
> bluetooth.target loaded active active Bluetooth
> cryptsetup.target loaded active active Encrypted Volumes
> getty.target loaded active active Login Prompts
> graphical.target loaded active active Graphical Interface
> local-fs-pre.target loaded active active Local File Systems (Pre)
> local-fs.target loaded active active Local File Systems
> multi-user.target loaded active active Multi-User
> network.target loaded active active Network
> remote-fs.target loaded active active Remote File Systems
> sockets.target loaded active active Sockets
> sound.target loaded active active Sound Card
> swap.target loaded active active Swap
> sysinit.target loaded active active System Initialization
> syslog.target loaded active active Syslog
> systemd-…es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
>
> LOAD = Reflects whether the unit definition was properly loaded.
> ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
> SUB = The low-level unit activation state, values depend on unit type.
> JOB = Pending job for the unit.
>
> 76 loaded units listed. Pass --all to see loaded but inactive units, too.
> To show all installed unit files use 'systemctl list-unit-files'.
(sans oublier la commande journalctl),
- bien plus rapide que SysV (même sur un SSD),
- fiable (au contraire de udev),
- largement documenté ( man systemctl, man systemd, man journalctl).
"Quand certains râlent contre systemd, d'autres s'attaquent aux vrais problèmes." (merci Sinma !)
[^] # Re: systemd ! Tant de complexité pour un moins bon fonctionnement...
Posté par xcomcmdr . En réponse au journal Archlinux va passer à systemd : appel à volontaire pour maintenir SysVinit. Évalué à -1.
Pour ma part, systemd fonctionne très bien. C'est :
- facile à configurer ( sudo systemctl enable/disable , et voilà! On peut faire un start/ restart/ stop ensuite si on est pressé),
- facile de surveiller (d'autant que systemctl accepte de nombreux filtres en arguments) :
> $ systemctl
> UNIT LOAD ACTIVE SUB JOB DESCRIPTION
> proc-sys…misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
[…]
> cronie.service loaded active running Periodic Command Scheduler
> cups.service loaded active running CUPS Printing Service
> dbus.service loaded active running D-Bus System Message Bus
> getty@tty1.service loaded active running Getty on tty1
> lightdm.service loaded active running LightDM Display Manager
> network.service loaded active running Legacy unit for network
> NetworkManager.service loaded active running Network Manager
> rc-local.service loaded active exited /etc/rc.local Compatibility
> syslog-ng.service loaded active running System Logger Daemon
> systemd-journald.service loaded active running Journal Service
> systemd-logind.service loaded active running Login Service
> systemd-…s-load.service loaded active exited Load Kernel Modules
> systemd-…unt-fs.service loaded active exited Remount Root and Kernel File Systems
> systemd-sysctl.service loaded active exited Apply Kernel Variables
> systemd-…-setup.service loaded active exited Recreate Volatile Files and Directories
> systemd-…rigger.service loaded active exited udev Coldplug all Devices
> systemd-udevd.service loaded active running udev Kernel Device Manager
> systemd-…ssions.service loaded active exited Permit User Sessions
> systemd-…-setup.service loaded active exited Setup Virtual Console
> udisks2.service loaded active running Storage Daemon
> upower.service loaded active running Daemon for power management
> wpa_supplicant.service loaded active running WPA supplicant
> cups.socket loaded active running CUPS Printing Service Sockets
> dbus.socket loaded active running D-Bus System Message Bus Socket
> syslog.socket loaded active running Syslog Socket
> systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
> systemd-journald.socket loaded active running Journal Socket
> systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
> systemd-…control.socket loaded active listening udev Control Socket
> systemd-…-kernel.socket loaded active running udev Kernel Socket
> arch-daemons.target loaded active active Arch Daemons
> basic.target loaded active active Basic System
> bluetooth.target loaded active active Bluetooth
> cryptsetup.target loaded active active Encrypted Volumes
> getty.target loaded active active Login Prompts
> graphical.target loaded active active Graphical Interface
> local-fs-pre.target loaded active active Local File Systems (Pre)
> local-fs.target loaded active active Local File Systems
> multi-user.target loaded active active Multi-User
> network.target loaded active active Network
> remote-fs.target loaded active active Remote File Systems
> sockets.target loaded active active Sockets
> sound.target loaded active active Sound Card
> swap.target loaded active active Swap
> sysinit.target loaded active active System Initialization
> syslog.target loaded active active Syslog
> systemd-…es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
>
> LOAD = Reflects whether the unit definition was properly loaded.
> ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
> SUB = The low-level unit activation state, values depend on unit type.
> JOB = Pending job for the unit.
>
> 76 loaded units listed. Pass --all to see loaded but inactive units, too.
> To show all installed unit files use 'systemctl list-unit-files'.
(sans oublier la commande journalctl),
- bien plus rapide que SysV (même sur un SSD),
- fiable (au contraire de udev),
- largement documenté ( man systemctl, man systemd, man journalctl).
"Quand certains râlent contre systemd, d'autres s'attaquent aux vrais problèmes." (merci Sinma !)