The timer having been reached, there being no outstanding issues, there being a positive acknowledgement +1, I've marked this case as closed approved.
Dan Daniel Hain wrote: > I'm sponsoring this fast-track for Abhinandan Ekande from RPE. The > exposure is > open, and we're seeking patch binding. Timeout is set for 04/10/2009. > > -Dan > > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > Add zone support to uprintf() and vuprintf() > > 1.2. Name of Document Author/Supplier: > Abhinandan.Ekande at Sun.COM > > 1.3. Date of This Document: > 04/03/09 > 1.3.1. Date this project was conceived: > 02/17/09 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > Solaris PAC > 1.4.2. The ARC(s) you expect to review your project: > PSARC > 1.4.3. The Director/VP who is "Sponsoring" this project: > Sanjay.Pandit at sun.com > 1.4.4. The name of your business unit: > Solaris Revenue Product Engineering (RPE) > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: ken.yan at sun.com > 1.5.2. Responsible Engineer: abhinandan.ekande at sun.com > 1.5.3. Marketing Manager: > 1.5.4. Interest List: > > 2. Project Summary > 2.1. Project Description: > > This fast-track proposes to extend the behavior of vuprintf() > and uprintf() routines to log message to user tty and global > zones's syslog and also to non-global zone's syslog. Currently > these routines log message to user tty and global zones's syslog. > > 2.2. Risks and Assumptions: > There are no risks and assumptions. > > 4. Technical Description: > 4.1. Details: > When the user process gets killed due to hardware uncorrectable > error we would like to log the message on user tty. The kernel > has a uprintf() routine which outputs the message to user tty > and in addition logs it into syslog. But when process gets killed > in non-global zone due to uncorrectable error, the uprintf() > sends the message to user tty and to global's zone's syslog, but > not to the non-global zone's syslog. And currently there is no > printf in kernel to log message to non-global zone's syslog. > Therefore we propose modification to behavior of uprintf() and > vuprintf() routines to log message to both global and non-global > zone's syslog and as well to log the message on user tty. > > 4.2. Bug/RFE Number(s): > 6676374 If Solaris Kills a process, the user needs to know why > 4.5. Interfaces: > The interfaces change here is behaviour change of the routines > uprintf() and vuprintf(), to log message to global zone's > syslog and to user tty and as well to non-global zone's syslog. > We do not plan to change the current stability level for uprintf() > and vuprintf() routines. > > Note: uprintf() was declared Contract Private in PSARC/2001/599. > As this is now an obsolete term the interface classification is > Contracted Consolidation Private. The SAM-QFS teams (Development > and Sustaining) will be notified of the change in behavior the > functions. > 5. Reference Documents: > 6676374 If Solaris Kills a process, the user needs to know why > > 6. Resources and Schedule: > 6.1. Projected Availability: > FY09Q04 > > 6.2. Cost of Effort: > 1 man month > > 6.4. Product Approval Committee requested information: > 6.4.1. Consolidation or Component Name: ON > 6.4.3. Type of CPT Review and Approval expected: > FastTrack > 6.4.4. Project Boundary Conditions: > N/A > 6.4.5. Is this a necessary project for OEM agreements: > NO > 6.4.6. Notes: > None > 6.4.7. Target RTI Date/Release: > S11 - May 2009, S10U8 - June 2009 > 6.4.8. Target Code Design Review Date: April 2009 > > 6.5. ARC review type: > FastTrack > 6.6. ARC Exposure: > OPEN > -- Dan Hain Solaris Revenue Product Engineering (RPE) http://namefinder/NameFinder?nfquery=-s+88796 -------------------------------------------------------------- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --------------------------------------------------------------
