You are not logged in.
Hello!
In the beginning, I was a fan of systemd, even I haven't know to use it, because
I never understood systemv (init-system).
Now, on debian (for several years), I am facing on this and that problems, which seem
to be systemd related.
I have a KVM guest with several accounts.
Astoundingly, each of this have processes running after boot and
independent, if they are logged in or not.
This is problematic, because for some users, I use a homedir which
resides on cifs/smb. On the host, these are zfs filesystems which I want
to snapshot and I wish, that all processes are terminated. For the moment,
I kill them und force unmount by root.
The question is, how this behaves on Devuan.
Thanks so far,
Manfred
Offline
I think that user process behaviour is dependent on the KillUserProcesses option in logind.conf so it can be disabled under both systemd (/etc/systemd/logind.conf) or sysvinit/elogind (/etc/elongind/logind.conf) by setting that to yes.
So I think the behaviour would be the same under both init systems. Perhaps try it and report back? I might be wrong.
Brianna Ghey — Rest In Power
Offline
Hi,
thank you.
I think that user process behaviour is dependent on the KillUserProcesses option in logind.conf so it can be disabled under both systemd (/etc/systemd/logind.conf) or sysvinit/elogind (/etc/elongind/logind.conf) by setting that to yes.
So I think the behaviour would be the same under both init systems. Perhaps try it and report back? I might be wrong.
I've already read and tried this (using the "exclude root" option) - but with different success, so the question
came up for me. The remaining processes are something like gfvs.*
You implicitely said, under systemV/etc this is not the case?
I have a lot of computers, am a linux-noob (nearly), countless VMs (kvm+lxc)
and would not be able to migrate that all fast, but were probably unable to work
with different systems.
Offline
You implicitely said, under systemV/etc this is not the case?
No.
Brianna Ghey — Rest In Power
Offline
Wouldn't you just find the service associated with the process and un-check that service's annoying run-levels with 'sudo sysv-rc-conf'?
Maybe I'm being dense and this has nothing to do with services. But this is usually one of the first places I look to get misbehaving autostart processes under control.
Offline
Or just purge that GVFS shite.
Brianna Ghey — Rest In Power
Offline
Hallo!
Thanks, but there is nothing like this on my debian!
I just beginning from scratch using devuan and even there, there is nothing like this.
On devuan, gvfs is installed, but not active running.
Manfred
Wouldn't you just find the service associated with the process and un-check that service's annoying run-levels with 'sudo sysv-rc-conf'?
Maybe I'm being dense and this has nothing to do with services. But this is usually one of the first places I look to get misbehaving autostart processes under control.
Offline
Hi!
Comes to my mind, but must learn about it first.
Probably I need it on that debian-vm.
Manfred
Or just purge that GVFS shite.
Offline
Hallo!
Thanks, but there is nothing like this on my debian!
I just beginning from scratch using devuan and even there, there is nothing like this.
On devuan, gvfs is installed, but not active running.Manfred
andyprough wrote:Wouldn't you just find the service associated with the process and un-check that service's annoying run-levels with 'sudo sysv-rc-conf'?
Maybe I'm being dense and this has nothing to do with services. But this is usually one of the first places I look to get misbehaving autostart processes under control.
sudo apt install sysv-rc-conf maybe?
Offline