James Carlson wrote:
> Kyle McDonald writes:
>
>> James Carlson wrote:
>>
>>> Did you perhaps forget the 'refresh'? If so, I'll close out this bug.
>>>
>>>
>>>
>> Nope. I rebooted. Doesn't 'reboot' imply a 'refresh' ;) ??
>>
>
> No, it does not. You must explicitly do "svcadm refresh" if you want
> the altered parameters (set in the service) to apply to the existing
> service _instance_.
>
> As I was suggesting, please try a "refresh", and if that works, I'll
> close out the bug.
>
> (Perhaps there's a separate complaint here about SMF's design and the
> need for "refresh", but that looks out of scope for the bug filed.)
>
Ok so the refresh did work.
Odd, because in earlier builds the Terminal type change took effect on
reboot, but the label one didn't.
When I saw both changes missing this time I finally got around to filing
a bug.
So as I undertssand it now, there is some 'middle' location where the
settings are cached, and service startup reads the setting from there,
and not directly out of SMF? I knew about 'refresh' and thought it was
great for triggering running processes to reread their config, but as
rebooting (and 'restart') involve the service starting up from scratch
it was my understanding that that would include rereading the config.
I just re-read the man page, and even after that it's not clear to me
that 'refresh' is needed even when your're planning on rebooting. Unless
I'm missing something it basically described exactly what I said above.
Thanks,
-Kyle
