Article View: comp.unix.sysv286
Article #88V/AT init - getty war
From: Ken Cornetet
Date: Tue, 22 Jan 1991 00:23
Date: Tue, 22 Jan 1991 00:23
21 lines
1313 bytes
1313 bytes
My V/AT system has developed a strange problem. Every once in a while, init (or at least I assume it is init) gets into a mode of sending signal 15 (SIGTERM) to getty. Getty then dies, gets respawned and about 10 seconds later, init sends another SIGTERM. This process continues until reboot (which may or may not stop it). I am assuming this is some sort of a race condition because it did not show up until moving from a 286 motherboard to a 386 board (I take that back, it did happen once, but a reboot cleared it up). Does anyone know of an explanation, fix, or any info at all ? I am baffled. I have considered getting a pd version of getty and adding code to ignore SIGTERM, but I highly suspect that init would send a SIGKILL after the SIGTERM did not do anything. BTW my V/AT is 2.4.0-L if that helps -- Ken Cornetet (812) 634-2824 | ken@coplex.uucp -or- Rt. 5 Box 184A, Jasper, IN 47546 | ...!uunet!coplex!ezelmo!kenc
Technical Details
Message-ID:
<188@ezelmo.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool2.mu.edu!uunet!coplex!ezelmo!kencShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool2.mu.edu!uunet!coplex!ezelmo!kenc From: kenc@ezelmo.UUCP (Ken Cornetet) Newsgroups: comp.unix.sysv286 Subject: V/AT init - getty war Message-ID: <188@ezelmo.UUCP> Date: 22 Jan 91 00:23:10 GMT Organization: Cornetet Consulting, Jasper, IN Lines: 21