Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #371231
    effects
    Participant

    Okay, I have a problem with Leopard server in which AFP apparently quits working for no reason even though AFP says it is running. When scouring the Apple discussion boards, I found a lot of people are having the same problem. In order to resolve this, I contacted Apple and they informed me that they were aware of the problem, but wouldn’t comment on whether or not they were working on a fix for it. The informed me I could fix the problem by creating a cron script to initial the following command [b]sudo killall -HUP AppleFileServer[/b] and having it run every five minutes. I had never done this before, so I asked if they would help and they said no. This is where I hope someone can help me. I know that you can view the current cron scripts by going to terminal and typing in crontab -e and you can use pico to edit it, but that is as far as I have gotten. I don’t know how to actually create the script that will run. I have done Applescript before, but I don’t know these particular commands or if I can even do this in applescript. Please help! 🙁

    Thanks,
    David

    #371244
    effects
    Participant

    Basically, we are using the leopard server for home directories. Each user logs in and automounts their profile from the server. For no reason at all, users won’t be able to log in. It tells them that their home directory is on an AFP or SMB share that is not available. If I log in locally to a client machine, I can’t access an AFP either. No services are stopped. Everything appears fine. Stopping and restarting the AFP service usually allows users to login, occasionally we have to reboot. That’s it in a nutshell. We can find no good reason for this and it happens at random times. This can happen multiple times in a day or it may skip a day. Other users are reporting similar problems on Apple’s forums, but no solution has been found.

    David

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

Comments are closed