Speaking from an enterprise shop point-of-view, having two tools for the same thing in the systems management space is a mistake. It'll cause more confusion than *familiarity*. Logadm has been around since Solaris 9 and many shops make heavy use of it to manage system and application logs. Primary reason being that Sun supports logadm, it's stable, and the management of the software package is not on the customers head. While many shops used logrotate prior to Solaris 9, going back to it will be more of a headache than blessing. Realistically, each UNIX and Linux variant has it's own tools for this or none. For example, BSD has newsyslog, while AIX/HP-UX have no tool. Not a lot of consistency to begin with. My take is that one of the following has to happen:
1. We stick with logadm, forget logrotate, and perhaps enhance logadm? 2. We drop logadm and switch to logrotate. 3. Standardize on logadm and make it handle logrotate.conf syntax in addition to the logadm.conf syntax. 4. Standardize on logrotate and make it handle logadm.conf syntax in addition to the logrotate.conf syntax. 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;) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Systems Engineer http://www.opensolaris.org/os/community/sysadmin/ http://unixconsole.blogspot.com unixconsole at yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Alan Coopersmith <[email protected]> To: Dean Roehrich <dr161460 at sac.sfbay.sun.com> Cc: lsarc-ext at sun.com Sent: Thursday, June 5, 2008 10:33:37 AM Subject: Re: logrotate [LSARC/2008/359 FastTrack timeout 06/10/2008] Since the top-level goal is familiarity, and code sharing is a lower level goal, behind making OpenSolaris a well-working system, would this case be better served by making the logrotate administrative interfaces (which may be just vi /etc/logrotate.conf) work to control the existing logadm system to prevent conflicts between the two? -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering _______________________________________________ opensolaris-arc mailing list opensolaris-arc at opensolaris.org
