Peter Suetterlin skrev:
Verner Kjærsgaard wrote:
Hi Peter and everyone else :-)
I can't get my head right...please bear with me and correct me here.
This is my auto.master file: /extern /etc/auto.nfs
This is my auto.nfs file: * 172.16.11.229:/volume1/EXPORT/&
Fine.
(the export works ok generally, I can mount the stuff manually and so forth)
Then also check permissions, i.e., when you manually mount 172.16.11.229:/volume1/EXPORT/vk, can you read/write as user vk there? That's a general issue, unrelated to the specific problem.
This is my / directory (snip): ... drwxr-xr-x 2 root root 4096 13 apr 15:49 extern/ ...
Also fine.
Now I also tried setting up an 'extern' directory with a subdir beneath it named 'vk'.
You shouldn't. /extern should be empty when you start autofs
I then tried with symlinks from /home/vk like these: ln -s /extern myfiles
No.
and ln -s /extern/vk myfiles
Yes.
It appears that I can 'cd' into 'myfiles', but I cannot do a 'touch xxx.yyy' in the directory. No permissions or so.
See above. Permissions and owner of the directory on the server have to be correct. You'll have to set that on the server as on the client root is mapped to nobody.
Q: should the original /extern directory have 755 or 777 rights?
Shouldn't matter much, but I'd recommend 755
Q: should each individual user have his own subdir beneath it, created manually before autofs is started?
No, autofs does that normally, either on start, or when it is requested.
Q: the symlink created in /home/vk, should this point to /extern or to /extern/vk?
The latter, to /extern/vk
Once again...I really do appreciate your inputs! Thanks a lot.
You're welcome ;^>
Pit
Hi list and P., - I've got some interesting (I hope...) debug info. - first, a manual mount of nfsserver:/export, it goes like this and it works perfectly fine: --- linux-3fm3:/ # mount -t nfs 172.16.11.229:/volume1/EXPORT /mnt/syn -o rw linux-3fm3:/ # cd /mnt/syn linux-3fm3:/mnt/syn # l totalt 8 linux-3fm3:/mnt/syn # cd / linux-3fm3:/ # umount /mnt/syn linux-3fm3:/ # --- I then SSH'd into the Synology DS209 box to look into the /var/log/messages of that box. I also set /etc/sysconfig/autofs in SuSE to 'verbose' logging. I then start up autofs with 'rcautofs start' These are my results (the contents of auto.master and auto.nfs are not modified): --- I start autofs, in the log I see: Apr 13 21:24:40 linux-3fm3 automount[24082]: Starting automounter version 5.0.3, master map auto.master Apr 13 21:24:40 linux-3fm3 automount[24082]: using kernel protocol version 5.00 Apr 13 21:24:40 linux-3fm3 automount[24082]: mounted indirect mount for /extern with timeout 600, freq 150 seconds Apr 13 21:24:40 linux-3fm3 automount[24082]: ghosting enabled --- As far as I can see, this look really good. I then carry on (using my regular vk account in another konsole) with 'ln -s /extern/vk myfiles' This succeeds in that I get no errors - but also no activity at all in either logfile(s). I then try to list the contents of directory 'myfiles', in SuSE I type 'l': In the client, nothing happens at all. Well, the symlink is displayed in RED colour, it appears to be broken. But...there was NO ERROR when I established it. In the SYNOLOGY server however, I see this in the /var/log/messages: --- Apr 13 21:26:28 mountd[3256]: can't stat exported dir /volume1/EXPORT/vk -o rw: No such file or directory --- Well...eh...that's not so difficult to understand in that the 'vk' subdir indeed does not exist. This is where I'm stuck. I don't understand what's going on. Any ideas? -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org