From sacadmin Mon Aug 16 08:03:34 2004 Date: Mon, 16 Aug 2004 09:03:07 -0600 From: Andy R. Subject: Re: logadm additional options [PSARC/2004/613 Timeout: 08/23/2004] To: psarc@sac.eng.sun.com MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040803 Content-Length: 1124 Sheesh. Please ignore this case until I'm finished getting the materials in the case directory, etc. I have no idea why sac_nextcase sent this when I told it I did not have a file prepared (it used to NOT send mail in that case). Anyone know what the current process is for getting a case directory (so you can start copying things there, etc) without sending mail out to everyone? I sent mail to John Plocher about this last time but did not get a response. -andy Andy R. wrote: > Subject: PSARC FastTrack [08/23/2004]: logadm additional options > > > Template Version: @(#)sac_nextcase 1.55 08/11/04 SMI > This information is Copyright 2004 Sun Microsystems, Inc. > 1. Introduction > 1.1. Project/Component Working Name: > logadm additional options > 1.2. Name of Document Author/Supplier: > Author: Andy R. > 1.3 Date of This Document: > 16 August, 2004 > 4. Technical Description > See the case directory for more detail > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack From sacadmin Wed Aug 18 09:39:17 2004 Date: Wed, 18 Aug 2004 10:38:55 -0600 From: Andy R. Subject: PSARC/2004/613: logadm additional options To: psarc@sac.eng.sun.com MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040803 Content-Length: 2145 I'm self-sponsoring this fast-track, timeout 08/25/2004. The suggested bugfixes are backwards compatible, and the requested release binding is micro/patch. ========================================================================= MOVING LOGADM TIMESTAMPS Bug reports 4866172 and 4685009 point out that storing the timestamps in /etc/logadm.conf, where logadm's configuration is stored, was a bad idea. This proposal moves the timestamps to a new file, /var/logadm/timestamps. The file format is the same as the /etc/logadm.conf file format described in PSARC/2001/660, except that only the "-P" option for specifying timestamps is allowed. To make the transition as easy as possible for our customers, logadm will transition the timestamps to the new file whenever it discovers them in the old file. The new logadm will *only* write to /etc/logadm.conf when performing this transition or when specifically asked to via the -w option. logadm already supports an option, -f, for specifying an alternate file to /etc/logadm.conf. This proposal adds another option, -F, which allows one to specify an alternate timestamps file. logadm handles the case when -f and -F point to the same file, and in that case returns to the previous behavior of storing timestamps in the config file (that is, supplying "-F /etc/logadm.conf" provides the old default behavior). ALLOWING LOCALTIME-BASED ROTATED LOG NAMES Bug 4824041 complains that rotated log names which contain the date in their names are getting the date in the UTC timezone. That was done intentionally so that machines from various timezones could store all store their logs on some NFS-mounted filesystem. But of course some customers do not see this as a feature and it is surprising that the files do not end named according to the local timezone. This proposal adds a new option to logadm, -l (ell), which tells logadm to use localtime when naming filenames. This option does not change how timestamps are stored -- those continue to always use UTC, and the default behavior has not changed. A diff-marked man page is supplied in the case directory as background material. From sacadmin Wed Nov 16 08:44:20 2005 Received: from sunmail1brm.Central.Sun.COM (sunmail1brm.Central.Sun.COM [129.147.62.17]) by sac.sfbay.sun.com (8.12.9+Sun/8.12.9) with ESMTP id jAGGiJIQ024383 for ; Wed, 16 Nov 2005 08:44:19 -0800 (PST) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by sunmail1brm.Central.Sun.COM (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id jAGGiJC09750 for ; Wed, 16 Nov 2005 09:44:19 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.108.183]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id jAGGiJD7002600 for ; Wed, 16 Nov 2005 09:44:19 -0700 (MST) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0IQ2003013S6GG00@mail-amer.sun.com> (original mail from Andy.R@Sun.COM) for psarc@Sun.COM (ORCPT psarc@Sun.COM); Wed, 16 Nov 2005 09:44:19 -0700 (MST) Received: from [192.168.0.6] ([199.45.162.89]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0IQ2006W73TUPH7F@mail-amer.sun.com> for psarc@Sun.COM (ORCPT psarc@Sun.COM); Wed, 16 Nov 2005 09:44:19 -0700 (MST) Date: Wed, 16 Nov 2005 09:44:18 -0700 From: Andy R. Subject: PSARC/2004/613 addendum (logadm additional options) Sender: Andy.R. To: psarc@Sun.COM Message-id: <437B61E2.6010601@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5 (Macintosh/20051025) Status: RO Content-Length: 695 This fast-track, which was approved without comment more than a year ago, contains two changes to logadm which are completely unrelated. I filed them together just for convenience but now one of the features has been escalated and needs to integrate before the other. The two features are: - moving logadm timestamps - allowing localtime-based rotated log names Since there is no reason at all that these two features need to deliver together, and since nothing in this ARC case has been delivered yet, I'm just writing this note to the modify this case to allow the two features to be delivered separately. Unless someone squawks, I will leave the case marked as "closed approved". -andy