From jw137282@sac.sfbay.sun.com Fri Feb 20 14:04:47 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1KM4kkU014866
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 20 Feb 2009 14:04:46 -0800 (PST)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1KM4ios012277;
	Fri, 20 Feb 2009 22:04:45 GMT
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFD00201XBWPI00@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 20 Feb 2009 14:04:44 -0800 (PST)
Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFD0003FXBWA120@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 20 Feb 2009 14:04:44 -0800 (PST)
Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n1KM4hAV014398; Fri, 20 Feb 2009 14:04:43 -0800 (PST)
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1KM4foC014846; Fri,
 20 Feb 2009 14:04:41 -0800 (PST)
Received: (from jw137282@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1KM4f31014842; Fri,
 20 Feb 2009 14:04:41 -0800 (PST)
Date: Fri, 20 Feb 2009 14:04:41 -0800 (PST)
From: James Walker <jw137282@sac.sfbay.sun.com>
Subject: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
To: PSARC-ext@sun.com
Cc: lizhong.li@sun.com
Message-id: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 13040

I'm sponsoring this familiarity case for Lizhong Li. The requested
release binding is minor. The man pages have been posted in the
materials directory.

Template Version: @(#)sac_nextcase %I% %G% SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 mrtg
    1.2. Name of Document Author/Supplier:
	 Author:  Lizhong Li
    1.3  Date of This Document:
	20 February, 2009
4. Technical Description
mrtg Check List
1.0 Project Information
1.1 Name of project/component
    mrtg

1.2 Author of document
    Lizhong.Li@Sun.COM

2.0 Project Summary
  2.1 Project Description
    MRTG - The Multi Router Traffic Grapher, is a popular tool to monitor
    network traffic and other system status.

    It monitors SNMP network devices and draws pretty pictures showing
    how much traffic has passed through each interface. Routers are only
    the beginning. MRTG is being used to graph all sorts of network
    devices as well as everything else from weather data to vending machines.

    mrtg-2.16.2 will be integrated into the SFW consolidation as part
    of this proposal, and will be installed as SUNWmrtg.

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [*] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [*] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
      Tobias Oetiker <oetiker@ee.ethz.ch>
    
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [*] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [*] Yes 
      [ ] No - briefly explain
      
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [*] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [*] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [*] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [*] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [*] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [*] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [*] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [*] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      <system drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product>
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product id>\<version id>\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [ ] Yes
      [*] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [ ] Yes
      [ ] No - ARC review required
      [*] N/A
    
      Are these components already in the Solaris WOS?
      [ ] Yes
      [*] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [ ] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [ ] Yes
      [*] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [ ] Yes
      [ ] No - ARC review required
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [ ] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [*] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [*] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [*] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [*] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [*] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [*] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [*] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [*] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [*] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [ ] Yes
      [*] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [ ] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [ ] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [ ] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [*] Yes
      [ ] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [*] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [ ] Yes - explain below
      [*] No
      [ ] N/A
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [*] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [*] Yes
      [ ] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [*] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [*] No 
      
      Examples of Core Solaris Components include but are not limited to:
      
        Secure By Default
        Authorizations
        PAM -- Plugable Authentication Module
        Privilege
        PRM -- Process Rights Management -- Privilege
        Audit
        xVm -- Virtualization
        zones / Solaris Containers
        PRM -- Process Rights Management
        RBAC -- Role Based Access Control
        TX / Trusted Extensions
        ZFS
        SMF -- Service Management Facility
        FMA -- Fault Management Architecture
        SCF -- Smart Card Facility
        IPsec
        
4.0 Interfaces
  4.1 Exported Interfaces
  
    Interface Name		Classification      Comments
    -------------------------- 	------------------- -------------------------
    SUNWmrtg                    Uncommitted	    Package
    /usr/bin/mrtg               Uncommitted	    Perl script
    /usr/bin/mrtg-traffic-sum   Uncommitted	    Perl script
    /usr/bin/cfgmaker           Uncommitted	    Perl script
    /usr/bin/indexmaker         Uncommitted	    Perl script
    /usr/bin/rateup             Uncommitted	    Executable binary file
    
  4.2 Imported Interfaces

    Interface Name		Classification 	Comments
    -------------------------- 	--------------	----------------------
    SUNWgd2                   	Uncommitted	Graphics Draw Package
    SUNWpng                   	Volatile	PNG Package
    SUNWzlib                   	Committed	Zip Package    
    SUNWzlibr                  	Committed	Zip Package (Root)   
    SUNWlibms                  	Committed	Math Package
    SUNWlibmsr                 	Committed	Math Package (Root)
    
Appendix A - References
  [1] http://oss.oetiker.ch/mrtg/

  OSR ID# 10872
  RFE ID# 6790397


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open


From carlsonj@phorcys.east.sun.com Wed Feb 25 09:34:41 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1PHYe40009465
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 25 Feb 2009 09:34:40 -0800 (PST)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1PHYVDj021464;
	Wed, 25 Feb 2009 17:34:37 GMT
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFM00F11U5PW900@brm-avmta-1.central.sun.com>; Wed,
 25 Feb 2009 10:34:37 -0700 (MST)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFM0087KU5O5N70@brm-avmta-1.central.sun.com>; Wed,
 25 Feb 2009 10:34:36 -0700 (MST)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1PHYNkl013883; Wed,
 25 Feb 2009 12:34:23 -0500 (EST)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n1PHYNus013880; Wed,
 25 Feb 2009 12:34:23 -0500 (EST)
Date: Wed, 25 Feb 2009 12:34:23 -0500
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
To: James Walker <jw137282@sac.sfbay.sun.com>
Cc: PSARC-ext@sun.com, Lizhong.Li@sun.com
Message-id: <18853.33055.24874.341778@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
Status: RO
Content-Length: 1628

James Walker writes:
>   3.3 Services and the /etc Directory
>       (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
>       Does the project integrate anything into /etc/init.d or /etc/rc?.d?
>       [ ] Yes - ARC review required
>       [*] No

There doesn't seem to be a service for this defined.  How does the
user invoke it?  Does the user have to write his own SMF manifest?

>       Do any of the components for the project deal with passwords?
>       [ ] Yes
>       [*] No - continue to next section (section 3.4.6)

I don't think that's correct.  Mrtg can be configured with the SNMP
"community" string, which is the (weak) password used for SNMP.  The
documentation for it suggests protecting that password.

>       If yes are these passwords entered via the CLI or environment?
>       [ ] Yes - ARC review required
>       [ ] No

CLI through cfgmaker, right?

>     /usr/bin/mrtg               Uncommitted	    Perl script
>     /usr/bin/mrtg-traffic-sum   Uncommitted	    Perl script
>     /usr/bin/cfgmaker           Uncommitted	    Perl script
>     /usr/bin/indexmaker         Uncommitted	    Perl script
>     /usr/bin/rateup             Uncommitted	    Executable binary file

Why /usr/bin?  Do ordinary users invoke this?

I would have expected mrtg to be delivered as a service that can be
enabled or disabled in the usual way (svcadm).  Am I missing
something?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From James.Walker@sun.com Fri Feb 27 14:40:47 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1RMeluQ026627
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 27 Feb 2009 14:40:47 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1RMekE4003011
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 27 Feb 2009 14:40:47 -0800 (PST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFQ00K0JXNYDO00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 27 Feb 2009 14:40:46 -0800 (PST)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFQ009XEXNY30C0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 27 Feb 2009 14:40:46 -0800 (PST)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1RMeko5023069	for
 <PSARC-ext@sun.com>; Fri, 27 Feb 2009 22:40:46 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 id <0KFQ00F00WW3W900@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 27 Feb 2009 15:40:46 -0700 (MST)
Received: from [172.20.25.153] ([unknown] [172.20.25.153])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit
 (built Dec 23 2008)) with ESMTPSA id <0KFQ00HHIXNXQG00@mail-amer.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 27 Feb 2009 15:40:45 -0700 (MST)
Date: Fri, 27 Feb 2009 15:42:31 -0700
From: Jim Walker <James.Walker@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <18853.33055.24874.341778@gargle.gargle.HOWL>
Sender: James.Walker@sun.com
To: James Carlson <James.D.Carlson@sun.com>
Cc: PSARC-ext@sun.com
Reply-to: Lizhong.Li@sun.com
Message-id: <49A86C57.1090304@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.14 (X11/20080728)
Status: RO
Content-Length: 2862

(sent for Lizhong)

James,

Thanks for your comments, please check my replies below.

And I've updated the check list file according your comments:
http://greatwall.prc/~ll222647/mrtg/


James Carlson wrote:
> James Walker writes:
>   
>>   3.3 Services and the /etc Directory
>>       (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
>>       Does the project integrate anything into /etc/init.d or /etc/rc?.d?
>>       [ ] Yes - ARC review required
>>       [*] No
>>     
>
> There doesn't seem to be a service for this defined.  How does the
> user invoke it?  Does the user have to write his own SMF manifest?
>
>   
Generally people run mrtg by crontab to create the traffic statistic
info, such as:
5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/mrtg-2/bin/mrtg
/var/apache2/
2.2/htdocs/mrtg.cfg

There's no daemon  process, too. So I think it's perhaps not applicable
to be a SMF service, is it reasonable ?
>>       Do any of the components for the project deal with passwords?
>>       [ ] Yes
>>       [*] No - continue to next section (section 3.4.6)
>>     
>
> I don't think that's correct.  Mrtg can be configured with the SNMP
> "community" string, which is the (weak) password used for SNMP.  The
> documentation for it suggests protecting that password.
>
>   
Yes, I've updated it as this:

    3.4.5 Passwords
      (see
http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and

http://opensolaris.org/os/community/arc/bestpractices/passwords-files/
for details)
      Do any of the components for the project deal with passwords?
      [*] Yes
      [ ] No - continue to next section (section 3.4.6)

      If yes are these passwords entered via the CLI or environment?
      [*] Yes - ARC review required
      [ ] No

      Are passwords stored within the file system for the component?
      [*] Yes
      [ ] No - continue to next section (section 3.4.6)

      If yes are the permissions on the file such to protect exposing
the password(s)?
      [*] Yes
      [ ] No - ARC review required

>>       If yes are these passwords entered via the CLI or environment?
>>       [ ] Yes - ARC review required
>>       [ ] No
>>     
>
> CLI through cfgmaker, right?
>   
Yes.
>   
>>     /usr/bin/mrtg               Uncommitted	    Perl script
>>     /usr/bin/mrtg-traffic-sum   Uncommitted	    Perl script
>>     /usr/bin/cfgmaker           Uncommitted	    Perl script
>>     /usr/bin/indexmaker         Uncommitted	    Perl script
>>     /usr/bin/rateup             Uncommitted	    Executable binary file
>>     
>
> Why /usr/bin?  Do ordinary users invoke this?
>   
Yes, users may use these commands manually or by crontab.
> I would have expected mrtg to be delivered as a service that can be
> enabled or disabled in the usual way (svcadm).  Am I missing
> something?
>
>   


-- 
Thanks,
Lizhong


From carlsonj@phorcys.east.sun.com Fri Feb 27 14:55:46 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1RMtkGq027994
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 27 Feb 2009 14:55:46 -0800 (PST)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1RMtfal031330;
	Fri, 27 Feb 2009 15:55:43 -0700 (MST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFQ00F03YCUQ800@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 27 Feb 2009 14:55:42 -0800 (PST)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFQ00F0KYCTO600@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 27 Feb 2009 14:55:41 -0800 (PST)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1RMtdhv019279; Fri,
 27 Feb 2009 17:55:39 -0500 (EST)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n1RMtdwU019276; Fri,
 27 Feb 2009 17:55:39 -0500 (EST)
Date: Fri, 27 Feb 2009 17:55:39 -0500
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <49A86C57.1090304@sun.com>
To: Lizhong.Li@sun.com
Cc: PSARC-ext@sun.com
Message-id: <18856.28523.336478.976218@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL> <49A86C57.1090304@sun.com>
Status: RO
Content-Length: 1440

Jim Walker writes:
> And I've updated the check list file according your comments:
> http://greatwall.prc/~ll222647/mrtg/

Please archive with the materials.  That's not accessible from outside
the SWAN.

> Generally people run mrtg by crontab to create the traffic statistic
> info, such as:
> 5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/mrtg-2/bin/mrtg
> /var/apache2/
> 2.2/htdocs/mrtg.cfg
> 
> There's no daemon  process, too. So I think it's perhaps not applicable
> to be a SMF service, is it reasonable ?

OK ... I had expected there'd be more integration.

(One of the underlying issues is that cron-driven things don't really
have an SMF representation, and they should, so that users can control
them easily and so that we can ship prototype configurations.  But
that's not your problem.)

>       Are passwords stored within the file system for the component?
>       [*] Yes
>       [ ] No - continue to next section (section 3.4.6)

Should probably say something about where passwords are stored, just
for completeness.

> > Why /usr/bin?  Do ordinary users invoke this?
> >   
> Yes, users may use these commands manually or by crontab.

I did some looking around, and that seems common enough.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From James.Walker@sun.com Fri Feb 27 15:21:11 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1RNLAoF028890
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 27 Feb 2009 15:21:10 -0800 (PST)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1RNL8Oc029666
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 27 Feb 2009 23:21:09 GMT
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFQ00K0BZJ5SK00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 27 Feb 2009 15:21:05 -0800 (PST)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFQ00FLWZJ4OC10@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 27 Feb 2009 15:21:04 -0800 (PST)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1RNL4So004035	for
 <PSARC-ext@sun.com>; Fri, 27 Feb 2009 23:21:04 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 id <0KFQ00I00Z9HAE00@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 27 Feb 2009 16:21:04 -0700 (MST)
Received: from [172.20.25.153] ([unknown] [172.20.25.153])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit
 (built Dec 23 2008)) with ESMTPSA id <0KFQ00E47ZJ3TC30@mail-amer.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 27 Feb 2009 16:21:04 -0700 (MST)
Date: Fri, 27 Feb 2009 16:22:49 -0700
From: Jim Walker <James.Walker@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <18856.28523.336478.976218@gargle.gargle.HOWL>
Sender: James.Walker@sun.com
To: James Carlson <James.D.Carlson@sun.com>
Cc: Lizhong.Li@sun.com, PSARC-ext@sun.com
Reply-to: James.Walker@sun.com
Message-id: <49A875C9.50604@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL> <49A86C57.1090304@sun.com>
 <18856.28523.336478.976218@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.14 (X11/20080728)
Status: RO
Content-Length: 546

James Carlson wrote:
> Please archive with the materials.  That's not accessible from outside
> the SWAN.

I updated the proposal.txt file in the case directory.

>>       Are passwords stored within the file system for the component?
>>       [*] Yes
>>       [ ] No - continue to next section (section 3.4.6)
> 
> Should probably say something about where passwords are stored, just
> for completeness.

We will add that.

Jim,

Since we are at the timeout today. Can you give this case a +1 now,
so I can mark it closed approved?

Cheers,
Jim

From carlsonj@phorcys.east.sun.com Sat Feb 28 07:27:40 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1SFRTcm003945
	for <psarc-ext@sac.sfbay.sun.com>; Sat, 28 Feb 2009 07:27:40 -0800 (PST)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1SFRDoQ018495;
	Sat, 28 Feb 2009 15:27:15 GMT
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFS0060989D0600@brm-avmta-1.central.sun.com>; Sat,
 28 Feb 2009 08:27:13 -0700 (MST)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFS00JTQ89D4J20@brm-avmta-1.central.sun.com>; Sat,
 28 Feb 2009 08:27:13 -0700 (MST)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1SFRCAM020452; Sat,
 28 Feb 2009 10:27:12 -0500 (EST)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n1SFRBqD020449; Sat,
 28 Feb 2009 10:27:11 -0500 (EST)
Date: Sat, 28 Feb 2009 10:27:11 -0500
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <49A875C9.50604@sun.com>
To: James.Walker@sun.com
Cc: Lizhong.Li@sun.com, PSARC-ext@sun.com
Message-id: <18857.22479.955609.646594@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL> <49A86C57.1090304@sun.com>
 <18856.28523.336478.976218@gargle.gargle.HOWL> <49A875C9.50604@sun.com>
Status: RO
Content-Length: 652

Jim Walker writes:
> James Carlson wrote:
> > Please archive with the materials.  That's not accessible from outside
> > the SWAN.
> 
> I updated the proposal.txt file in the case directory.

Thanks.

> Since we are at the timeout today. Can you give this case a +1 now,
> so I can mark it closed approved?

Not sure whose "today" that was, but I'll give it a +1 now, assuming
that the password storage information is included.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Lizhong.Li@sun.com Sun Mar  1 17:46:58 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n221kvYR003090
	for <psarc-ext@sac.sfbay.sun.com>; Sun, 1 Mar 2009 17:46:57 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n221ksjp017202
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 2 Mar 2009 09:46:56 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFU0090JVM7LT00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Sun, 01 Mar 2009 17:46:55 -0800 (PST)
Received: from sineb-mail-2.sun.com ([192.18.19.7])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFU006V2VM4V610@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun,
 01 Mar 2009 17:46:53 -0800 (PST)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n221kqos021835	for
 <PSARC-ext@sun.com>; Mon, 02 Mar 2009 01:46:52 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 id <0KFU00000VEM8R00@mail-apac.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 02 Mar 2009 09:46:52 +0800 (SGT)
Received: from [129.158.219.184] ([unknown] [129.158.219.184])
 by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 with ESMTPSA id <0KFU00CCFVM2G780@mail-apac.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 02 Mar 2009 09:46:51 +0800 (SGT)
Date: Mon, 02 Mar 2009 09:48:26 +0800
From: Lizhong Li <Lizhong.Li@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <18856.28523.336478.976218@gargle.gargle.HOWL>
Sender: Lizhong.Li@sun.com
To: James Carlson <James.D.Carlson@sun.com>
Cc: PSARC-ext@sun.com
Reply-to: Lizhong.Li@sun.com
Message-id: <49AB3AEA.6030900@sun.com>
Organization: sun.com
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_GrZxN3ICwii54SNDOxfJog)"
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL> <49A86C57.1090304@sun.com>
 <18856.28523.336478.976218@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.17 (X11/20081014)
Status: RO
Content-Length: 14571

This is a multi-part message in MIME format.

--Boundary_(ID_GrZxN3ICwii54SNDOxfJog)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT



James Carlson wrote:
> Jim Walker writes:
>   
>> And I've updated the check list file according your comments:
>> http://greatwall.prc/~ll222647/mrtg/
>>     
>
> Please archive with the materials.  That's not accessible from outside
> the SWAN.
>   
Please see the attachment.
>   
>> Generally people run mrtg by crontab to create the traffic statistic
>> info, such as:
>> 5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/mrtg-2/bin/mrtg
>> /var/apache2/
>> 2.2/htdocs/mrtg.cfg
>>
>> There's no daemon  process, too. So I think it's perhaps not applicable
>> to be a SMF service, is it reasonable ?
>>     
>
> OK ... I had expected there'd be more integration.
>
> (One of the underlying issues is that cron-driven things don't really
> have an SMF representation, and they should, so that users can control
> them easily and so that we can ship prototype configurations.  But
> that's not your problem.)
>
>   
>>       Are passwords stored within the file system for the component?
>>       [*] Yes
>>       [ ] No - continue to next section (section 3.4.6)
>>     
>
> Should probably say something about where passwords are stored, just
> for completeness.
>   
Generally command 'cfgmaker' is used to introduce a config file for 
'mrtg' like this:
# cfgmaker public@192.168.1.100 > mrtg.cfg
So the 'community' password is stored in the file mrtg.cfg , it's owned 
by root and could be saved in any location. The clients from web can't 
see this file since they can just access the files allowed by apache.


>   
>>> Why /usr/bin?  Do ordinary users invoke this?
>>>   
>>>       
>> Yes, users may use these commands manually or by crontab.
>>     
>
> I did some looking around, and that seems common enough.
>
>   

-- 
Thanks,
Lizhong


--Boundary_(ID_GrZxN3ICwii54SNDOxfJog)
Content-type: text/plain; name=FCL-mrtg
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=FCL-mrtg

mrtg Check List
1.0 Project Information
1.1 Name of project/component
    mrtg

1.2 Author of document
    Lizhong.Li@Sun.COM

2.0 Project Summary
  2.1 Project Description
    MRTG - The Multi Router Traffic Grapher, is a popular tool to monitor network traffic and
    other system status.

    It monitors SNMP network devices and draws pretty pictures showing how much traffic 
    has passed through each interface. Routers are only the beginning. MRTG is being used 
    to graph all sorts of network devices as well as everything else from weather data to 
    vending machines.

    mrtg-2.16.2 will be integrated into the SFW consolidation as part of this proposal, and will
    be installed as SUNWmrtg.

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [*] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [*] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
      Tobias Oetiker <oetiker@ee.ethz.ch>
    
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [*] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [*] Yes 
      [ ] No - briefly explain
      
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [*] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [*] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [*] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [*] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [*] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [*] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [*] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [*] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      <system drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product>
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product id>\<version id>\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [ ] Yes
      [*] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [ ] Yes
      [ ] No - ARC review required
      [*] N/A
    
      Are these components already in the Solaris WOS?
      [ ] Yes
      [*] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [ ] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [ ] Yes
      [*] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [ ] Yes
      [ ] No - ARC review required
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [ ] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [*] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [*] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [*] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [*] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [*] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [ ] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [ ] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [*] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [*] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [*] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [*] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [*] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [*] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [*] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [*] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [*] Yes
      [ ] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [*] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [ ] Yes - explain below
      [*] No
      [ ] N/A
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [*] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [*] Yes
      [ ] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [*] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [*] No 
      
      Examples of Core Solaris Components include but are not limited to:
      
        Secure By Default
        Authorizations
        PAM -- Plugable Authentication Module
        Privilege
        PRM -- Process Rights Management -- Privilege
        Audit
        xVm -- Virtualization
        zones / Solaris Containers
        PRM -- Process Rights Management
        RBAC -- Role Based Access Control
        TX / Trusted Extensions
        ZFS
        SMF -- Service Management Facility
        FMA -- Fault Management Architecture
        SCF -- Smart Card Facility
        IPsec
        
4.0 Interfaces
  4.1 Exported Interfaces
  
    Interface Name			Classification      Comments
    --------------------------- 	------------------- ---------------------------
    SUNWmrtg                         Uncommitted	    Package
    /usr/bin/mrtg                    Uncommitted	    Perl script
    /usr/bin/mrtg-traffic-sum        Uncommitted	    Perl script
    /usr/bin/cfgmaker                Uncommitted	    Perl script
    /usr/bin/indexmaker              Uncommitted	    Perl script
    /usr/bin/rateup                  Uncommitted	    Executable binary file
    
  4.2 Imported Interfaces

    Interface Name		Classification       Comments
    --------------------------- -------------------- --------------------------
    SUNWgd2                    Uncommitted	     Package
    SUNWpng                    Uncommitted	     Package
    SUNWzlib                   Uncommitted	     Package    
    SUNWzlibr                  Uncommitted	     Package    
    SUNWlibms                  Uncommitted	     Package
    SUNWlibmsr                 Uncommitted	     Package
    
Appendix A - References
  [1] http://oss.oetiker.ch/mrtg/

  OSR ID# 10872
  RFE ID# 6790397


--Boundary_(ID_GrZxN3ICwii54SNDOxfJog)--

From James.Walker@Sun.COM Mon Mar  2 13:47:56 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n22Llu9p017741
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 2 Mar 2009 13:47:56 -0800 (PST)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n22LltWn013750
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 2 Mar 2009 13:47:56 -0800 (PST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFW00L0BF7VAB00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 02 Mar 2009 14:47:55 -0700 (MST)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFW00G1EF7U6I30@brm-avmta-1.central.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 02 Mar 2009 14:47:54 -0700 (MST)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n22LlsqL024978	for
 <PSARC-ext@sun.com>; Mon, 02 Mar 2009 21:47:54 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 id <0KFW00G00BRS3X00@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 02 Mar 2009 14:47:54 -0700 (MST)
Received: from [172.20.25.153] ([unknown] [172.20.25.153])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit
 (built Dec 23 2008)) with ESMTPSA id <0KFW00HFUF7868E0@mail-amer.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 02 Mar 2009 14:47:32 -0700 (MST)
Date: Mon, 02 Mar 2009 14:49:39 -0700
From: Jim Walker <James.Walker@Sun.COM>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <49AB3AEA.6030900@sun.com>
Sender: James.Walker@Sun.COM
To: Lizhong.Li@Sun.COM
Cc: James Carlson <James.D.Carlson@Sun.COM>, PSARC-ext@Sun.COM
Reply-to: James.Walker@Sun.COM
Message-id: <49AC5473.60208@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL> <49A86C57.1090304@sun.com>
 <18856.28523.336478.976218@gargle.gargle.HOWL> <49AB3AEA.6030900@sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080728)
Status: RO
Content-Length: 708

Lizhong Li wrote:
>> James Carlson wrote:
>>
>> Should probably say something about where passwords are stored, just
>> for completeness.
>>   
> Generally command 'cfgmaker' is used to introduce a config file for 
> 'mrtg' like this:
> # cfgmaker public@192.168.1.100 > mrtg.cfg
> So the 'community' password is stored in the file mrtg.cfg , it's owned 
> by root and could be saved in any location. The clients from web can't 
> see this file since they can just access the files allowed by apache.

I added this information to a Notes section in the proposal.txt file,
and marked this case closed approved.

Cheers,
Jim

-- 
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado

From Lizhong.Li@sun.com Mon Mar  2 17:18:49 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n231ImZi018684
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 2 Mar 2009 17:18:49 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n231IiYk007835
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 3 Mar 2009 01:18:48 GMT
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KFW00101OZB7R00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 02 Mar 2009 17:18:47 -0800 (PST)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFW00GZYOZ9WR90@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 02 Mar 2009 17:18:46 -0800 (PST)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n231IjPq012834	for
 <PSARC-ext@sun.com>; Tue, 03 Mar 2009 01:18:45 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 id <0KFW00K00OUNLH00@mail-apac.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Tue, 03 Mar 2009 09:18:45 +0800 (SGT)
Received: from [129.158.219.184] ([unknown] [129.158.219.184])
 by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008))
 with ESMTPSA id <0KFW00BG3OZ8BTB0@mail-apac.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Tue, 03 Mar 2009 09:18:45 +0800 (SGT)
Date: Tue, 03 Mar 2009 09:20:19 +0800
From: Lizhong Li <Lizhong.Li@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
In-reply-to: <49AC5473.60208@sun.com>
Sender: Lizhong.Li@sun.com
To: James.Walker@sun.com
Cc: James Carlson <James.D.Carlson@sun.com>, PSARC-ext@sun.com
Reply-to: Lizhong.Li@sun.com
Message-id: <49AC85D3.9060608@sun.com>
Organization: sun.com
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200902202204.n1KM4f31014842@sac.sfbay.sun.com>
 <18853.33055.24874.341778@gargle.gargle.HOWL> <49A86C57.1090304@sun.com>
 <18856.28523.336478.976218@gargle.gargle.HOWL> <49AB3AEA.6030900@sun.com>
 <49AC5473.60208@sun.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20081014)
Status: RO
Content-Length: 763

Thanks Jim, then I'll start to prepare the C-Team checklist.

Lizhong

Jim Walker wrote:
> Lizhong Li wrote:
>>> James Carlson wrote:
>>>
>>> Should probably say something about where passwords are stored, just
>>> for completeness.
>>>   
>> Generally command 'cfgmaker' is used to introduce a config file for 
>> 'mrtg' like this:
>> # cfgmaker public@192.168.1.100 > mrtg.cfg
>> So the 'community' password is stored in the file mrtg.cfg , it's 
>> owned by root and could be saved in any location. The clients from 
>> web can't see this file since they can just access the files allowed 
>> by apache.
>
> I added this information to a Notes section in the proposal.txt file,
> and marked this case closed approved.
>
> Cheers,
> Jim
>

-- 
Thanks,
Lizhong


From James.Walker@sun.com Mon Apr 20 17:53:58 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3L0rwAK002685
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 20 Apr 2009 17:53:58 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3L0ruMI012194
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 20 Apr 2009 17:53:57 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIF00L05EHWRM00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@Sun.Com); Mon, 20 Apr 2009 18:53:56 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIF0097QEHVDKB0@brm-avmta-1.central.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Mon,
 20 Apr 2009 18:53:55 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3L0rth8016265	for
 <PSARC-ext@Sun.Com>; Tue, 21 Apr 2009 00:53:55 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIF00300E84L200@mail-amer.sun.com> for PSARC-ext@Sun.Com
 (ORCPT PSARC-ext@Sun.Com); Mon, 20 Apr 2009 18:53:55 -0600 (MDT)
Received: from [172.20.25.153] ([unknown] [172.20.25.153])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KIF002SFEHV6KC0@mail-amer.sun.com> for
 PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Mon,
 20 Apr 2009 18:53:55 -0600 (MDT)
Date: Mon, 20 Apr 2009 19:01:46 -0600
From: Jim Walker <James.Walker@sun.com>
Subject: mrtg [PSARC/2009/120 FastTrack timeout 04/22/2009]
Sender: James.Walker@sun.com
To: PSARC-ext@sun.com
Cc: Lizhong.Li@sun.com
Reply-to: James.Walker@sun.com
Message-id: <49ED1AFA.2090506@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
User-Agent: Thunderbird 2.0.0.14 (X11/20080728)
Status: RO
Content-Length: 2032

I'm reopening this case for comments to allow the addition of the
following two Project Private directories:

     /usr/lib/mrtg2/             Project Private     Perl scripts
     /usr/share/mrtg2/           Project Private     Icon and Image files

Since I don't think these changes are controversial and don't
effect public interfaces, I don't think a separate case is required.
The proposal.txt file in the case directory has been updated.

I plan to reclose the case on 4/22/2009 unless there are issues.

Cheers,
Jim

+++

2.0 Project Summary
   2.1 Project Description
     MRTG - The Multi Router Traffic Grapher, is a popular tool to monitor
     network traffic and other system status.
...

Here is the complete interface description:

4.0 Interfaces
   4.1 Exported Interfaces

     Interface Name		Classification      Comments
     -------------------------- 	------------------- -------------------------
     SUNWmrtg                    Uncommitted	    Package
     /usr/bin/mrtg               Uncommitted	    Perl script
     /usr/bin/mrtg-traffic-sum   Uncommitted	    Perl script
     /usr/bin/cfgmaker           Uncommitted	    Perl script
     /usr/bin/indexmaker         Uncommitted	    Perl script
     /usr/bin/rateup             Uncommitted	    Executable binary file

     /usr/lib/mrtg2/             Project Private     Perl scripts
     /usr/share/mrtg2/           Project Private     Icon and Image files

   4.2 Imported Interfaces

     Interface Name		Classification 	Comments
     -------------------------- 	--------------	----------------------
     SUNWgd2                   	Uncommitted	Graphics Draw Package
     SUNWpng                   	Volatile	PNG Package
     SUNWzlib                   	Committed	Zip Package
     SUNWzlibr                  	Committed	Zip Package (Root)
     SUNWlibms                  	Committed	Math Package
     SUNWlibmsr                 	Committed	Math Package (Root)

Appendix A - References
   [1] http://oss.oetiker.ch/mrtg/

   OSR ID# 10872
   RFE ID# 6790397


