Danek Duvall wrote:
[..]
(2) Create a new SMF service that runs late in boot and also only once
on boot after upgrade to perform the PVID update. Please share any pointers
to existing SMF services that are similar and run just once.
This might work, but I don't know much about services disabling themselves.
I would presume it's safe to run "svcadm disable $SMF_FMRI" from within the
script, but folks on greenline-discuss would know better.
Okay
The question I see with this is whether this will ever need to be run
again. You have to keep delivering the service as long as you care about
transitioning people across this flag day (just like you would have to
carry the code in your postinstall script or upgrade script for that long),
but if you never have to run it again, then it can stay disabled and not
worried about until it's time for the service to be removed.
It doesn't need to run again, it is a one-time check and update.
[..]
But a service that runs exactly once in the lifetime of the system (unless
manually told otherwise) seems like it should work.
I am just wondering if this approach is used by other projects as well
to handle such updates won't we
end up with many of these services that run once and then remain
disabled on the system. I don't know
if it is a bad thing, maybe if they could also be deleted soon after
running and suitably logged so that they
don't just remain disabled.
My only other comment (and this is more in your domain that ours) is that
it sounds like this needs to be done earlier in boot -- won't network
connections already be established by the time this service runs, and won't
that make changing this configuration problematic?
It just needs to be run on upgrade and prints warning if there were any
links configured with VLAN 1.
So there are no boot order dependencies with other network services.
Rishi
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
