![]() | |
#11
| |||
| |||
|
|
I would suggest that it is NEVER a good idea to simply stop the D3 service. That will NOT force memory to flush or processes to log off properly. If at all possible, it will always be better if you get a port logged on to do a proper "shutdown". Even something as simple as: for i = 1 to system(18) execute "logoff ":i:" (z" next i data "Y" chain "shutdown" This will at least force the ports to all logoff, giving up their workspace to overflow. Some steps actually writing to filespace will not allow themselves to be broken, so this will keep you from creating GFEs automatically. Using the STOP to stop the service simply kills D3 and if it's in the middle of pulling up a group or updating the overflow table, you're just out of luck. "Brian Bond" <brian (AT) XYZXYZXYZXYZbonanzapress (DOT) com> wrote in message news:11rm2hq4cndca31 (AT) corp (DOT) supernews.com... In conjunction with the UPS monitoring software that comes with Windows 2000, I have set up a script that is executed when the power has been off for three minutes. The script consists of "net stop D3vme", and then blat.exe to send me email notification (all comm gear is on the UPS). After the script is run, the UPS software then shuts down the computer. I understand that the D3Tray program can also be used to automate this procedure, but it appears that the console must be logged on in order for that to work, and our console is typically not left logged on. I don't know if my setup qualifies as a "best practice", but I certainly do not want it to be a "worst practice". Is there any else or anything different that I should be doing? thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |