"Batey, Everett II NAVSEA" writes:
> 
> Usually I try not to reboot when fixing ipfilter, ntp, nis, and others
> and the absence of the Console and Syslog info leave me having to search
> out a svcs or other option to see what died. 
> 
> I had repaired about a dozen (and sometimes do so on the fly)
> /etc/init.d scripts to tell what failed.  I generated forced syslog as
> well as echo to console.
> 
> Really would be nice to retrieve that ability .. Even if I have to do it
> for myself, manually per startup, restart, reload, stop.

A few things that you do get with SMF:

1. As James mentioned, svcs -x and -xv is meant to be one stop shopping to
   answer the "what's wrong with my system" question.  We've been 
   working to make error notifications in OpenSolaris directly locatable
   without needing to read syslog tea leaves (which can be challenging
   for admins new to Unix).  svcs -x and fmadm faulty follow that
   model, SMF and FMA form the basis of an architecture that will be able
   to do even better software fault diagnosis in the future.

2. Additionally, I've recently fixed a bug in Solaris Express (and it's being 
   backported to S10 soon) to ensure that transitions to maintenance 
   always cause a syslog message.
      http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6321540

   Based on another customer escalation, it's being backported to a 
   Solaris 10 patch.  I don't have a date when it'll be available, but you 
   could get more info through your support contract.

If you're looking for notification on any type of transition (not just 
maintenance), that's a project we're planning.  I'm hoping to have a 
draft project document published this month in this community.

> A separate issue:  "EXPORTING MESSAGES / SYSLOG without email cut  and
> paste."  
> 
> Here in Navy country we are prohibited from emailing from a Sun.  IT IS
> NOT part of EDS/NMCI where email is permitted.  
> IT WOULD be nice, once opening a ticket to have access to a small upload
> where we could add the log data to the OnLine Support file via Port 80
> or 443 since we can still access the web from our email denied Suns.

That's a bit off-topic for OpenSolaris (and the right folks to make 
such a change probably aren't subscribed here).  If my memory is 
correct, there's already an FTP area, but I don't know about any 
web-based drop location.  You'll probably get more effective responses 
through your support channel about this issue.  Sorry.

liane
-- 
Liane Praza, Solaris Kernel Development
liane.praza at sun.com - http://blogs.sun.com/lianep



Reply via email to