If you don't know what NSD is you should probably go read this,
Once upon a time, NSD had a command line option -kill. This is the description of that option from NSD's help.
Runs NSD in a special mode that kills all Notes/Domino processes in the current "partition" (i.e. all processes that are accessing Notes shared memory and that are running from the same location as NSD
Sounds pretty ominous huh? We'll it was. It is also slow and dived deep into the OS to do the dirty work of getting Notes killed. At some point in NSD's evolution, a lighter implementation of -kill was created. This new approach leveraged the NotesInit and NotesTerm API functionality that all processes that worked with Notes invoked. The NSD -kill option was changed to kill processes listed in the pid.nbf. "Wait what is the pid.nbf you ask?" "Go read this", I reply. However the old sledgehammer functionality was kept around and hidden under the command line option -k.
"That's nice, but so what?" you may be asking yourself. That's a pretty good question. For 99% of the time (a percentage I made up btw) -kill should be perfectly sufficient for killing Notes processes. However ever so often a rogue application somehow manages to get into a state that either doesn't update the pid.nbf properly or fails to be terminated even thought it's listed . In those cases NSD -k is a possible solution.
Jeff Mitchell | 14 October 2010 02:18:51 PM ET | Littleton, MA | Comments (3)