Results 1 to 4 of 4

Thread: zimbra.log owner changing on reboot

  1. #1
    Join Date
    Jan 2006
    Posts
    2
    Rep Power
    9

    Default zimbra.log owner changing on reboot

    I'm having a bit of a problem. I have Zimbra up and running great on my SuSE 10 box. Everything works perfectly and the only thing I had to do to get all the services started was to change the owner on zimbra.log from root to zimbra. Logger and snmp would not start if the owner was root.
    This works great, but every reboot causes the owner to change back to root.

    Is this a bug?

    I also don't see any data in the server specific monitoring. I see some graphs for system wide information, but only data not available for the server.
    Just mentioning that in case they are related.

  2. #2
    Join Date
    Feb 2006
    Posts
    59
    Rep Power
    9

    Default

    How did you get suse to recognise your fully qualified hostname

    If you do: hostname at the prompt do you get

    machinename.domainname.com

    or just machine name?

    Cheers

    Yogiman!

  3. #3
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    The server specific stats stuff is a known bug.

    I'm not sure what's happening with the log files - it may be a suse reboot thing.
    I've heard it mentioned in other places.

  4. #4
    Join Date
    Jan 2006
    Posts
    2
    Rep Power
    9

    Default

    hostname returns just the system name.
    hostname -f or hostname --fqdn returns the fqdn

    This is normal behavior from what I have read.

Similar Threads

  1. Replies: 4
    Last Post: 10-19-2006, 08:58 PM
  2. MTA is Dying after yum update
    By tonyawbrey in forum Administrators
    Replies: 27
    Last Post: 04-02-2006, 06:11 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •