From lianep@nihil.sfbay.sun.com Wed Nov 11 12:47:33 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 nABKlWqK005200 for ; Wed, 11 Nov 2009 12:47:32 -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 nABKlEG7014288 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 11 Nov 2009 20:47:26 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 <0KSY00C03PR0UW00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Nov 2009 13:47:24 -0700 (MST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSY006SHPQZN540@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Nov 2009 13:47:24 -0700 (MST) Received: from nihil.sfbay.sun.com (nihil.SFBay.Sun.COM [129.146.228.161]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nABKlMs5020389; Wed, 11 Nov 2009 12:47:22 -0800 (PST) Received: from nihil.sfbay.sun.com (localhost [127.0.0.1]) by nihil.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id nABKdnnS005967; Wed, 11 Nov 2009 12:39:49 -0800 (PST) Received: (from lianep@localhost) by nihil.sfbay.sun.com (8.14.3+Sun/8.14.3/Submit) id nABKdnaQ005964; Wed, 11 Nov 2009 12:39:49 -0800 (PST) Date: Wed, 11 Nov 2009 12:39:49 -0800 (PST) From: Liane Praza Subject: Software Events Notification Parameters CLI [PSARC/2009/617 FastTrack timeout 11/18/2009] To: PSARC-ext@sun.com Cc: antonello.cruz@sun.com Message-id: <200911112039.nABKdnaQ005964@nihil.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 12612 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Software Events Notification Parameters CLI 1.2. Name of Document Author/Supplier: Author: Antonello Cruz 1.3 Date of This Document: 11 November, 2009 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: Software Events Notification Parameters CLI 1.2. Name of Document Author/Supplier: Author: Antonello Cruz 1.3. Date of This Document: 11/11/2009 1.5. Email Aliases: 1.5.1. Responsible Manager: William.Wahl@sun.com 1.5.2. Responsible Engineer: Antonello.Cruz@Sun.COM 4. Technical Description: 4.1. Details: This project introduces a common SMF facility to configure parameters for software event notification. These parameters will be stored in the SMF repository and consumed by notification daemons which implement various forms of notifications. Separate cases will be brought for each type of notification -- SMTP and SNMP are initially introduced by concurrently running cases. SMF state transitions may generate software events which are dispatched to the notification daemons for processing. Software events will always be generated for instances that transition to or from maintenance. Software events will be generated by a state transition if notification parameters exist for that transition. This case introduces new subcommands to svccfg(1M) to provide a command line interface for software events notification parameters. It allows configuration of those parameters through SMF manifests and profiles. It also introduces new libscf(3LIB) interfaces that facilitate the implementation of notification daemons. These features are described in the included diffs for smf(5) and svccfg(1M) below. 4.5. Interfaces: DTD extensions -------------- Notification parameters can be defined in the service manifest or profile. An updated DTD and diffs are provided in the case materials. An example of how to define notification parameters in a service manifest or profile can be found in the attached diffs for smf(5). New exported interface Stability Binding --------------------------------------------------------------- setnotify subcommand of svccfg(1M) Committed Patch listnotify subcommand of svccfg(1M) Committed Patch delnotify subcommand of svccfg(1M) Committed Patch smf_state_to_string(3SCF) Committed Patch smf_state_from_string(3SCF) Committed Patch smf_notify_set_params(3SCF) Committed Patch smf_notify_get_params(3SCF) Committed Patch smf_notify_del_params(3SCF) Committed Patch Imported Interface Stability ------------------------------- ------------ libnvpair(3LIB) Committed (PSARC/2000/212) libfmevent(3LIB) Committed (PSARC/2009/573) 4.6. Doc Impact: Manpage diffs for smf(5) and svccfg(1M) are included. Diffs for the remaining manpages, libscf.3lib.diff, service_bundle.dtd.1, service_bundle.dtd.1.diff, smf_enable_instance.3scf.diff, and smf_notify_get_params.3scf are included in the case directory. 5. Manpage diffs --- smf.5.old Tue Oct 27 15:24:49 2009 +++ smf.5.new Tue Nov 10 16:20:30 2009 @@ -207,6 +207,106 @@ States can also have transitions that result in a return to the originating state. + Event Notifications + SMF allows notification via SNMP or SMTP of state transitions. + It publishes software events for state transitions which are + consumed by notification daemons like snmp-notify(1M) and + smtp-notify(1M). + + SMF state transitions of disabled services will not generate + notifications unless the final state for the transition is + disabled and there exist notification parameters for that + transition. Notification will not be generated for + transitions that have the same initial and final state. + + Notification Parameters + Notification parameters for FMA Events are stored in + svc:/system/fm/notify-params:default except for Software + Events generated by SMF state transitions. They are stored + in the service or in the instance of the transitioning + service. + + Notification parameters for SMF state transition generated + events can be set system wide in + svc:/system/svc/global:default. The system wide notification + parameters will be used when a composed lookup, as in + scf_instance_get_pg_composed(3SCF), in the transitioning + instace cannot be found. + + Notification parameters can be manipulated using svccfg(1M). + + Notification parameters can be configured in a service + manifest or profile using the notification_parameters + element described in the DTD. An example is provided below. + + + + + + + + + + + + + events is a comma separated list of SMF state transition + sets or a comma separated list of FMA event classes. events + cannot have a mix of SMF state transition sets and FMA event + classes. + + For convenience, the tags + problem-{diagnosed,updated,repaired,resolved} describe the + lifecycle of a problem diagnosed by the FMA subsystem - from + initial diagnosis to interim updates and finally problem + closure. These tags are aliases for underlying FMA protocol + event classes (all in the "list.*" hierarchy) but the latter + should not be used in configuring notification preferences. + + problem-diagnosed + A new problem has been diagnosed by the FMA + subsystem. The diagnosis includes a list of one or + more suspects, which (where appropriate) may have + been automatically isolated to prevent further + errors occuring. The problem is identified by a + UUID in the event payload, and further events + describing the resolution lifecycle of this problem + will quote a matching UUID. + + problem-updated + One or more of the suspect resources in a problem + diagnosis has been repaired, replaced or acquitted + (or has been faulted again), but there remains at + least one faulted resource in the list. A "repair" + could be the result of an fmadm command line (fmadm + repaired, fmadm acquit, fmadm replaced) or may have + been detected automatically such as through + detection of a part serial number change. + + problem-repaired + All of the suspect resources in a problem diagnosis + have been repaired, resolved or acquitted. Some or + all of the resources may still be isolated at this + stage. + + problem-resolved + All of the suspect resources in a problem diagnosis + have been repaired resolved or acquitted *and* are + no longer isolated (for example a cpu that was a + suspect and offlined is now back online again; this + un-isolate action is usually automatic). + + State Transition Sets are defined as: + + to- Set of all transitions that have + as the final state of the transition. + + form- Set of all transitions that have + as the initial state of the transition. + + Set of all transitions that have + as either the initial or final state of + the transition. + + Valid values of are maintenance, offline, disabled, + online and degraded. An example of a transitions set + definition: maintenance,from-online,to-degraded + Properties and Property Groups The dependencies, methods, delegated restarter, and instance state mentioned above are represented as properties or pro- --- svccfg.1m.old Tue Oct 27 15:25:00 2009 +++ svccfg.1m.new Tue Nov 10 15:46:40 2009 @@ -458,6 +458,62 @@ smf_security(5) for the privileges required to modify properties. + Notification Parameters Subcommands + setnotify {[-g] tset | class} ... + + Sets notifications parameters for software events and + Fault Management problem lifecycle events in the SMF + repository. + + class: comma separated list of FMA Event classes or + aliases. See smf(5) Notification Parameters. + tset: comma separated list of SMF state transitions. + See smf(5) Notification Parameters. + notification parameters: URI format for each + notification mechanism implemented; for smtp use + mailto:[?=[&=]] + or mailto:{[active]|inactive} + and for SNMP traps use snmp:{[active]|inactive} + + The parameter msg_template defined in smtp-notify(1M) + can be set as a header value in the mailto URI. + E. g. mailto:root@localhost?msg_template= + + SNMP traps are directed to the host as defined by the + trapsink directive in /etc/net-snmp/snmp/snmpd.conf or + as specified by the SNMP trap notification daemon, see + snmp-notify(1M). + + The notification parameters are specific to the class or + tset specified and will overwrite pre-existing + notification parameters. The active/inactive form does + not overwrite previous notification parameters. It just + switches on/off the notification mechanism for the + specified class or tset. Setting notification parameters + implicitly sets them active. + + The -g option is used to set system wide notification + parameters for SMF state transition, see smf(5). These + notification parameters are set in + svc:/system/svc/global:default regardless of any svccfg + current selection. This subcommand refresheses all + instances it modifies. + + listnotify <[-g] tset | class> + + Displays the existing notification parameters for the + specified class or tset. If the '-g' option is used, the + notification parameters in + svc:/system/svc/global:default are displayed. + + delnotify <[-g] tset | class> + + Delete the existing notification parameters for the + specified class or tset. If the '-g' option is used, the + notification parameters in + svc:/system/svc/global:default are deleted. + Snapshot Navigation and Selection Subcommands listsnap @@ -551,6 +607,36 @@ appropriate entry from /etc/ttydefs ... + Example 7 Configuring notification preferences for SMF + service state transition events + + # svccfg setnotify -g from-online,to-maintenance \ + mailto:admin@somehost.com + + Example 8 Enabling email notifications for Fault Management + events + + # svccfg setnotify problem-diagnosed,problem-updated \ + mailto:admin@somehost.com snmp: + + Example 9 Listing notification settings for Fault + Management events + + # svccfg listnotify problem-diagnosed,problem-updated + Event: problem-diagnosed + Notification Type: smtp + active: true + to: admin@somehost.com + Notification Type: snmp + active: true + + Event: problem-updated + Notification Type: smtp + active: true + to: admin@somehost.com + Notification Type: snmp + active: true + ENVIRONMENTAL VARIABLES EDITOR 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From gww@sac.sfbay.sun.com Tue Nov 17 18:10:19 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 nAI2AIjk013176 for ; Tue, 17 Nov 2009 18:10:18 -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 nAI2AFrB002193 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 18 Nov 2009 02:10:17 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 <0KTA00L0F8P4ZQ00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 17 Nov 2009 18:10:16 -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 <0KTA000E18P39Y60@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 17 Nov 2009 18:10:15 -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.4) with ESMTP id nAI2AFOo015238; Tue, 17 Nov 2009 18:10:15 -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 nAI2AE7n013173; Tue, 17 Nov 2009 18:10:14 -0800 (PST) Received: (from gww@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id nAI2AEAX013172; Tue, 17 Nov 2009 18:10:14 -0800 (PST) Date: Tue, 17 Nov 2009 18:10:14 -0800 (PST) From: Gary Winiger Subject: Re: Software Events Notification Parameters CLI [PSARC/2009/617 FastTrack timeout 11/18/2009] To: PSARC-ext@sun.com, lianep@nihil.sfbay.sun.com Cc: antonello.cruz@sun.com Message-id: <200911180210.nAI2AEAX013172@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 499 > New exported interface Stability Binding > --------------------------------------------------------------- > setnotify subcommand of svccfg(1M) Committed Patch > listnotify subcommand of svccfg(1M) Committed Patch > delnotify subcommand of svccfg(1M) Committed Patch It seems to me that setnotify and delnotify would qualify as auditable administrative actions. I see no mention of audit. Gary.. From Antonello.Cruz@sun.com Thu Nov 19 17:12:04 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 nAK1C4SZ027932 for ; Thu, 19 Nov 2009 17:12:04 -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.4) with ESMTP id nAK1Bm8Q010899 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 20 Nov 2009 01:12:03 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 <0KTD00E0BVC23V00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 19 Nov 2009 17:12:02 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KTD002X5VC21UA0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 19 Nov 2009 17:12:02 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nAK1C2de019515 for ; Thu, 19 Nov 2009 17:12:02 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KTD00500V8BNX00@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 19 Nov 2009 17:12:02 -0800 (PST) Received: from [10.0.0.125] ([unknown] [76.21.7.211]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KTD00I9GVBXZ3B0@fe-sfbay-10.sun.com>; Thu, 19 Nov 2009 17:12:02 -0800 (PST) Date: Thu, 19 Nov 2009 17:11:57 -0800 From: Antonello Cruz Subject: Re: Software Events Notification Parameters CLI [PSARC/2009/617 FastTrack timeout 11/18/2009] In-reply-to: <200911180210.nAI2AEAX013172@sac.sfbay.sun.com> Sender: Antonello.Cruz@sun.com To: Gary Winiger Cc: PSARC-ext@sun.com, lianep@nihil.sfbay.sun.com Message-id: <4B05ECDD.5060605@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200911180210.nAI2AEAX013172@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091027) Status: RO Content-Length: 839 Gary, setnotfy and delnotify are just wrappers that create and delete properties and property groups. The auditing of these operations are handled by the standard property and property group add/modify/delete audit records. Do you think a more robust auditing is required here? Thanks, Antonello Gary Winiger wrote: >> New exported interface Stability Binding >> --------------------------------------------------------------- >> setnotify subcommand of svccfg(1M) Committed Patch >> listnotify subcommand of svccfg(1M) Committed Patch >> delnotify subcommand of svccfg(1M) Committed Patch > > It seems to me that setnotify and delnotify would qualify > as auditable administrative actions. I see no mention of > audit. > > Gary.. From gww@sac.sfbay.sun.com Fri Nov 20 10:40:47 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nAKIekdK029587 for ; Fri, 20 Nov 2009 10:40:47 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nAKIejLA026844 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 20 Nov 2009 12:40:46 -0600 (CST) 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 <0KTF006037VY4H00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 20 Nov 2009 10:40:46 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KTF00JS27VWRI90@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 20 Nov 2009 10:40:44 -0800 (PST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nAKIehtV008150; Fri, 20 Nov 2009 10:40: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 nAKIeh6W029584; Fri, 20 Nov 2009 10:40:43 -0800 (PST) Received: (from gww@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id nAKIehbd029583; Fri, 20 Nov 2009 10:40:43 -0800 (PST) Date: Fri, 20 Nov 2009 10:40:43 -0800 (PST) From: Gary Winiger Subject: Re: Software Events Notification Parameters CLI [PSARC/2009/617 FastTrack timeout 11/18/2009] To: Antonello.Cruz@sun.com Cc: PSARC-ext@sun.com, lianep@nihil.sfbay.sun.com Message-id: <200911201840.nAKIehbd029583@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 852 > setnotfy and delnotify are just wrappers that create and delete > properties and property groups. The auditing of these operations are > handled by the standard property and property group add/modify/delete > audit records. Do you think a more robust auditing is required here? OK, thanks. +1 Gary.. > Gary Winiger wrote: > >> New exported interface Stability Binding > >> --------------------------------------------------------------- > >> setnotify subcommand of svccfg(1M) Committed Patch > >> listnotify subcommand of svccfg(1M) Committed Patch > >> delnotify subcommand of svccfg(1M) Committed Patch > > > > It seems to me that setnotify and delnotify would qualify > > as auditable administrative actions. I see no mention of > > audit. From liane.praza@sun.com Fri Nov 20 11:15:13 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 nAKJFDQ4000225 for ; Fri, 20 Nov 2009 11:15:13 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id nAKJFBB5040319; Fri, 20 Nov 2009 12:15:12 -0700 (MST) 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 <0KTF0080L9HCA600@nwk-avmta-2.sfbay.sun.com>; Fri, 20 Nov 2009 11:15:12 -0800 (PST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KTF00J9F9HBRKC0@nwk-avmta-2.sfbay.sun.com>; Fri, 20 Nov 2009 11:15:11 -0800 (PST) Received: from [129.146.228.161] (nihil.SFBay.Sun.COM [129.146.228.161]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id nAKJF9es997154; Fri, 20 Nov 2009 11:15:09 -0800 (PST) Date: Fri, 20 Nov 2009 11:15:11 -0800 From: Liane Praza Subject: Re: Software Events Notification Parameters CLI [PSARC/2009/617 FastTrack timeout 11/18/2009] In-reply-to: <200911201840.nAKIehbd029583@sac.sfbay.sun.com> To: Gary Winiger Cc: Antonello.Cruz@sun.com, PSARC-ext@sun.com, lianep@nihil.sfbay.sun.com Message-id: <4B06EABF.5010802@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200911201840.nAKIehbd029583@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091027) Status: RO Content-Length: 134 This case was approved at this weeks meeting pending the requisite +1, which it now has. I've marked it as approved. thanks, liane From liane.praza@oracle.com Wed Jun 23 16:38:58 2010 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 o5NNcw5J004743 for ; Wed, 23 Jun 2010 16:38: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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5NNcwFO027050 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 23 Jun 2010 16:38:58 -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 <0L4H00D05R0Y8400@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 23 Jun 2010 17:38:58 -0600 (MDT) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L4H00BKCR0XKA00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 23 Jun 2010 17:38:58 -0600 (MDT) Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id o5NNcvxW002586 for ; Wed, 23 Jun 2010 23:38:57 +0000 (GMT) Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o5NLPi5F021720 for ; Wed, 23 Jun 2010 23:38:56 +0000 (GMT) Received: from abhmt014.oracle.com by acsmt353.oracle.com with ESMTP id 352037771277336284; Wed, 23 Jun 2010 16:38:04 -0700 Received: from [129.146.228.161] (/129.146.228.161) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 23 Jun 2010 16:38:04 -0700 Date: Wed, 23 Jun 2010 16:38:03 -0700 From: Liane Praza Subject: Minor addendum to PSARC/2009/617 Software Events Notification Parameters CLI To: psarc-ext@sun.com Cc: Antonello Cruz Message-id: <4C229ADB.3030202@oracle.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090206.4C229B10.0136:SCFMA4539814,ss=1,fgs=0 User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.9) Gecko/20100607 Lightning/1.0b1 Thunderbird/3.0.4 Status: RO Content-Length: 1395 I believe this is an obvious update to this case. If anyone disagrees, let me know and I'll run it separately. During the implementation of this work, the team determined that a simple way to display all notification parameters on the system was desirable. svcs -n is introduced to achieve that goal, and has the same output format as the svccfg subcommand already introduced by this case. The -n option to svcs will be committed. For reference, the manpage diffs are: --- svcs.1m.old Mon Jun 21 15:30:10 2010 +++ svcs.1m.new Mon Jun 21 15:39:42 2010 @@ -11,6 +11,8 @@ svcs {-d | -D} [-Hpv?] [-o col[,col]]... [-sS col]... [FMRI | pattern] ... + svcs -n [FMRI | pattern]... + svcs -l [-v] [FMRI | pattern]... svcs -x [-v] [FMRI]... @@ -163,6 +165,13 @@ specific milestone. See svcadm(1M) for details. + -n Prints the notification parameters (see + SMF(5)). It always prints the FMA events + notification parameters and the system + wide SMF state transition notification + parameters, regardless of the FMRI or + pattern selected. + -o col[,col]... Prints the specified columns. Each col should be a column name. See COLUMNS below for available columns. liane