Leopard Server reliability

Discussion in 'Mac OS X Server, Xserve, and Networking' started by andyadmin, May 22, 2008.

  1. macrumors newbie

    May 22, 2008
    Findhorn in Northeast Scotland

    I would like to introduce myself as I have just joined this forum.

    I am Andy and I am Network manager/Administrator for the Findhorn Foundation located in Northeast Scotland.

    So now to my question!

    I am considering recommending using Leopard server (build 10.5.2) to provide DNS, DHCP, Webmail, File sharing and calendaring.

    I also found a bug in postfix which reulted in local mail not being delivered.

    I do have some reservations though, having read some other posting elsewhere other folk report similar problems to myself i.e. DNS and DHCP not working then a while later just start working (having flushed DNS Cache anyway).

    Would it be better to stay with Tiger Server until Leopard is more reliable?

    I look forward to some feedback please.


  2. Guest

    Sky Blue

    Jan 8, 2005
    Yes, I'd wait until 10.5.3 to see if bugs are fixed. Leopard server is very flakey.
  3. macrumors P6


    Jun 11, 2007
    not that i have any personal experience, but i would suggest that you stay with tiger. it seems to be still working a lot better and reliable than leopard at the moment.
  4. macrumors 6502

    May 28, 2006
    I've been running 10.5 on my Xserve for several months and I would say that you should stick with tiger for now. It mostly works but still has a few bugs that I still have not seen fixed.

    The main one I have dealt with is with the DHCP services. I found that when using the GUI, the DHCP's .plist file would not be setup correctly. This would cause the DHCP service to not function correctly. I ended up having to go in and manually edit the .plist file, which was a pain considering I had never done this before. For some reason the GUI would leave out info randomly that had to be reenterd. I could never see a patern to it. I still had the same issue as of the 10.5.2 update. Never had this issue when running 10.4.7 and later on the same machine. Even with editing the plist file, I would still get random failures. Since then I have transfered my DHCP services to a dedicated router.

    I haven't had any problems with DNS other than getting use to the 10.5 interface. Filesharing has worked fine for me also. Haven't used my Xserve for mail or calendar. Mine is setup as an open directory server, providing external mobile accounts. Besides the ocasional sync error they also run fine.

    As others have said, wait for leopard to mature a bit more before moving to it. My setup isn't critical, so I can live life on the edge.
  5. macrumors newbie

    May 21, 2008
    Ditto, wait for 10.5.3

    The well documented filesharing bug makes it feel like it is not ready for prime time. There is a work around for it, but it really should have been fixed by now.
  6. thread starter macrumors newbie

    May 22, 2008
    Findhorn in Northeast Scotland
    Leopard Server

    Thanks guys for the feedback.

    I've just got back from being away and have just read the postings.

    They do confirm my thoughts that Leopard needs to be a wee bit more stable before setting 50 60 clients loose on it.

    I've had Tiger running as a trial for over a year and found it to be stable and reliable (although with only one client - me!



Share This Page