I hate replying to my own posts, but...
I got it working.
Quote:
Tips:
- create /opt/zimbra/openldap-data directory
- some scripts are not in bin but in libexec and they are not executable, chmod +x them
|
These I had figured out on my own. cd'ing to the /opt/zimbra/libexec directory in order to exec those scripts rather than specifying them by full path also helped. Some scripts have relative paths hardcoded, iirc, to something like "../bin".
The ant-reset-the-world thing was solved (or bypassed) by commenting out the small section of build.xml that references the sample search folders. I figured I really didn't need those anyhow.
The cpu + error message thing happens when testing the client on the same machine that's running the server. Accessing the server via another PC on the network, it worked fine (in my limited testing). Maybe this is a race condition, or something?
Since I'm hoping to potentially deploy Zimbra on the same machine that serves up thin client desktops, this could be a problem. I'll search for this in the forums, but feel free to direct me to information on this if it's already available.
I've done only limited testing, but will be glad to share my experiences with anyone interested in hearing about how further use goes.