> On Sun, Apr 23, 2006 at 11:30:00AM -0400, Dennis Clarke wrote:
>
>> I therefore propose that any and all optional software that shall be
>> installed into the /opt filesystem also respect these standards.
>
> I'm uncertain what you mean by this. In most cases, the standards for
> commands are already met by existing OpenSolaris software;
Right now I am concerned with a software stack that addresses the entire
customer base from Solaris 8 upwards.
The idea is to have a pile of software that goes into /opt which also has
its configuration files optionally in /etc/opt/foo as that would allow zones
to pick up the binaries hile having separate configuration data.
Take a look at the thread in OpenSolaris-discuss which inspired this thread.
Currently I have a pile of software that goes into /opt/csw but it was
designed from square one to address the needs of Solaris 8 upwards. Some
packages may or may not look for config data in /etc/opt/foo and are trapped
with looking in /opt/csw/etc or /opt/csw/share/foo for example.
Consider clamav-0.88,REV=2006.04.15 which was added into the CSW software
pile as an update ( the ClamAV antivirus scanner has been at Blastwave for
years ) at 17 April 01:07 AM.
That is pretty recent.
Where does it gets its configuration data from when it runs ?
>From conf files in /opt/csw/etc and not from /etc/opt/clamav/ and thus it
works fine on Solaris 8 and 9 and 10 and upwards provided that the Global
Zone is where it runs. In a zone it can run fine also provided that no
other zone trys to run it and also provided that the /opt filesystem is
shared with one common set of binaries into the non-global zones.
Really, this is a trivial code tweak and then we can install SendMail (
latest rev is SendMail 8.13.6 ) as well as clamav in a zone no problem.
I have a user in Montreal that has 192 branches and all email is handled by
a single small Solaris box running the SendMail+ClamAV software. They are
considering an upgrade and thus a small Galaxy box ( or anything Opteron
really ) will suit them fine. With the code tweaks that I mention we can
put SendMail and ClamAV into a zone and then the user is left with a
powerful machine that they can zone again to provide some other service.
Provided that the conf files are in /etc/opt/clamav as opposed to only
/opt/csw/etc . Then we can put in the same software from Solaris 8 upwards
and have no isses in the Solaris 10+ Zones.
I think that makes for happy customers.
Dennis
ps : see :
http://www.blastwave.org/packages.php/sendmail
http://www.blastwave.org/packages.php/clamav
http://www.blastwave.org/packages.php/libclamav
http://www.blastwave.org/packages.php/libmilter
These are all updated quite regularly and have been in
production environments for years now.
Alex Moore is just fantastic :
http://www.blastwave.org/maintainers/asmoore