From James.Walker@sun.com Wed Apr 22 20:37:01 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3N3b1gc022534
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 22 Apr 2009 20:37:01 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3N3ausZ011997
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 23 Apr 2009 11:36:59 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIJ00501BDMS600@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Wed, 22 Apr 2009 20:36:58 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIJ00020BDLFU50@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed,
 22 Apr 2009 20:36:57 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3N3avmo005472	for
 <PSARC-ext@sun.com>; Thu, 23 Apr 2009 03:36:57 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIJ00100B2ES300@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Wed, 22 Apr 2009 21:36:57 -0600 (MDT)
Received: from [172.20.25.153] ([unknown] [172.20.25.153])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KIJ00FSUBDKAR40@mail-amer.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed,
 22 Apr 2009 21:36:57 -0600 (MDT)
Date: Wed, 22 Apr 2009 21:45:03 -0600
From: Jim Walker <James.Walker@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 04/22/2009]
In-reply-to: <49ED1AFA.2090506@sun.com>
Sender: James.Walker@sun.com
To: PSARC-ext@sun.com
Cc: Lizhong.Li@sun.com
Reply-to: James.Walker@sun.com
Message-id: <49EFE43F.8060303@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <49ED1AFA.2090506@sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080728)
Status: RO
Content-Length: 628

