Then I don't get something. I never really see any updated info when I install a new version so perhaps that's part of it. But I run mis as a
install a new version so perhaps that's part of it. But I run mis as a daemon so the only way I know to stop it is kill the task. If I do so I
install the new kernel). How is mis -d designed to be stopped now?
Ok, I'll do sudo kill PID on the mis PID. I guess I've gotten too use to the run away tasks that hog everything, which is why the -9 from another system via ssh or telnet (the real use and need of it).
(I may add a 'mis -shutdown' option one of these days to make it easily doable without grepping the PID first).
(I may add a 'mis -shutdown' option one of these days to make it easi doable without grepping the PID first).
is there a pid file created when mis is executed? generally in
/var/run... if so, one can do
sudo kill `cat /var/log/mis.pid`
|Location:||Beaverton, Oregon, USA|
|Nodes:||16 (0 / 16)|