More on the fast timer driver

utzoo!decvax!ucbvax!ihnss!vax135!cornell!dean utzoo!decvax!ucbvax!ihnss!vax135!cornell!dean
Tue Feb 9 14:10:16 AEST 1982


I should probably make a few further comments about the fast timer
driver.  First, the extended signal stuff in 4BSD Berkeley UNIX is
essential to the reliable operation of the fast timer.  You should
use a sequence of the form (see sigset(3) for the details):

	sigset(your_signal, action);
	sighold(your_signal);
	ioctl( fd, FTIOCSET, &request );
	sigpause(your_signal);

where you have previously set up the timer buffer 'request' with
your_signal and successfully opened a fast timer as fd.  This
sequence guarantees that the signal won't pop through before you
get to execute the pause.

I specified in the net.sources distribution that the timer driver
should go in as device 25.  This would make it the first local device.
Obviously, if you already have other local devices, you should just
add it on to the end of your previous list.  The device number is not
critical.
			Dean Krafft (decvax!cornell!dean)



More information about the Comp.unix.wizards mailing list