Can a member give this a +1 so I can close it?

Thanks,
Jim

Jim Walker wrote:
> I'm reopening this case for comments to allow the addition of the
> following two Project Private directories:
> 
>     /usr/lib/mrtg2/             Project Private     Perl scripts
>     /usr/share/mrtg2/           Project Private     Icon and Image files
> 
> Since I don't think these changes are controversial and don't
> effect public interfaces, I don't think a separate case is required.
> The proposal.txt file in the case directory has been updated.
> 
> I plan to reclose the case on 4/22/2009 unless there are issues.
> 
> Cheers,
> Jim

From Mark.Carlson@sun.com Fri Apr 24 05:03:17 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3OC3Grd025735
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 24 Apr 2009 05:03:16 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3OC37Pf004532
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 24 Apr 2009 05:03:16 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIL00423THERX00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 24 Apr 2009 06:03:14 -0600 (MDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIL00MTYTHCFM70@brm-avmta-1.central.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 24 Apr 2009 06:03:13 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3OC3CvZ005215	for
 <PSARC-ext@sun.com>; Fri, 24 Apr 2009 12:03:12 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIL00L00TA2B300@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 24 Apr 2009 06:03:12 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [71.237.94.98])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KIL0074ATHCH870@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 24 Apr 2009 06:03:12 -0600 (MDT)
