Difference between revisions of "Todd dsm-Notes"

Line 8: Line 8:
 
Here's some background:
 
Here's some background:
 
  1) I am working from a slim install of the latest version of CentOS 5. Here are some loose install notes:
 
  1) I am working from a slim install of the latest version of CentOS 5. Here are some loose install notes:
    * -nobase is designated in the kickstart file.
+
      * -nobase is designated in the kickstart file.
    * We're installing only the packages necessary for all required applications and their dependencies.
+
      * We're installing only the packages necessary for all required applications and their dependencies.
    * And some additional utilities.
+
      * And some additional utilities.
  
 
  2) We are using shell scripts to automate the install of the aforementioned solution.
 
  2) We are using shell scripts to automate the install of the aforementioned solution.
  
  3) For all scripts that need to modify Zimbra the setuid bit is set (for example) to 4744 so the scripts run as the user zimbra.
+
  3) For all scripts that need to modify Zimbra:
 +
      *The setuid bit is set (for example) to 4744 so the scripts run as the user zimbra, and
 +
      *They have all been chown'd to zimbra.root.

Revision as of 17:01, 14 December 2009

Hey all,

As some of you may or may not know, I'm working on a build of a Zimbra server that's a little off the beaten path. In order for me to ask for help in the forums it seems like it would be helpful to provide some additional information.

I intend to transition my current clients away from MS-SBS (Small Business Server) with the solution laid out in Gregs write-up for making Zimbra/OpenLDAP/Samba work together; see the solution here: UNIX and Windows Accounts in Zimbra LDAP and Zimbra Admin UI

Here's some background:

1) I am working from a slim install of the latest version of CentOS 5. Here are some loose install notes:
     * -nobase is designated in the kickstart file.
     * We're installing only the packages necessary for all required applications and their dependencies.
     * And some additional utilities.
2) We are using shell scripts to automate the install of the aforementioned solution.
3) For all scripts that need to modify Zimbra:
     *The setuid bit is set (for example) to 4744 so the scripts run as the user zimbra, and
     *They have all been chown'd to zimbra.root.
Jump to: navigation, search