Hey thank you ppl for your efforts... I had to log off early last evening and hence didn't follow the thread.. really good work mates...
Cheers, Prasath -----Original Message----- From: Tom Whitten [mailto:thomas.whit...@sun.com] Sent: Thursday, July 30, 2009 4:45 AM To: Alexandre Dumont Cc: Prasath Srinivasan (WT01 - Telecom Equipment); smf-discuss at opensolaris.org Subject: Re: [smf-discuss] svcs -l command Cool. Thanks for running the experiment. tom Alexandre Dumont writes: > adumont$ who -b > system boot 2009-07-27 22:07 > > In my case, as you suggested vbox:test01 was disabled before reboot (Jul 23 > 20:22:38). In the log I can see: ... > > So, based on this you seem to be right: after being enabled for the first > time since last reboot, the restarter/logfile property is populated and svcs > shows it again. > > Alex > > On Wed, Jul 29, 2009 at 11:38 PM, Tom Whitten <thomas.whitten at sun.com>wrote: > > > OK. I think that I understand. svcs gets the name of the log file from > > the restarter/logfile property for the instance. In this case the > > restarter property group is created and populated by svc.startd. The > > restarter property group is a nonpersistent property group, however. > > Nonpersistent property groups are lost on reboot. > > > > Thus, I think that you will only find a restarter/logfile property for > > services that have been started since the last reboot. The corollary to > > this is that svcs will only print a logfile for these services. > > > > Is this consistent with your experience? > > > > tom Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
