![]() Registered Member ![]()
|
This problem seems to fall between all the forums so I thought I'd try here first
If I set up my NFS4 server as people seem to recommend ie /shared *(fsid=0,ro,crossmnt,sync,root_squash,no_subtree_check) /shared/home *(rw,sync,root_squash,no_subtree_check,bind=/home) Then have /shared /home /home/user1 /home/user2 etc Clients with KDE will let you log in but stops after the first icon fades in and never goes any further If I make /shared rw everything works perfectly Have I done something wrong ? Thanks M |
![]() Administrator ![]()
|
KDE requires write access to it's configuration files, and the user home directory in order to startup successfully.
Which directory does /shared correspond to?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
/shared is my NFS4 pseudo root
Ta M |
![]() Administrator ![]()
|
Sorry, should have been more direct. Does /shared have any impact upon the following directories?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
/shared is my nfs4 pseudo mount with /home bound to it
making the pseudo root ro seems to make everything under it ro as well even if you make bound directories rw - maybe I have missed something I have done some more research this morning and I have come to the conclusion that it's not KDE - About half the guides show the pseudo root as ro and the rest show it as rw - NFS4 howtos seem to be like standards ... there are lots to choose from Thanks for getting back anyway best wishes M |
![]() Administrator ![]()
|
In this case, I would recommend two NFS mounts: one read-only for /shared and one writable for /home.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]