Date: Fri, 24 Apr 2009 06:03:12 -0600
From: "Mark A. Carlson" <Mark.Carlson@sun.com>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 04/22/2009]
In-reply-to: <49EFE43F.8060303@sun.com>
Sender: Mark.Carlson@sun.com
To: James.Walker@sun.com
Cc: PSARC-ext@sun.com, Lizhong.Li@sun.com
Message-id: <49F1AA80.5020905@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_oUnUl14MBy8xldj4eAOMNA)"
X-PMX-Version: 5.4.1.325704
References: <49ED1AFA.2090506@sun.com> <49EFE43F.8060303@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 3434

This is a multi-part message in MIME format.

--Boundary_(ID_oUnUl14MBy8xldj4eAOMNA)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

+1

-- mark

Jim Walker wrote:
> Can a member give this a +1 so I can close it?
>
> Thanks,
> Jim
>
> Jim Walker wrote:
>> I'm reopening this case for comments to allow the addition of the
>> following two Project Private directories:
>>
>>     /usr/lib/mrtg2/             Project Private     Perl scripts
>>     /usr/share/mrtg2/           Project Private     Icon and Image files
>>
>> Since I don't think these changes are controversial and don't
>> effect public interfaces, I don't think a separate case is required.
>> The proposal.txt file in the case directory has been updated.
>>
>> I plan to reclose the case on 4/22/2009 unless there are issues.
>>
>> Cheers,
>> Jim

