Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mit-eddie!wuarchive!uunet!mcsun!ukc!edcastle!aiai!richard
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.programmer
Subject: Re: Problems with signal handler
Message-ID: <3997@skye.ed.ac.uk>
Date: 24 Jan 91 14:19:21 GMT
References: <1991Jan22.151906.9695@daimi.aau.dk> <1991Jan22.230448.28521@NCoast.ORG> <1991Jan23.183422.24871@robobar.co.uk>
Reply-To: richard@aiai.UUCP (Richard Tobin)
Organization: AIAI, University of Edinburgh, Scotland
Lines: 22

In article <1991Jan23.183422.24871@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
>To pick a nit, SCO Xenix V.2.3 has sighold()/sigrelse().  Question:
>where do these come from ? BSD 4.1 ?

Yup.  They were in the "jobs library" which went away in 4.2.

From jobs(3J):

 The facilities described here are used to support the job control
 implemented in csh(1) ... Because these facilities are not standard
 in UNIX and because the signal mechanisms are also slightly different,
 the associated routines are not in the standard C library ...

In 4.2, sighold() and sigrelse() were replaced with sigblock() and
sigsetmask(), and the job control facilities were integrated into
the standard library.

-- Richard
-- 
Richard Tobin,                       JANET: R.Tobin@uk.ac.ed             
AI Applications Institute,           ARPA:  R.Tobin%uk.ac.ed@nsfnet-relay.ac.uk
Edinburgh University.                UUCP:  ...!ukc!ed.ac.uk!R.Tobin