[opensuse] cifs.service ignoring /etc/samba/cifstab since recent update
Hi samba gurus. Following a recent update (although I can't say exactly which one), cifs.service has stopped auto mounting samba shares. My samba shares are defined in /etc/samba/cifstab, but running systemctl status cifs.service reports: Mar 16 19:42:28 mako systemd[1]: Starting LSB: Import remote CIFS file systems... Mar 16 19:42:28 mako cifs[11479]: No filesystem of type cifs active in /etc/fstab. ..skipped Mar 16 19:42:28 mako systemd[1]: Started LSB: Import remote CIFS file systems. It seems to be looking only in /etc/fstab, not /etc/samba/cifstab. I can mount the shares successfully running mount (as root) directly from the command line (with the appropriate options as defined in /etc/samba/cifstab. Is there still a valid reason to keep /etc/samba/cifstab, or is the LSB way now to move the contents of that file to /etc/fstab? Thanks in advance, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 16 Mar 2015 20:17:31 Rodney Baker wrote:
Hi samba gurus. Following a recent update (although I can't say exactly which one), cifs.service has stopped auto mounting samba shares.
My samba shares are defined in /etc/samba/cifstab, but running systemctl status cifs.service reports:
Mar 16 19:42:28 mako systemd[1]: Starting LSB: Import remote CIFS file systems... Mar 16 19:42:28 mako cifs[11479]: No filesystem of type cifs active in /etc/fstab. ..skipped Mar 16 19:42:28 mako systemd[1]: Started LSB: Import remote CIFS file systems.
It seems to be looking only in /etc/fstab, not /etc/samba/cifstab. I can mount the shares successfully running mount (as root) directly from the command line (with the appropriate options as defined in /etc/samba/cifstab.
Is there still a valid reason to keep /etc/samba/cifstab, or is the LSB way now to move the contents of that file to /etc/fstab?
Thanks in advance, Rodney.
Sorry - forgot to add, running samba version 4.1.17-2.3-3377-SUSE-oS13.1- x86_64. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rodney Baker wrote:
Is there still a valid reason to keep /etc/samba/cifstab, or is the LSB way now to move the contents of that file to /etc/fstab?
File protections:
llg /etc/passwd -rw-r--r-- 1 root root 11397 Feb 28 16:23 /etc/passwd llg /etc/samba/cifstab -rw-rw---- 1 root Administrators 705 May 11 2013 /etc/samba/cifstab
(assuming you need to supply passworded credentials to access your share(s) as you -- if not, and you don't need to protect the passwds, then maybe not). I did use the indirection thing and store credentials in my ~/.ssh dir for a while, but then ssh sabotaged security and disallowed the NT-security model of allowing files to be owned by a group). Alot of lame linux utils are doing that these days.. like 'group' ownership/access is somehow pointless/ worthless. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 17 Mar 2015 15:51:59 Linda Walsh wrote:
Rodney Baker wrote:
Is there still a valid reason to keep /etc/samba/cifstab, or is the LSB way now to move the contents of that file to /etc/fstab?
----
File protections:
llg /etc/passwd
-rw-r--r-- 1 root root 11397 Feb 28 16:23 /etc/passwd
llg /etc/samba/cifstab
-rw-rw---- 1 root Administrators 705 May 11 2013 /etc/samba/cifstab ---- (assuming you need to supply passworded credentials to access your share(s) as you -- if not, and you don't need to protect the passwds, then maybe not).
Thanks, Linda. Well, I do run my samba network as a domain and use passworded credentials, but this is a home network and nobody else has root access to the machine(s), so I don't really *need* to - I do it purely for learning purposes. :) So, there's no real risk to moving the relevant lines to /etc/fstab, if that is what is required to make it work again. Looks like a few more hours pouring over samba 4 docs required...
I did use the indirection thing and store credentials in my ~/.ssh dir for a while, but then ssh sabotaged security and disallowed the NT-security model of allowing files to be owned by a group). Alot of lame linux utils are doing that these days.. like 'group' ownership/access is somehow pointless/ worthless.
I still find it useful, but mainly to provide multi-user write access to shared data files rather than control access permissions for configs or executables. Again, home network vs corporate network. Mind you, the "wheel" group does come in handy for allowing certain sysadmin tasks to be done by unprivileged users on some Raspberry Pi's that we have dotted around the place doing data collection duties. Regards, Rodney -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Linda Walsh -
Rodney Baker