Thanks to all for svcadm restart <fmri>. This works great in the intended case where my service is already enabled, and the reboot needed to fully enable my service has already occurred.
This appears to be a no-op when my service was disabled. Is that the expected behavior? But this is a disaster in the edge case where my service has been enabled but the needed reboot has not been done: the service goes into maintenance because the start method goes too fast. This is not good. -- Jon
