Gary Winiger wrote: >>From Phi.Tran at sun.com Wed Feb 13 12:34:52 2008 >>Date: Wed, 13 Feb 2008 12:44:12 -0800 >>From: Phi Tran <Phi.Tran at sun.com> >>Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout >> 01/23/2008] >>To: Gary Winiger <gww at eng.sun.com> >>Cc: PSARC-ext at sun.com, dchieu at sac.sfbay.sun.com, solaris-battery-team >>at sun.com, >> tamarack-core at sun.com, x86power-iteam at sun.com >>Content-transfer-encoding: 7BIT >>X-Accept-Language: en-us, en >>User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 >> >>Gary Winiger wrote: >> >>>>Lid >>>>--- >>>> >>>>GPM allows the user to set actions for lid close such as suspend, >>>>hibernate, and shutdown. Suspend and hibernate actions will be >>>> >>>>Power Button >>>>------------ >>>> >>>>GPM allows for the configuration of power button actions such as >>>>shutdown, suspend, and hibernate. These actions will be allowed >>> >>> >>> How does this project meet the audit requirements for >>> auditing a system discontinuity? >>> >>> Before this project, when the system is shutdown (halt(1M), >>> reboot(1M), uadmin(1M)), an audit record is written indicating >>> the start of a discontinuity, the audit trail is flushed to >>> disk, the current audit trail file closed, the audit service is >>> temporarially disabled. Upon reboot, the kernel genereates >>> a boot audit record. When the audit service is started >>> during svc.startd processing, a new audit trail file is created >>> and the boot audit record is recorded in that file. >>> >>> Note also prom entry and exit are audited. >>> >>>Gary.. >> >>The base calls will be init(1M), reboot(1M), and uadmin(1M) which are >>all audited like you said. Are you saying the auditing there isn't >>sufficient? > > > Are you saying you run init/reboot/uadmin (but not halt) in the > full context of the user? If so that's sufficient for initiating > the discontinuity. > When the system comes out of suspended animation, is kernel main() > run?
Yes, the init/reboot/uadmin calls run in the full context of the user. Halt is not used since it doesn't shut down SMF services cleanly. The kernel was suspended, so on a resume like any suspended process would start running again. That's my simplified answer :), but the power management group would have more details if needed. Phi