-- 
<http://www.sun.com> 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	



--Boundary_(ID_oUnUl14MBy8xldj4eAOMNA)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>+1<br>
<br>
-- mark<br>
</tt><br>
Jim Walker wrote:
<blockquote cite="mid:49EFE43F.8060303@sun.com" type="cite">Can a
member give this a +1 so I can close it?
  <br>
  <br>
Thanks,
  <br>
Jim
  <br>
  <br>
Jim Walker wrote:
  <br>
  <blockquote type="cite">I'm reopening this case for comments to allow
the addition of the
    <br>
following two Project Private directories:
    <br>
    <br>
&nbsp;&nbsp;&nbsp; /usr/lib/mrtg2/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Project Private&nbsp;&nbsp;&nbsp;&nbsp; Perl scripts
    <br>
&nbsp;&nbsp;&nbsp; /usr/share/mrtg2/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Project Private&nbsp;&nbsp;&nbsp;&nbsp; Icon and Image
files
    <br>
    <br>
Since I don't think these changes are controversial and don't
    <br>
effect public interfaces, I don't think a separate case is required.
    <br>
The proposal.txt file in the case directory has been updated.
    <br>
    <br>
I plan to reclose the case on 4/22/2009 unless there are issues.
    <br>
    <br>
Cheers,
    <br>
