You are not logged in.
Hello!
I have setup a devuan (chimaera) system using kvm.
I am planning to have the users home directory residing on a cifs share.
I try to mount is in fstab like this (where ncu9/2009 is the user):
//192.168.26.1/kvmabc-homes--ncu2 /home/ncu9 cifs _netdev,user,mfsymlinks,rw,exec,dev,suid,user_xattr,vers=1.0,username=mbu-smb1,password=123,iocharset=utf8,uid=2009,gid=100,dir_mode=0755,file_mode=0755 0 0
It does not mount on users login.
If I am issuning a "mount -a" as root, it mounts and if the users logs in after this,
everything is ok at a first glance (debating with samba group about missing exec/dev options).
Any tip would be great.
I found hints about a pam.*mount module in the past, but there is nothing on
my devuan-vm and event in the repository.
Manfred
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.
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.
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.
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
Hallo!
I have the same problem.
The answer does'nt fit.
I have ipv6 disabled on all computers (acp-cacher-ng, proxy, chimera-host).
Just to be sure, I applied the same settings like in your answer, but no changes.
Additionally, on the chimera-box I have a lxc-container (running debian buster), which updates fine.
I found a similar post regarding ubuntu and then, I made a try to load one of the failing urls
using curl over acng:.
curl -p http://192.168.12.132:4455 http://pkgmaster.devuan.org/merged/pool/DEBIAN-SECURITY/updates/main/x/xorg-server/xvfb_1.20.11-1%2bdeb11u2_amd64.deb
curl: (56) Received HTTP code 403 from proxy after CONNECT
Went to the acng-box and I see the response from the final squid-proxy and I get:
<p>Some aspect of the requested URL is incorrect.</p>
<p>Some possible problems are:</p>
<ul>
<li><p>Missing or incorrect access protocol (should be <q>http://</q> or similar)</p></li>
<li><p>Missing hostname</p></li>
<li><p>Illegal double-escape in the URL-Path</p></li>
<li><p>Illegal character in hostname; underscores are not allowed.</p></li>
</ul>
Changing apt-settings from acng to squid, doing update, changing back to acng following an upgrade
works.
There were wrong urls/hostnames in the apt-sources (which were probably very old, because
it is an experiment (which I use to see devuan instead of debian/systemd).
Hope this helps someone, wo felt over this too.
Regards,
Manfred