Al> Suns sendmail is just too "different" to where it gets in the way, rather Al> than solves your email config issues. (Sorry John Beck)
If you are talking about things like patches modifying sendmail.cf, then I agree that this is a problem, and a bug is in fact open on this issue. If you are talking about things like the netservices example you gave, then I agree that this is a problem (more below). But if you are talking about e-mail configuration in general, then I strongly disagree, as the primary objective of my work on sendmail in my 10 years at Sun has been to get rid of the "Sun hacks" in the Solaris version of sendmail, and get it to be as similar as possible to the version available from sendmail.org . I believe I have succeeded in this regard, and if there are any differences in the binary or configuration files which are causing user pain, then I would like to know about them, as I believe I have eliminated all of them. Al> install the blastwave sendmail in /opt/csw Al> Now enjoy independent *per zone* sendmail operation and you don't have Al> to worry about a Solaris patch screwing up your (Sun) sendmail config. However, if you want to upgrade sendmail, you need to do it in N separate zones, as opposed to one if you run the Solaris version. That was a design goal of Zones, and why /usr is in the default inherit-pkg-dir list. Al> netservices limited Al> svcadm disable sendmail Al> netservices limited Al> It's back! This appears to be a bug in the netservices script, as it does a `svccfg apply` on the new profile, which has enabled='true' for sendmail. I will check with my colleagues who implemented the Secure by Default project and get a bug filed on this if one is not open already. -- John http://blogs.sun.com/jbeck _______________________________________________ opensolaris-discuss mailing list [email protected]