Jim
    <br>
  </blockquote>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title></title>
<table border="0" cellpadding="0" cellspacing="0" width="519">
  <tbody>
    <tr valign="top">
      <td height="121" width="98"><a moz-do-not-send="true"
 href="http://www.sun.com"><img moz-do-not-send="true"
 src="http://www.sun.com/emrkt/sigs/6h_top.gif" border="0" height="92"
 width="98"></a></td>
      <td style="font-family: Arial; font-size: 10px;" height="121"
 width="249"><b> Mark A. Carlson </b><br>
Sr. Architect<br>
      <br>
      <b>Systems Group</b><br>
Phone x69559 / 303-223-6139<br>
Email <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
 href="mailto:Mark.Carlson@Sun.COM">Mark.Carlson@Sun.COM</a><br>
      </td>
      <td style="font-family: Arial; font-size: 10px;" width="172"><img
 moz-do-not-send="true" src="http://www.sun.com/emrkt/sigs/q12.gif"
 height="118" width="172"></td>
    </tr>
  </tbody>
</table>
<div class="moz-signature"><br>
</div>
</div>
</body>
</html>

--Boundary_(ID_oUnUl14MBy8xldj4eAOMNA)--

From James.Walker@Sun.COM Fri Apr 24 14:04:29 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3OL4Ti7029614
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 24 Apr 2009 14:04:29 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3OL4RQV028876
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sat, 25 Apr 2009 05:04:28 +0800 (SGT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIM00C01IJFXW00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 24 Apr 2009 15:04:27 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIM00CRQIJE0U00@brm-avmta-1.central.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 24 Apr 2009 15:04:26 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3OL4Qsb001596	for
 <PSARC-ext@sun.com>; Fri, 24 Apr 2009 21:04:26 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIM00200IAUS200@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 24 Apr 2009 15:04:26 -0600 (MDT)
Received: from [172.20.25.153] ([unknown] [172.20.25.153])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KIM00MP3IJ8Z790@mail-amer.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 24 Apr 2009 15:04:21 -0600 (MDT)
Date: Fri, 24 Apr 2009 15:12:39 -0600
From: Jim Walker <James.Walker@Sun.COM>
Subject: Re: mrtg [PSARC/2009/120 FastTrack timeout 04/22/2009]
In-reply-to: <49F1AA80.5020905@sun.com>
Sender: James.Walker@Sun.COM
To: PSARC-ext@Sun.COM
Cc: Lizhong.Li@Sun.COM
Reply-to: James.Walker@Sun.COM
Message-id: <49F22B47.7020601@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <49ED1AFA.2090506@sun.com> <49EFE43F.8060303@sun.com>
 <49F1AA80.5020905@sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080728)
Status: RO
Content-Length: 83

The update was approved. I'm marking this case closed approved again.

Cheers,
Jim

