Quoth Peter van Gemert on Tue, Sep 25, 2007 at 02:17:31AM -0700:
> #### Change manifest file with new value
> # vi pvg.xml
> * Change timeout value for start method to 480
>
>
> #### Try to import the new manifest
> # svccfg import pvg.xml
> svccfg: Conflict upgrading svc:/site/pvg (property "start/timeout_seconds"
> has different values).
> # svcprop -p start/timeout_seconds pvg
> 240
>
>
> #### Reset value of timeout_seconds to the value of the last successfull
> import
> # svccfg
> svc:> select pvg
> svc:/site/pvg> editprop
> * Change timeout value for start method back to 120
> # svcadm refresh pvg
> # svcprop -p start/timeout_seconds pvg
> 120
This is the problem. From SCF's perspective, the last import was
successful, so it thinks that the developer wants the value to be 480.
It considers 120 to be a customization.
You should be able to see what SCF thinks the value at the last
successful import was with
svcprop -s last-import -p start/timeout_seconds pvg
I believe "last-import" isn't stable, though. And I'm planning on
removing it in the enhanced SMF profiles project.
David
