NFS home directories

It appears that using AFP home directories in ML server means that Fast User Swtiching cannot work anymore.
And it sounds like the solution is to dump AFP and use NFS. Anyone have information on how to set that up?

The NFS mounts are being shared off of a NetApp. We didn't have any issues with this in the past, only with Leopard.

Similar Messages

NFS Home Directories Yosemite

Has anyone successfully used NFS home directories for network logins?
This used to work in 10.6.8 Server but I am having a hard time setting it up in Yosemite. I need to enable fast user switching with multiple logins to our server which appears to be impossible using AFP.
I'd appreciate any tips on how to accomplish this. All clients and server are running clean Yosemite installs.

Apple stopped officially supporting NFS based home directories when Lion and Server.app was released. I have not done extensive testing but I certainly find two sessions using fast user switching and AFP works with Mavericks clients.
As far as I can see if a Snow Leopard server was connected to a Mavericks or Yosemite OD server it would still be possible for the Snow Leopard server to register an NFS home directory share in to Open Directory. This suggests that it might be possible to do the same even with a Mavericks or Yosemite server but that one would have to do all the work by hand in the command line. The logic for this conclusion is that Mavericks and Yosemite still include NFS even if they do not provide a GUI means to configure it and OD itself would appear to still be able to store records relating to NFS locations.
I have used NFS home directories in the past and found it solved a number of issues including -
Completely getting round Adobe's long time issues with network home directories
The same for some other third-party applications
Allowed 20+ users all on the same server to be logged in to their individual home directories in a Mac Terminal Server setup
This was all back in the days of using Snow Leopard Server.
I get the impression Apple secretly added the ability to use Fast User Switching for network logins with Lion or later to compensate for removing NFS support. This may have been at the behest of the developers of the two Mac Terminal Server products.

Problem mounting NFS home directories of NIS users.

Only on one of client (rest on all clients working fine), the Local directories under /home is getting mounted instead of NFS shared home directories of NIS users. Able to manually mount the NFS shared directories but they also get automatically unmount after some ideal time. Want that the NFS shared directories gets automatically mount when the NIS user gets login as it is happening on all other clients.
Scenario:_
NIS user: user1
NFS Shared home directory: /export/home/user1 (which should get mount as /home/user1 when user1 gets login)
Local directory: /home/user1 (which is getting mounted when user1 is getting login)
[CLIENT]/--->ps -ef | grep automount
root 23369 1 0 Mar 19 ? 1:58 /usr/lib/autofs/automountd
[CLIENT]/--->cat /etc/auto_master
/xfn -xfn
/net -hosts -nosuid,nobrowse
/- auto_direct -intr
/- auto_home -intr
[CLIENT]/--->ypcat -k auto.home
/home/user1 NFS_SERVER:/export/home/user1
/home/user2 NFS_SERVER:/export/home/user2
[NFS_SERVER]-->cat /etc/dfs/dfstab
share -F nfs -d "user home dir" /export/home
[NIS_SERVER]--->cat /etc/auto_master
/xfn -xfn
/net -hosts -nosuid,nobrowse
/- auto_direct -intr
/- auto_home -intr
Please let me know if any other information is required.

add this entry as the first non-comment line in /etc/auto_master on the client:
+auto_master

NFS Home Directories not acquiring permissions

Hi there. We have recently upgraded our labs to 10.5.4 from 10.4.11. We mount user home directories via NFS and have for some time without an issue. Now, though, I can create the mount using either fstab or Directory Services and it works, however when a new user logs in who does not have a home directory, the profile gets copied to the NFS server but does not acquire the correct permissions. THe home directory is owned by root and not the logged in user. Have any of you seen this? Are there any solutions or something that I might have done wrong? Any help would be appreciated and if this is the wrong section, point me to where I can post and I'll repost there.
Thanks
Jason

The NFS mounts are being shared off of a NetApp. We didn't have any issues with this in the past, only with Leopard.

NFS Network Home Directories

Hi,
I am able to authenticate the iMAC through an LDAP directory on a Linux machine but the home directories do not get mounted - can someone help me to get the NFS home directories from the server to mount dynamically on boot? There are around 300+ users and putting each user into a seperate line is not an option.
Thank you in advance!

