> One thing I am seeing about the property restarter/logfile is some use > alt_logfile. For instance > > # svcs -l svc:/system/identity:node > fmri svc:/system/identity:node > name system identity (nodename) > enabled true > state online > next_state none > state_time Sun Oct 08 10:21:35 2006 > alt_logfile /etc/svc/volatile/system-identity:node.log > restarter svc:/system/svc/restarter:default > dependency require_any/none svc:/network/loopback (online) > dependency optional_all/none svc:/network/physical (online) > > but it also has a log file in /var/svc/log/system-identity\:node.log > so I am not sure which one to use here. Can you provide any info on > this?
For early service instances in split-root scenarios, where /var/svc/log might not yet be writeable, svc.startd will place the per-instance logs in /etc/svc/volatile. This location is called the "alternate logfile" because, if that service instance is restarted, the logfile will appear in /var. So, if you have a service without restarter/logfile, check for restarter/alt_logfile. (If restarter/logfile is present, it is always the authoritative log.) - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems stephen.hahn at sun.com http://blogs.sun.com/sch/
