I think that building utilities around expect is adding unecessary complexity where you could just as easily (or more easily) simplify everything with a solution at a different level. A much better solution, if simple command line scripting isn't sufficient, would be to fix the utilities in MUMPS and disentangle such system management utilities once and for all from the roll-and-scroll interactive dialog - if it isn't already done.
Actually, in looking at STOP^ZTMKU (http://vista.vmth.ucdavis.edu/rtn/ZTMKU.html#STOP), that appears to be the only one of the entry points RUN, WAIT, UPDATE, and STOP that is interactive. The TaskMan shutdown is actually done with the non-interactive calls to GROUP("SMAN(NODE)") and GROUP("SSUB(NODE)"). Gregory wrote: >Nancy's suggestion (using expect) is probably worth exploring. > >The "mandatory" user interactions have been a perennial source of >frustration to me, too. >=== >Gregory Woodhouse >[EMAIL PROTECTED] > >"Nothing is as powerful than an idea >whose time has come." >-- Victor Hugo > > >On Aug 30, 2005, at 5:28 PM, César Yáñez Fernández wrote: > >> >> and now, I want to stop the TASKMAN without confirmation, in order to >> stop it, I type: >> GTM> D STOP^ZTMKU >> Are you sure you want to stop TaskMan? NO// >> (...) --------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) ------------------------------------------------------- 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 Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
