I am actually more interested in the opposite case, where we don't have the database running, but want it to startup on the next reboot.
This is a common case where we disable the startup scripts for our applications that are managed by another group, prior to starting system maintenance. We are then free to perform maintenance, reboot as needed, and fully test. We then reenable the startup scripts before the last reboot before handing the systems back to the users. (app admins). (This has the added benefit of providing for a cross system/application/milestone test of the full boot process.) Cheers, Brian P.S. - I hope that was clear... let me know if you need clarification. On 10/30/07, Stephen Hahn <sch at sun.com> wrote: > * Darren Reed <Darren.Reed at Sun.COM> [2007-10-30 19:59]: > > Stephen Hahn wrote: > > > > >* Darren Reed <Darren.Reed at Sun.COM> [2007-10-30 18:55]: > > > > > > > > >>Stephen Hahn wrote: > > >> > > >> > > >> > > >>>... > > >>> > > >>>But I think the main point is that many of the "this application > > >>>shouldn't run until next boot" are really errors in sequencing, and > > >>>aren't in fact sensitive to the OS instance lifetime. (I suppose my > > >>>own reboot sensitivity was triggered by the E10K reboot latency (then > > >>>due to SCSI), and hasn't eased much, given the large memory reboot > > >>>latencies today...) > > >>> > > >>> > > >>It's not just "shouldn't run until next boot" but "after the next > > >>boot, it should not run." Although the latter is more easily > > >>worked around by doing a "svcadm disable .." before you > > >>reboot, it changes the boundary of availability from the reboot > > >>itself to before the reboot. > > >> > > >> > > > > > > Could you give me an example of when I would want to run something > > > until the OS reboots, and then not run it? (The only example I can > > > think of are the graphical login services, but there might be > > > something more interesting.) Generally, I don't worry about allowing > > > this case as much as the other one. > > > > If I'm migrating a database from one system to another and in > > doing so I need to disconnect some number of disks, after the > > disks are removed (while power is off) I'll reboot the box and > > then the database should be disabled. > > svcadm disable database > shutdown > > ? > > - Stephen > > -- > sch at sun.com http://blogs.sun.com/sch/ > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org > -- - Brian Gupta http://opensolaris.org/os/project/nycosug/
