Has anyone else out there noticed this? When we manually start an NSR
group on the NSR server through the GUI then select 'stop' on the
group after a few seconds, all those nodes that have already called
'savefs' shut down!
This is a little disturbing. I have a suspicion that nsrexecd may be
getting its parent process id rather than its child process id and
sending an interrupt signal to the parent (ie pid 1). Then again
perhaps not.
Anyone seen this??
Needless to say "Don't try this one at home kids".
Keith McCabe
Banque Paribas Capital Markets
London W1
Received on Mon Apr 28 1997 - 20:01:40 NZST