OpenSolaris

Printable Version Enter a New Search
Bug ID 6765907
Synopsis services can be started without a running snapshot
State 10-Fix Delivered (Fix available in build)
Category:Subcategory utility:smf
Keywords smf
Responsible Engineer Sean Wilcox
Reported Against snv_100
Duplicate Of
Introduced In
Commit to Fix snv_106
Fixed In snv_106
Release Fixed solaris_nevada(snv_106)
Related Bugs 6765798 , 6790135 , 6794357
Submit Date 31-October-2008
Last Update Date 16-January-2009
Description 
[dep, 30Oct2008]

  Some people have noticed coreadm dumping core on preliminary build
  100 OpenSolaris live CDs.  Though the immediate cause of the problem
  is 6765798, the reason coreadm is failing there is because it needs
  to be able to read its configuration but the running snapshot for
  coreadm hasn't been created yet.  Even if the aforementioned bug is
  fixed, coreadm will still fail because it won't be able to read its
  configuration.

  This is a general problem: running services are supposed to obtain
  their configurtion from their running snapshot.  SMF is setting
  services up for failure when it starts them without first ensuring a
  running snapshot exists.
Work Around 
N/A
Comments 
bustos 2008-10-30

This is an RFE because the system has always worked this way.  Clients
should never assume the running snapshot exists.  If it doesn't, they
should fall back to the current properties.  See, for example,
svcprop.

Creating the running snapshot on import is a clever solution.  The
alternative suggested (an in-core running snapshot) will be done in
the course of the enhanced SMF profiles project.