Article View: comp.bugs.sys5
Article #1122Re: What's a system call ( Was: 'what' doesn't use perror...)
From: Leslie Mikesell
Date: Thu, 18 May 1989 18:57
Date: Thu, 18 May 1989 18:57
19 lines
1275 bytes
1275 bytes
In article <225@jetson.UPMA.MD.US> john@jetson.UPMA.MD.US (John Owens) writes: >> ] alarm(n); >> ] pause(); >> ](the guts of sleep) and what happens if the process doesn't run for n >If the process doesn't run for 'n' seconds *after* the alarm() is >posted and *before* pause() is called, it'll get a SIGALRM (which is, >I think, set to SIG_IGN at that point), not do anything, then call >pause() too late.... Hmmm... Could this perhaps be why uugetty (SysVr3.1 on a 3b2) sometimes leaves a port dead and killing it lets a new one start properly. Maybe when it sees a uucp lockfile it tries to sleep awhile and check again. An idle uugetty would be a likely thing to be swapped out and not run during the time the time the signal is delivered. Les Mikesell
Technical Details
Message-ID:
<8484@chinet.chi.il.us>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!chinet!lesReferences:
<3759@sugar.hackercorp.com] <10156@smoke.BRL.MIL] <1232@netcom.UUCP> <225@jetson.UPMA.MD.US>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!chinet!les From: les@chinet.chi.il.us (Leslie Mikesell) Newsgroups: comp.bugs.sys5 Subject: Re: What's a system call ( Was: 'what' doesn't use perror...) Message-ID: <8484@chinet.chi.il.us> Date: 18 May 89 18:57:36 GMT References: <3759@sugar.hackercorp.com] <10156@smoke.BRL.MIL] <1232@netcom.UUCP> <225@jetson.UPMA.MD.US> Reply-To: les@chinet.chi.il.us (Leslie Mikesell) Organization: Chinet - Public Access Unix Lines: 19