Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!wuarchive!cs.utexas.edu!mailrus!cornell!ken
From: ken@gvax.cs.cornell.edu (Ken Birman)
Newsgroups: comp.sys.isis
Subject: Re: isis_input() question
Message-ID: <33420@cornell.UUCP>
Date: 21 Oct 89 01:54:39 GMT
References: <RICH.89Oct20140203@oxtrap.sendai.ann-arbor.mi.us>
Sender: nobody@cornell.UUCP
Reply-To: ken@gvax.cs.cornell.edu (Ken Birman)
Distribution: comp
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 12

In article <RICH.89Oct20140203@oxtrap.sendai.ann-arbor.mi.us> rich@oxtrap.UUCP writes:
>How do I turn a callback off?  ie, I've reached end of file or socket
>broke and I've closed the descriptor.  Sooner or later, that
>descriptor will be reallocated...

Most of the ISIS callbacks can be turned off by repeating the
original call (i.e. isis_input) and specifying a null routine.
The constant NULLROUTINE is predefined to make this easy:
	isis_input(fdes, NULLROUTINE, NULLARG);

An exception is that pg_monitor and pg_watch have an
explicit cancel call.