Every time I halt VistA and exit, I run my mupip rundown * and I am happy when it works. When I do this, if there are processes running that I didn't realize I left running, it tells me all is not well in Mudville. I am regularly powering down my machine to cart it to work, so I guess maybe in my situation, it is a good idea .
However, when I do find there is a process running and I do my ps aux | grep mumps and I terminate those processes, I always pray because I assume I am stopping something inappropriately and I am so happy when the next attempt at rundown is OK. Is there a way that I could find out what is going on inside that resulted in my leaving with a process running - i.e., how can I find out what that process was? The ps aux | grep mumps always yields a mumps -direct *, On Tuesday 08 March 2005 07:48 am, Bhaskar, KS wrote: > With GT.M, the first process to open a database file sets up the control > structures to manage it, and the last one out turns out the lights and > cleans up. Mupip rundown is not required for normal operation. > > Mupip rundown was designed so that in the event a PC was powered down with > processes accessing the database, and there is no database damage, then a > rundown cleans up certain fields in the database file header. It is not > needed when journaling is used. > > Another use for mupip rundown is to see whether any processes are accessing > a database before shutting down a computer system. Another way to do this > is to execute "ps -ef | grep mumps". > > Note that it is not a good idea to shut down VistA by issuing a mupip stop > to all mumps processes. If, for example, the processes are Taskman > processes. there is information in the database about their process ids, > etc. It is better to shut them down cleanly from inside VistA, and they > will clean up the database before shutting down. > > If you find yourself needing to rundown databases routinely, let's review > what you are doing in order to find out what you should do differently. > Using a medical analogy, if you find a patient using bronchdilators or > nitroglycerine frequently, you would try to find and treat an underlying > condition, even if what they are doing gives them relief. > > -- Bhaskar > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of Kevin > Toppenberg Sent: Tue 3/8/2005 6:52 AM > To: hardhats-members@lists.sourceforge.net > Cc: > Subject: RE: [Hardhats-members] set HL COMMUNICATION SERVER PARAMETERS > fails Bhaskar, > > Superstition perhaps? > > Actually, it seems that when the database has not been > rundown properly, that attempting to access globals is > unsuccesful. Thus if one has code that depends on > this variable, it will fail. So it seems that I have > had programs that just drop out, or act funny--only to > start working properly when the database was rundown. > > Kevin -- Nancy Anthracite ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
