[halg]

Sorry I have not been on this forum until about a month ago when my gf found Zimbra and wanted me to install it. Like others here, I am concerned about multiple installations of, e.g., mysql server on the same Linux box.

Originally Posted by anand

You should think of the mysql instance inside the Zimbra mailbox
store as an embedded database.

I can think of it any way you want. Or any way I want. I have no problem conceptually. The concern is having multiple mysql servers, e.g., competing to serve the mysql service port.

So, without me having to try the Zimbra install to find out, can you just tell me if you modify /etc/services or other files in /etc ? Quotes, below, contraindicate each other in terms of what files external to /opt get modified by Zimbra. Do Zimbra apps use their own internal /etc/services-like file under /opt?

Originally Posted by anand

At this time, we have a LOT of people trying to install ZCS, and
kick the tires. Many of them would like that any trial install of
Zimbra not screw up their distro installation - everything being
in /opt/zimbra adds some insurance and level of comfort. Going
forward, for every new release with a lot of features that people
want to quickly install and try, they should feel comfortable that it is
not going to do "atrocious" things to their /etc directory. [One
person's atrocious is another persons normal. Such is life.]

I am not sure whether this paragraph was written in the current or future tense ("people...would like that any trial version ..."). Does the current release install EVERYTHING for Zimbra into /opt? Any exceptions we might want to know about? The install docs do not get into this much detail; they just tell you to disable any running versions of mysql, etc.

Originally Posted by KevinH

We only patch SASL but the other packages are configured to run in /opt/zimbra so even if you remove our pkgs the local versions will not be configured to use the config tools we ship.

Let's say what I have concluded so far is correct. How hard is it to get my SASL back to its original state?

Originally Posted by marcmac

In order to accomplish this, you'd probably have to edit all of the scripts in bin and libexec, as well as the /etc/sudoers file. You'll also have to duplicate or adapt all of our config files to your versions/locations.

I would hope you mean the bin and libexec under /opt, and not anywhere else under the Linux root directory?

So, /etc/sudoers is another file external to /opt that gets modified by Zimbra?

Again, can we get an impact listing of all the files external to /opt that get modified by Zimbra, either in installation or during administration and use of the running Zimbra system?

Sorry I am so damn anal about all this.

Thanks,
Hal