You discovered that the network/ipmp:default is not starting on boot. You listed the service and discovered the name of the log file. You now want to examine the log file entry created at boot. In…

Question

Options

• A/lib/svc/volatile
• B/etc/svc/volatile
• C/var/svc/volatile
• D/var/run
• E/var/tmp
• F/var/svc/log
• G/lib/svc/log

• B
  81% (30)
• C
  3% (1)
• D
  11% (4)
• G
  5% (2)

Explanation

On Solaris, SMF (Service Management Facility) log files are accessible in two places because of a two-phase boot process: /etc/svc/volatile (option B) is a tmpfs filesystem mounted very early in boot - before /var is available - so startup log entries are written there first; /var/svc/log (option F) is the standard persistent location where SMF log files live once the full filesystem is mounted, and the boot-time log is accessible here as well. The other volatile-named paths are wrong because the actual volatile tmpfs is always mounted under /etc/svc/volatile, not /lib/svc/volatile (A) or /var/svc/volatile (C). /var/run (D) holds PID files and runtime socket data, not SMF logs; /var/tmp (E) is for general temporary files; and /lib/svc/log (G) doesn't exist - /lib/svc/ holds SMF method scripts and binaries, not logs.

Memory tip: Think of the two "svc" paths - one under /etc (early/volatile, before /var mounts) and one under /var (persistent, after full boot). If you remember that /var isn't available at the very start of boot, it's clear why /etc/svc/volatile must exist as the early-boot fallback.

No community discussion yet for this question.