On Fri, Feb 10, 2012 at 12:52:51PM +0100, Andreas wrote:
Am 10.02.2012 12:14, schrieb Lars Müller:
On Fri, Feb 10, 2012 at 12:00:22PM +0100, Andreas wrote:
Then I entered apparently suitable lines in /etc/samba/cifstab but the shares aren't automatically mounted on boot time. How does your /etc/samba/cifstab look like?
//192.168.0.210/e /mnt/backup_extern cifs username=x,password=y //192.168.0.211/updates /mnt/updates cifs username=x,password=y
I tried rccifs status and got "running" though yast shows it as not running. And it listed the 2 shares I mounted manually.
rccifs stop unmounts both shares but rccifs start mounts only the first though the lines look the same. Am I missing some detail? Why is the 2nd line ignored?
I have no clue. Please check /var/log/messages (syslog) if you find there any complain. As you're usinf IP addresses and no names it can't be an DNS issue.
This is ignored. Nothing gets mounted and there is no error in the smb.log.
I found a refernce that I need to start the cifs service in Yast-->Runlevel. I set it to runlevel 3+5 and tried to start it imediatly in yast. When I try this I get the error : /etc/init.d/cifs start returned 6 (program not configured)
Can someon point me in the right direction, please? 6 (program not configured) as defined in /etc/init.d/skeleton we return in the case when /etc/fstab has no cifs mount point configured and if there is no /etc/samba/cifstab file. I've got no cifs mounts sin fstab but /etc/samba/cifstab exists.
This smells more and more like a bug. :/
Please check via bash -x /etc/init.d/cifs
I did and it dumped some stuff that doesn't give me a clue. Is there a special part to look at?
You are using systemd? If ls -l /sbin/init shows ../bin/systemd, then the answer is yes. Can you please give the following commands a try: systemctl status cifs.service If this reports an active service please call next: systemctl stop cifs.service and then: systemctl start cifs.service If inactive (dead) was reported as on the status request call the latter two commands the other way around. In between follow all the time /var/log/messages via tail -f and please report the lines you get printed on screen via bugzilla. Then quote the bug ID here as cross reference.
Btw. there are a lot of errors in /var/log/messages coming roughly every minute like:
Feb 10 12:25:01 mybox kernel: [104270.254182] CIFS VFS: Received no data, expecting 4
This might be caused by your cifs server. Is this a recent recent Linux kernel based system too? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany