AFP548 Changing the world one server at a time.

home directory was not found in the usual place

Home › Forums › OS X Server and Client Discussion › File Serving › home directory was not found in the usual place

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #365740
    djc6
    Participant

    Hello,

    I get the following error “home directory was not found in the usual place or cannot be accessed” the first time a user logs into the system. I set the LDAPv3 plug-in to map NFSHomeDirectory to an attribute homeDirectory in the campus LDAP that says “/usr/homes/{username}”.

    For testing purposes I was going to use the local disk in the machine before I went and mounted /usr/homes off of the NFS Server. I created /usr/homes and everything works fine – the user’s home directory is created on first login, home dir permissions seem ok, users can save data. And on subsequent logins everything is fine, too. Its just on first login they are greeted with something along the lines of “home directory was not found in the usual place or cannot be accessed”.

    One other thing I tried was symlinking /usr/homes to -> /Users – everything still works fine, except for that benign error.

    The system log is full of errors like this during the first login, always 20 attempts. Subsequent logins to the system occur much faster, since its not polling the directory.

    loginwindow[70]: Failed to stat homedir: sleeping 1 second: chdir returns -1 for /usr/homes/{username}: Attempt 20

    Any ideas? Thanks!

    #365750
    djc6
    Participant

    I figured it out…

    I was logging in with my ldap account to test it out, and would then log out. Next, I would log in as a local user and delete the profile, thinking I could then log in again with my ldap account to test its automatic creation. Well, apparently OS X is smart enough to know I’d logged in before and would look for my home directory. People who had truely never touched the machine before wouldn’t receive this error the first time they logged in; it would simply create them a home directory. Because I had logged in before, OS X brought up that error since it knew it’d already made me a home directory once before (I guess).

    If I rebooted the machine between deleting my home directory and logging in again, OS X would not present that error. I guess rebooting clears some cache that told the OS it had made a home directory for me in the past. Thanks!!

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.