Octave Orgeron wrote: > The point here is that when it comes to systems management, there has to be > standardization. Otherwise, we end up with a system that can't be managed > consistently across SA's, which is a bad thing. Having both tools will > eventually lead to something crazy like.. logadm and logrotate colliding and > rotating log files that contain important system or application data. This > raises all sorts of flags on the data-corruption and audit radar for > customers that care;) >
I think the standardization is most important within an organization. Plenty of people don't use logadm because it is kinda funky. logrotate is easier to use thanks to is config syntax. Choice is good, but I agree that there should be a single "standard" toolchain. I've always believed that IPS would drive us closer to standardization because the installed software set would continue to shrink as packages increasingly become available as remote package installations. What do NOT want to see is default installations with redundant software. There has always been wayyyyyyy too much duplication in Solaris, leading to obscene installation sizes. Thus far the problem has gotten worse rather than better, but we'll see how it goes. From a tools perspective I'm far more concerned about a default shell with usable RBAC functionality than switching log rotators. :) benr.
