Am Dienstag, dem 25.05.2021 um 22:23 +0800 schrieb 吾为男子:
> Systemd provides pam_systemd.so for PAM module and for many commands,
> such as su command, pam_systemd.so will be called and the process
> will be moved to the cgroup that systemd managed.
Regardless your problem, `su` is never the solutio
On Di, 25.05.21 22:23, 吾为男子 (csren...@qq.com) wrote:
> Systemd provides pam_systemd.so for PAM module and for many
> commands, such as su command, pam_systemd.so will be called and the
> process will be moved to the cgroup that systemd managed.
>
> Generally, if we move the bash process from its r
Systemd provides pam_systemd.so for PAM module and for many commands, such as
su command, pam_systemd.so will be called and the process will be moved to the
cgroup that systemd managed.
Generally, if we move the bash process from its related session cgroup created
by systemd under /sys/fs/cg
On Di, 25.05.21 12:32, Mantas Mikulėnas (graw...@gmail.com) wrote:
> Hi,
>
> As you might've heard, the freenode IRC network is suddenly under new
> ownership. Neither the process nor the result are making many people
> comfortable, so the old staff collectively packed up and left to start a
> new
Hi,
As you might've heard, the freenode IRC network is suddenly under new
ownership. Neither the process nor the result are making many people
comfortable, so the old staff collectively packed up and left to start a
new network in its place, with many channels either following them to the
new plac
