[wjlyerly]

Nope, the behavior is still the same. Fortunately for us, our situation allows for a work around by making a local account on the few shared workstations we have. Most users have a local account on their laptops, so its not too much of an issue. Our Tiger server will probably limp along until snow leopard comes out. Surely that’ll fix it. 🙂

[wjlyerly]

A few other tidbits

– root on the leopard client can su to a OD account instantly
– OD account home dirs are automounting correctly
– id, finger, etc instantly show the proper info for OD accounts
– set up was simply adding the OD server in Directory Utility

[wjlyerly]

I’m not specifying any mount options other than nfsvers=2/3 so I know explicitly which I’m using. Otherwise its just the default. Serverside its all out of the box defaults too.

I can do a ‘cat history > /dev/null’ with no errors. I also made a copy and opened it in vi, made some edits, and closed with no errors. It seems cvs might be doing something slightly more exotic?

I ran a ktrace on cvs with the repo mounted via nfs2 (working) and with it mounted nfs3 (broken). The results show identical trace until an open syscall on the history file. The working one succeeds:

15907 CALL open(0x3016d0,0x9,0x1b6)
15907 cvs NAMI “/mnt/dev/cvsroot/CVSROOT/history”
15907 cvs RET open 5

where the broken (nfs3) one fails on the same call

15907 cvs CALL open(0x3016d0,0x9,0x1b6)
15907 cvs NAMI “/mnt/dev/cvsroot/CVSROOT/history”
15907 cvs RET open -1 errno 13 Permission denied

Mounted either way, the permissions on the history file are 777.

The second argument to open is the flags parameter. /usr/include/sys/fcntl.h indicates that a 0x9 should correspond to O_APPEND (0x8) and O_WRONLY (0x1). So, its being opened as write only, append mode.

Any of that hint at the problem?

thanks,
jay

[wjlyerly]

Great. That seems to handle it nicely. What’s the preference order here? If I set mobility options (or any preference) for group, computer list and user, how do they get applied. I would imagine user prefs get top priority, followed by group and then computer list. Is that right? Can I disable PHD syncing for a user and have it apply to all machines?

thanks.

[wjlyerly]

No replies… hmmmm.

Anyway, I did ditch the GUI managed bootp for dhcpd (which happily compiles with gcc 3.3 but not gcc 4). Everything is back to working, but being served from the Xserve and not the old linux box. I find it odd that dhcpd can hand out LDAP over dhpc much better than bootp that Apple ships.

[wjlyerly]

Yes, that’s right.

Our home directories (among other things) are hosted on a linux based NFS server.

[Author]

Posts