Hallo zusammen,
eine kleine Warnung am Rande:
Beim letzten Tumbleweed snapshot gab es wohl ein paar Probleme in Sachen pam_config und systemd:
Alles anzeigenHi everybody,
Many of you already reached out to report issues with this snapshot,
which openQA sadly did not spot....
We started analysing this and it seems the above package is the reason
for the failure...
In all cases we received so far to investigate, pam_systemd was missing
in the configuration, which results in many side effects:
* user.slice not being used - hence the user is limited to system.scope
and that's 512 children (not sufficient for a normal session, resulting
in forking issues)
* GNOME/GDM users don't get an X-Session at all: gdm starts X as user
(unlike all other DMs, that start as root) - for this to work,
systemd/logind needs to pass the permissions to it. without
pam_systemd. this passing on is missing.
It should be rather simple to recover from it by issuing the command:
pam-config --add --systemd
But please compare your /etc/pam.d/common* files to integrate possibly
other missing service definitions too
Cheers,
Dominique
Der Spaß führte bei mir u.a. dazu, dass mir teilweise Prozesse gestorben sind, weil sie nicht mehr "forken" konnten. Beispiel Bash:
HTH!