This page came up in Google:
http://coewww.rutgers.edu/www1/linuxclass2005/lessons/lesson5/sec_10.html
I believe that the automount daemon is normally running on Mac OS X, so you don't need to start it, but I think you do need to define the master mapping. You also need to create a mount point directory such as /mnt or /home as an empty directory.

Multiple simutaneously logged in users accessing AFP home directories?

Hi,
Many of our problems are described in this guy's blog:
http://alblue.blogspot.com/2006/08/rantmac-migrating-from-afp-to-nfs.html
The basic capability we want is to have multiple simultaneously logged in users to have access to their AFP mounted home directory, which is configured in a sane, out-of-the box setup using WGM and Server Admin.
Multiple user access could take the form of FUS (fast user switching), or simply allowing a user to SSH into a machine that another user is already logged into and expect to be able to manipulate the contents of her home directory.
From my extensive searches, I have no reason to believe this is currently possible with 10.4 Server and AFP.
(here's the official word from apple: http://docs.info.apple.com/article.html?artnum=25581)
I've read that using NFS home directories will work, though.
I want to believe that Apple has a solution for this by now (it's been almost a year since we first had difficulty), or at least a sanctioned workaround. If Apple doesn't have one, maybe someone else has come up with something clever. I find it hard to believe that more people haven't wanted this capability! (not being able to easily search the discussion boards doesn't help, though...)
Thanks for your help!
Adam

Parallels Issue. Track at http://forum.parallels.com/showthread.php?p=135585

Portable Home Directories, FileSyncAgent, and Case-sensitive drives

I have a 10.5.3 Server machine that is serving (via NFS) home directories to a mixed group of Leopard (10.5.3) and Linux clients. The drive containing user home directories is formatted to be case-sensitive. I also use Portable Home Directories and mobile accounts on all the Leopard clients. Many of the client machines have case-insensitive drives.
FileSyncAgent is dying on the client machines with a lot of "Reverification failed" messasges in ~/Library/Logs/FileSyncAgent.log. The files being verified often have mixed case file names, while the error messages show lower case file names.
Anyone else seeing FileSyncAgent dying on every home sync?

Hi Guys, So far I have found what seems to be a fix for this issue. I was also having the issue happen to me around some iphoto file but that seems to be coincidental. I will detail what I did below but please first backup the mobile account on the local machine as you will need to recreate it.
Backup the local mobile home folder
Log into a admin account and delete the mobile account under the Accounts Pane in System Prefs
Log into the users Network account on the notebook
Delete all the following items
~/Library/Application Support/SyncServices
~/Library/Mirrors
~/Library/Preferences/ByHost/com.apple.syncservices.*
~/Library/Preferences/com.apple.filesync.plist
~/Library/Preferences/com.apple.homesync.plist
~/Library/Preferences/com.apple.LaunchServices.plist
~/Library/Preferences/com.apple.syndication.plist
~/Library/Preferences/Syndication
Logout of the Network account and then back in
Recreate the Mobile Account
From this point on I have not seen any issues with the FileSyncAgent crashing. Omit any of the files listed above that do not exist. I generally have the notebooks sync on login and logout and I forced a sync while logged in to make sure everything was okay and so far so good. Hope this helps.

Word 2008 for Mac and NFS mounted home directories "Save File" issues

Greetings everyone,
(Long time lurker, first time poster here)
I admin a small network (under 20 workstaitons) with a centralized NFS server, with user home directories mounted via NFS upon login. Users are authenticated via LDAP. This is all working fine, there is no problem here. The problem lies when my users use Microsoft Word 2008 for Mac. When they attempt to save a file to thier Desktop (or Documents or any folder under thier home dir) they are met with the following message:
(dialog box popup)
"Word cannot save or create this file. The disk maybe be full or write-protected. Try one or more of the following: * Free more memory. * Make sure the disk you want to save the file on is not full, write-protected or damaged. (document-name.ext)"
This happens regardless of file format (Doc, Docx, Txt) and regardless of saved location under the network mounted dir. I've noticed that when saving Word creates a .tmp file in the target directory, which only further confuses me to the underlying cause of the issue.
When users logon to a local machine account and attempt the save, there is no issue.
I have found many posts in other commuity forums, including this one, indicating that the issue is a .TempoaryItems folder in the root of the mounted directory. This folder already exists and is populated with entries such as "folder.2112" (where 2112 is the uid of the LDAP user). I find other posts indicating that this is an issue with Word:2008 and OSX10.8, with finger pointing in either direction, but no real solution.
I have installed all Office for Mac updates from Microsoft (latest version 12.3.6).
I have verified permissions of the user's home dir.
I have also ensured that this issue effects ONLY Microsoft Office 2008 for Mac apps, LibreOffice and other applications have no issue.
Does *ANYONE* have a solution or workaround for this issue? While we're trying to phase Microsoft products out, getting users to ditch Word and Excel is difficult without removing them from systems completely. So any pointers or help would be greatly appreciated.
Thanks.
~k

I can't tell you how to fix bugs in an obsolete version of Office, but a possible workaround is to use mobile home directories under OS X Server. The home directories are hosted locally and synced with the server.

NFS and LDAP on different servers: Problems with location of home director

Dear Apple Experts.
We are using LDAP server for user authentification
and NFS server for home directories.
Both are decictaed servers on differnt machines.
on the NFS server there are directories
/home/urpi
for staff's home directories
and
/home/students
for student's home directories
both are mounted to the Mac minis in
/Users directory
so
/Users/urpi
contains home directories for staff
/Users/students
contains home directories for students
Authentification works well andpermission are set as needed
but OS X shows missing home directories for LDAP authentificated users
and terminal shows missing home directory
for me it is
/home/urpi/fodrek
I was tried to mount NFS to /home, but it is not allowed
Would I ask if there is any setting to add directories, where home directories are placed,please?
I look forward hearing form you.
Yours faithfully
Peter Fodrek

So none of these machines are Snow Leopard servers?
What exactly do you mean when you say you tried to mount the NFS share to home? Can you copy and paste the command and error?
It sounds as though you don't actually have the NFS shares mounted. Assuming this is so, you might want to investigate how the automount command works so that your MacMinis mount the NFS shares on boot.
If your NFS/LDAP server is an OS X 10.6 server, set the shares to be automounted as user/group directories. Make sure your LDAP server is providing correct information on the home directory location. If it is local, I think the home directories need to be in /Users. If your mounts are indeed working but you cannot login, you might consider making links from /Users to /home/urpi or /home/students on an account-by-account basis (could be done with a quick shell script).

NFS for portable home directories not working

I just recently tried to move our PHD's over to NFS instead of AFP to allow for fast user switching and some other reasons.
However it doesn't work at all... The automount seems to work fine, as I can browse to /Network/Servers/servername/Users/ fine, but when the user tries to sync, a dialog pops up:
The sync could not complete because your network home at "nfs://servername/Users" is currently unavailable.
Try again later when it is available.
and then in the console it shows:
com.apple.SystemUIServer.agent[14236] mount_nfs: /Volumes/Users: Operation not permitted
HomeSync[14369] HomeSync.syncNow: Unable to mount server URL at 'nfs://servername/Users', status = 65.
com.apple.SystemUIServer.agent[14236] HomeSync[14369:903] HomeSync.syncNow: Unable to mount server URL at 'nfs://servername/Users', status = 65.
It seems like its trying to mount it at /Volumes/Users, but it can't (because a normal user can't mount nfs volumes?(..as far as i know))...and furthermore I don't know why it needs to mount it at /Volumes/Users when it's already automounted at /Network/Servers/servername/Users

I just managed to get my first sync to work.
My server exports /opt/home/<user> but not /opt/home since each user has a separate lvm volume. What worked was the following:
dscl . -delete /Users/<user> dsAttrTypeStandard:OriginalHomeDirectory
dscl . -append /Users/<user> dsAttrTypeStandard:OriginalHomeDirectory "<homedir><url>nfs://find/opt/home/<user></url><path></path></homedir>"
This is similar to what I saw on http://managingosx.wordpress.com/2009/02/19/leopard-mobileaccounts-and-nfs-homes / except putting the users name (in place of <user> as part of the url instead of part of the path.
The value for dsAttrTypeStandard:OriginalHomeDirectory was formerly /Network/Servers/<server>/opt/home/<user> which is a perfectly good directory, but not a url. I don't know why it wouldn't use the directory and manufactured a url instead.
By changing the value back to default and making my server export /opt/home, I'm still able to sync. Naturally I like this solution much better.
Doesn't seem like this solution will help you much if a given user can sync on some machines and not others, unless maybe you have different export rules to different machines in your network.

Home directories from GUI work but not from command line

I'm having trouble accessing home directories through SSH. After significant trouble, I reinstalled OS 10.4.6 Server on each of my 24 XServes. This is a HPC with an XServe RAID providing the storage space. I promoted the first XServe to an Open Directory master and created 2 test users. I created a two sharepoints from the XServe RAID--one for general data and one for home directories. I enabled AFP on both, granted R/W access to the default group "staff" (of which my two test users are members) and set the home directory sharepoint ("HomeDir") to automount using AFP for users' home directories through WGM. If I use Remote Desktop to login to one of the cluster nodes, the home directory seems to mount correctly. However, if I try to access the same user account through the command line--the home directory cannot be found.
I can cd to /Network/Servers/headnode.domain.com/Volumes/HomeDir; but I cannot see any of the folders listed there. On the head node, I can verify that the user's home directory has been created--it seems to be fully populated. I've checked permissions, and they seem to be correct; but the fact that I cannot access it from the command line seems to suggest that there's a greater permissions issue.
I've tried doing the identical setup using an NFS automount instead of AFP with no success. I can't find any answers for command line/SSH access to this problem. Any help would be appreciated.
Thanks,
CF

