Hello,
when I start a child process with fork(), it seems that the new process
runs in the same session as the parent process, due to what loginctl
thinks, even after a call of setsid. Especially, running '/bin/login -f
cpleger' results in the following message in /var/log/auth.log:
pam_systemd(login:session): Not creating session: Already running in a
session or user slice
Does anybody know if and how a child process can be created in a
completely new session, regarding to what pam_systemd and loginctl think
about it?
Viele Grüße
Christoph
