There is no reason to start up these VistA processes using some external script except for Taskman. Once Taskman starts up he can start up whatever background process you desire. Most, if not all, of these background processes already have VistA options to be run as scheduled tasks at startup from Taskman. Of course many of these options assume you have properly configured the corresponding files prior to trying to start up those background processes. The Broker, HL7, Mailman, and others can all be started by Taskman.
Stopping processes non-interactively is more of a problem as most of them do not have a silent way to stop the background processes. Taskman can be told to stop all processes when they finish. But this has always been problematic. Some processes never get terminated, perhaps because they were not started by Taskman directly. Then what does Taskman do (or a system shutdown do) if a process is running, say a report, still has several hours to go before running to completion? Yes VistA tasked jobs can be programmed to look for a stop running request so that they shutdown gracefully. The truth is that most Taskman jobs are not programmed to even look for these stop requests. ------------------------------------------------------- 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
