lock(1) bug reported

[utzoo!decvax!harpo!npois!alice!sjb]

This was one of the two topics covered on lock in my note that I
sent from harpo.  The fix to the ^Z problem is simple -- there
is a line that reads:
	for (x = 1; x <= 16; x++)
(or something like that)
in lock.c that starts a loop that ignores signals.  To fix the
^Z problem, change the 16 to an 18 (or NSIG), and you will ignore
the signal that controls the ^Z feature.