Clay Baenziger wrote:
> Hi all,
> I see this as a blocker bug, for as I see it:
> This seems pretty severe that once an A/I install server is rebooted the
> admin must either create a new service or understand how to manually start
> the Apache image server (on top of running installadm start <service> for
> each service on the machine).
> However, this late in the release should we simply release note
> how to start the Apache server (and for good measure that one must
> installadm start <service> for each service)?
> Thank you,
> Clay
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
Clay,
I agree that it is a critical bug that should be fixed soon. The fix
is not straight forward to start all the install services that were
running before the reboot along with the apache web server that serves
the clients. There are some bugs in installadm that prevents us to get a
reliable list of services that were running before the reboot. While I
am working on a fix for this problem, I don't to destabilize the
November release with this fix. This problem is similar to 3975, (the
service svc:/system/filesystem/local:default will not start after reboot)
We should document this bug in the release notes (along with 3975)
and try to fix asap after November release.
Thanks,
Sundar
