Accueil > Linux > en cas de problème > systemd

systemd

Publié le 26 avril 2019, dernière mise-à-jour le 19 février 2024, 11 visites, visites totales.

journalctl |grep blue

sudo systemctl status dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled)
   Active: active (running) since Fri 2019-04-26 21:19:42 UTC; 17min ago
     Docs: man:dbus-daemon(1)
 Main PID: 488 (dbus-daemon)
    Tasks: 1 (limit: 4180)
   Memory: 4.5M
   CGroup: /system.slice/dbus.service
           └─488 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

avril 26 21:19:52 ordi dbus-daemon[488]: [system] Successfully activated service 'org.blueman.Mechanism'
avril 26 21:19:52 ordi blueman-mechanism[964]: /usr/lib/blueman/blueman-mechanism:94: PyGIDeprecationWarning: GObject.timeout
                                                 GObject.timeout_add(1000, self.tick)
avril 26 21:19:52 ordi blueman-mechani[964]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
avril 26 21:19:52 ordi blueman-mechanism[964]: loading Network
avril 26 21:19:52 ordi blueman-mechanism[964]: loading RfKill
avril 26 21:19:52 ordi blueman-mechanism[964]: loading Rfcomm
avril 26 21:19:52 ordi blueman-mechanism[964]: loading Ppp
avril 26 21:19:56 ordi dbus-daemon[488]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='
avril 26 21:19:56 ordi dbus-daemon[488]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
avril 26 21:20:22 ordi blueman-mechanism[964]: Exiting

systemd-analyze

Startup finished in 9.632s (kernel) + 17.825s (userspace) = 27.457s 
graphical.target reached after 17.774s in userspace

sudo journalctl -xeu fail2ban.service
sudo systemctl reload fail2ban
sudo systemctl enable fail2ban
sudo systemctl disable fail2ban

[bruno sanchiz]

systemd

Derniers articles modifiés

Linux

Dans la même rubrique