There are only two reasons to have to reboot any type of Unix-based
OS:
1) hard server crash/kernel panic
2) OS updates that require reboots
Other than that, no reason
Or faulty kernel cache problems.
I hit this recently when messing around with a certain ACL setup.
Starting/stopping the AFP server, flushing lookupd, forcing
replication, local caches, whatever, nothing would resolve the client-
side issue I was seeing. (Users would be denied access in the Finder,
but could access said folders in Open/Save dialogs and through the
terminal). I spent most of a day on and off working on this, so any
cached data should have been cleared.
I came into work early the next morning, tested two clients, problem
still existed. Rebooted the AFP server and everything started working
perfectly.
Obviously this *shouldn't* happen, but just pointing out that there
are bugs in OS X/OS X Server, and sometimes a reboot will fix
whatever problem you're having.
--
Nigel Kersten [Senior Technical Officer]
College of Fine Arts, University of NSW, Australia.
CRICOS Provider Code: 00098G
