[[falke]$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
plymouth-quit-wait.service loaded failed failed Wait for Plymouth Boot Screen to Quit
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.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
/code]
un systemctl status me donne :
[code][falke]$ systemctl status plymouth-quit-wait.service
plymouth-quit-wait.service - Wait for Plymouth Boot Screen to Quit
Loaded: loaded (/usr/lib/systemd/system/plymouth-quit-wait.service; static)
Active: failed ([b]Result: timeout[/b]) since jeu. 2013-05-16 18:26:06 CEST; 27min ago
Main PID: 272
CGroup: name=systemd:/system/plymouth-quit-wait.service
1) A quoi sert ce service ? Je n'ai trouvé d'info nulle part
2) Qu'est ce qui peut bien causer l'échec ça semble lié au dépassement d'un délai mais de quoi ? Pourquoi ?
[root@falke_netbook falke]# journalctl -b _PID=272
Error was encountered while opening journal files: Too many open files
Failed to create pager pipe: Too many open files
-- Logs begin at sam. 2013-03-23 16:23:11 CET, end at ven. 2013-05-17 19:10:54 CEST. --
pb de journaux ? j'ai paramétré ceux-ci selon les recommandations de mémoire :