*BSD News Article 7936


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!rpi!news.ans.net!cmcl2!prism.poly.edu!kapela
From: kapela@prism.poly.edu (Theodore S. Kapela)
Subject: Broken patched init (Was Re: 386BSD or LINUX?)
Message-ID: <1992Nov20.141026.5652@prism.poly.edu>
Organization: Polytechnic University, New York
References: <1992Nov4.052106.29266@menudo.uh.edu> <1992Nov4.131541.15661@prism.poly.edu> <1992Nov17.045443.20013@cs.chalmers.se>
Date: Fri, 20 Nov 92 14:10:26 GMT
Lines: 21

In article <1992Nov17.045443.20013@cs.chalmers.se> augustss@cs.chalmers.se (Lennart Augustsson) writes:
>In article <1992Nov4.131541.15661@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
>>the bad buffers back to disk, writing over the fixes made by fsck (using the
>>raw partition).  I haven't really had a chance to check this out yet.
>Add the line
>	trap : 15
>at the start of /etc/rc to fix the problem.  reboot send SIGTERM to all
>processes and it is not ignored by default by the shell.  (One one the 58
>patches caused this behaviour.)

I came across a note about one of the patches in the patchkit, which also fixed
my problem.  There is a missing semicolon as part of the 
"send SIGTERM, sleep, send SIGKILL" patch to init.  Replacing the 
semicolon fixed this problem. (Near line 234 in init.c, I beleive).


-- 
...............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University