I've discovered something else in the course of troubleshooting this problem. If I login as a test user through remote desktop to, say, node1.domain.com; the home directory mounts correctly; and, as long as I do not reboot either headnode.domain.com or node1.domain.com, I can login via SSH and access my home directory.
Of course, if I do reboot--access no longer works. I've browsed through dozens of other posts and tried to follow other users' suggestions. I've manually created a hosts file, which I've uploaded to /etc/hosts on each node. I've double and triple checked DNS and DHCP--I have LDAP propagated through autodiscovery on DHCP; I have each node statically assigned; and I have DNS entries for each node. I also have computer entries in WGM; and I've used the FQDN of each node (node#.domain.com) for everything across the board.
I'm also hitting the "authentication error" when I try to access my other AFP sharepoint. I can't figure this out.

Users on network home directories hang after sleep

Hi,
I have the following problem: I have a 10.5 server with network home directories. I can login from Snow Leopard (10.6.1) however whenever the machine goes to sleep and comes back from sleep, the user hangs then if you wait a bit then it will come with the message that the share has been disconnected and it asks you to manually unmount. It will stay there forever. When you click disconnect, the system will unmount and remount the home directory but in the mean time, Mail will have reported disk i/o errors in the logs and throw errors (ranging from type in your password to 'rebuild index').
Going through the log files (and verbosity high) it seems that when going to sleep, the system doesn't unmount the network home directory. After it wakes up from sleep it attempts to unmount the home directory share which off course fails because it's in use and then it locks up, after you click disconnect, it says "spins reported" in the logs and goes on with remounting the shares.
The issue doesn't happen if the user is local. If anybody has an idea as to how this works or if they have it working, please let me know. I have tried just about anything. AFP shares, NFS shares, I have tried with or without the intr, nolocks, locallocks mount options - they all have the same issue. I have even tried another Mac Mini with a fresh install of Snow Leopard.

I found a possible cause and solution.
This has been on 10.6.1 with Mac Mini's. Then we got a new Mac Pro with 10.6 out of the (Apple) factory which I updated to 10.6.1, same issue. What I didn't think about is that by default I install a heap of software (including XCode, Adobe CS4 and Office 2008) with customized packages and workgroup manager preferences.
So I was mucking around with Cocktail (the tool to clean up caches etc.) and I noticed Snow Leopard hung every time after cleaning & recreating some caches. Now that I had a reliable way to hang Snow Leopard I investigated what could cause it.
I noticed during a PackageMaker session that Adobe CS4 installs a Version Cue startup script in /etc/machinit_peruser.d. I deleted it, rebooted, used Cocktail again and it went all the way through without hanging. Rebooted again, according to the logs it pre-linked & cached the kernel and several kernel extensions and that was it, no more hangs, no more issues logging in after sleep or screensaver.
So possible causes:
- VersionCue installs itself as a kernel module or something (the location says "mach" which is the kernel after all) which is not compatible with Snow Leopard.
- The caches and kernel extensions were 'dirty' out of the box but VersionCue (or something else that interacts with it) blocked my or Snow Leopard's automated attempts to clean them.
- VersionCue reinitializes (it sits on the network after all) after a sleep or screen saver timeout in a way that gives issues with Snow Leopard

How to specify one ethernet port for network home directories (other for normal filesharing)?

So I'm trying to get Home Directories up and running on a 10.6.8 Xserve (waiting until I get my NFS sharepoints migrated to a Linux server [for other reasons] before moving up to 10.7 Server). But posting here since that will be happening in the next few weeks, and it might be applicable now (so I can at least get that resolved ahead of time).
I have a different DNS entry for each ethernet port: server.office.domain.com at 192.168.0.11 for the first, and homes.services.internal at 192.168.0.10 for the second. DNS lookups for both resolve correctly (as does the reverse lookup).
If I use the Server Admin to pick a sharepoint as an automount for Home Directories, everything is fine, but it picks the server.office.domain.com hostname. Picking that works just fine, but that is also the connection that feeds the filesharing. I'd prefer to split that home directory traffic out onto the second ethernet port. So I tried just duplicating the initial connection (since it can't be edited directly in Workgroup Manager) and changing the hostname to the internal one, but I get an error when attempting to log in (the client login screen gives a very helpful "Couldn't login because of an error" error message) and don't see anything in the server logs.
The client machine shows the following line:
Code:
10/20/12 5:27:42.688 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] |
PremountHomeDirectoryWithAuthentication( url=afp://homes.services.internal/Users,
homedir=/Network/Servers/homes.services.internal/Volumes/HomeDirectories/Users/ user123, name=user123 ) returned 45
(added line breaks so it didn't extend off the page)
So it looks like this is failing because the automount isn't in place, but I'm not sure how to work that out either (i.e. how do I add that making sure it uses the internal hostname?).
Any suggestions on getting this to work?
I realize one solution is just to LACP the two ports, but that is a different ball of wax (I may do that later if I get a 4 port ethernet card and performance limitations demand it).

A possible solution might be this.
On ADSLBOX and CABLEBOX configure different subnets for the LAN, e.g.
ADSLBOX: 192.168.1.0/24
CABLEBOX: 192.168.2.0/24
The MEDIABOX gets these static IPs:
ADSL-LAN: 192.168.1.2
CABLE-LAN: 192.168.2.2
On the MEDIABOX, configure the two network interfaces using two routing tables.
The ADSL-LAN routing table
ip route add 192.168.1.0/24 dev eth0 src 192.168.1.2 table 1
ip route add default via 192.168.1.1 table 1
The CABLE-LAN routing table
ip route add 192.168.2.0/24 dev eth1 src 192.168.2.2 table 2
ip route add default via 192.168.2.1 table 2
The main routing table
ip route add 192.168.1.0/24 dev eth0 src 192.168.1.2
ip route add 192.168.2.0/24 dev eth1 src 192.168.2.2
# use the CABLE-LAN gateway as default, so general internet traffic from MEDIABOX runs over CABLEBOX
ip route add default via 192.168.2.1
define the lookup rules
ip rule add from 192.168.1.2 table 1
ip rule add from 192.168.2.2 table 2
To test the setup:
ip route show
ip route show table 1
ip route show table 2
I don't know how to persist something like this in ArchLinux using netctl. Might require to write a special systemd unit for it. Above is a working example from a RedHat box at my company.
Last edited by teekay (2013-12-04 07:42:22)

Portable Home Directories over CIFS

I'm trying to configure PHD over CIFS with samba/linux as file server.
It works. But there is a issue. When it synchronizes directory with server, for every newly created folder it complains about problem with sync.But regardless of complain directory is created. I traced down. Error happens when FileSync trying to chflags on directory created on samba share.
Typical error is
0:: 09/12/16 06:49:55.282 EXCEPTION: Invalid argument <-SStoreFileOperator_FS applyPermissionsFromObject: (StoreFileOperator-FS.m:508): chflags('/Network/Servers/cmsdata.tnw.utwente.nl/cifstest/Library/Assistants', flags=0)--> Error Domain=NSPOSIXErrorDomain Code=22 UserInfo=0x10058c170 "Invalid argument">
0:: 09/12/16 06:50:02.221 EXCEPTION: Invalid argument <-SStoreFileOperator_FS applyPermissionsFromObject: (StoreFileOperator-FS.m:508): chflags('/Network/Servers/cmsdata.tnw.utwente.nl/cifstest/Library/Autosave Information', flags=0)--> Error Domain=NSPOSIXErrorDomain Code=22 UserInfo=0x10057cb50 "Invalid argument">
Also it complains in similar way for chflags for couple of files
<PHD> 0:: 09/12/16 06:48:50.852 EXCEPTION: Operation not permitted <-SStoreFileOperator_FS applyPermissionsFromObject: (StoreFileOperator-FS.m:508): chflags('/Users/cifstest/Library/Preferences/com.apple.CoreGraphics.plist', flags=0x10000)--> Error Domain=NSPOSIXErrorDomain Code=1 UserInfo=0x1005839b0 "Operation not permitted">
But files isn't a big issue it is just couple of files from ~/Library which aren't going to be changed often, but complains about every directory - it is definitely too much. And, in fact, it even doesn't really want to set some flags for directories. Most of time it is "flags=0".
Is it possible to switch off this behavior? And not by "unix extensions = no", cause I need support for symlinks.
In fact, if you have mixed mac os x/other unix environment situation with PHD is terrible.
OSX doesn't support kerberized NFS4 in full way, especially through open directory (obviously, autofs doesn't accept vers=4, but even if it would, mount_nfs needs "4.0alpha", while autofs clearly expects number there). Although it is possible to patch sources for both of them, it isn't really solution.
In mixed unix environment AFP to Netatalk is useless, cause it doesn't handle symlinks in proper way (like native OSX server does, translate "slink" fdType into underlying FS symlink.
And with samba it is problem of chflags now. (ACL's also broken with samba BTW).

antst wrote:
Actually, there is a chance that I will add XServe into our setup. But it isn't $500 solution
I was referring to the price of the software only. If you want to add hardware as well, that is a different story.
But, still, Xserve doesn't support nfs4 for linux hosts.
Is that a requirement?
So far, from what I see, best option for file-server in multi-platform environment is solaris.
I think the best option for a server in a multi-platform environment is "each to his or her own". Get MacOS X Server for Macs, Solaris for NFS, and Windows for Windows. They can all access each other, but for system critical tasks like booting and home directories, let them handle what they know best.
It has full support of NFS4 ACLs on ZFS, which means you will also map correctly SAMBA ACLs and Netatalk also supports ACL when underlying system supports NFS4 ACLs (but probably only on solaris).
And in addition you get all nice features of ZFS and probably the best NFS server implementation.
I think you need to review what your requirements really are. You are still going to have 2 out 3 OSes running from foreign servers. You may find yourself back at square one with NFS4 instead of CIFS.
The last time I used Solaris full time was 2006, I think. I was in an organization big enough to have all our Solaris and NFS work done by Sun people on site. NFS went down on a regular basis. We are starting to go back to Solaris at my current big organization because Linux can't handle Multipath and QFS.
Don't get any ideas about me vis-a-vis all those buzzwords. I'm still just a programmer. It is perfectly normal to have multiple servers with different OSes. You can get things working the way they are supposed to work and then see if you can migrate things over to NFS4. I still think you would have more success running MacOS X as the server and getting rid of Netatalk.

Workgroup Manager won't create home directories; no error message

This is quite frustrating. For the past 3 years or so I have used the same procedure to add new users to my LDAP directory:
1) In Workgroup Manager, click the New User button
2) Assign name and password under the basic tab
3) Assign group memberships under the Groups tab
4) Under the Home tab, select the right place (nfs://my.server.org/Volumes/Users), click Create Home Now
5) Click Save
Suddenly, when I try to do this yesterday, workgroup manager won't create home directories anymore. I could probably do it manually, but I'm not sure how to get all the right skeleton setup in there. But my main question is, why doesn't this work anymore? Why can't I at least get an error message instead of being silently ignored?
I share admin duties with other people, so it's possible someone installed an update recently; all I can really say is that I'm running Leopard Server 10.5.8 right now, and can find out whatever else is relevant.
Any ideas?
Thanks!
~Ben

Thanks for the pointer to createhomedir - that did indeed do the trick. (How on earth do people find these little nuggets).
I hesitate to mark this as solved however - it's a functioning workaround, but does nothing to explain why on earth the GUI suddenly stopped functioning.
But in the (likely) event that that question never gets answered, thanks again for letting me get on with working!

NFS home directories

Similar Messages

Maybe you are looking for