Actually, it's not quite that slick. Maybe Cameron has something else in mind, but what KIDS does do is allow you to mark options "out of order" at the level of the VistA Kernel, so that options exercising the code cannot be invoked. You can also place Taskman in a wait state so that it remains "alive" but it doesn't start new tasks.
One thing I learned that hard way is that the error generated when a routine being called (at least under DSM, or was it Cache?) cannot be caught (rather like SIGKILL under Unix). It would be nice to have something like SIGTERM (which causes process termination by default, but which can be caught). That way, a daemon process could be set up to die gracefully in situations like this. --- "K.S. Bhaskar" <[EMAIL PROTECTED]> wrote: > Cool! I didn't know KIDS did all that. So what we now need is to > establish the set of signals that tell a ship that it needs to go > into > dry dock for an oil change (or whatever ships do in floating dry > docks > when on maneuvers - excuse my skimpy nautical knowledge). > > What does KIDS do if a process is in an area that it wants to change? > > -- Bhaskar > > On Mon, 2005-08-29 at 15:54 -0500, Cameron Schlehuber wrote: > > All patches and version updates to VistA in VA are handled via KIDS > > (or at > > least they're supposed to!) One of the capabilities KIDS offers is > to > > lock > > out users of selected options related to the code being changed. > > Other > > users then can continue their merry way during what in some cases > may > > be > > lengthy installation processes. Rather than VistA being like a car > > (a > > system), it's more like a fleet (a system of systems), where we > even > > have > > the equivalent of floating dry-docks to do repairs while engaged in > > active > > maneuvers. > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > & QA > Security * Process Improvement & Measurement * > http://www.sqe.com/bsce5sf > _______________________________________________ > Hardhats-members mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hardhats-members > === Gregory Woodhouse <[EMAIL PROTECTED]> "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- Antoine de Saint-Exupery ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
