Date: Mon, 26 Jan 1998 01:05:03 -0800 (PST) From: Alex <garbanzo@hooked.net> To: current <current@FreeBSD.ORG> Subject: inetd patch/idea Message-ID: <Pine.BSF.3.96.980126004746.437A-101000@zippy.dyn.ml.org>
index | next in thread | raw e-mail
[-- Attachment #1 --]
I've been messing around with a little program that provides a front end
for inetd.conf, and in doing so, I noticed two things:
1.) inetd.conf wasn't re-read on reception of a SIGHUP
2.) When a SIGTERM is recieved, inetd died a horrible death and didn't
clean up its pid file.
A little investigation proved that all the code for the re-reading of
inet.conf was actually there, however, it was among the list of signals to
be blocked. I haven't seen any ill effects of removing it from the list,
however if there are any, it's simple enough to generate two lists of
signals to be blocked.
El hombre mas brillante dijo una vez "Cuidado hay NT". (it's a nerd thing)
- alex
[-- Attachment #2 --]
LP4inetd.diff Uo6eKvYei-,C7CKF"t I {wG
CJt9
~
'0'7(Z[>3z9}po!jGG \!D]-@g4KaJb
#x*^oD.Acɼ1IRIw`7!:sPkk墼aX'Thk 1DU`ex9(Wg"c6w+pS\."|$aI1-JBz58Iմ%jk Qݒ[D
| eCxQ5MC|-P9cNbmQcl֛%ݶ(}"{L%uBg|kwO!jߥ"C:ϫSNƃq*NxFͷ8pq?d*~DAejPqr~;{'+Zq{=Y_^Am((cX49][`۳x=Z57]k}4Baaa oC_?R˔\92BTOh
eD.-:iM/>IȊ%;Spg<Cq"{!A ]r琎 UK@'@ O@껂P"C
xB#uS(S>M=ڎ*sE'ak2 ʥ4ZU4dT[
i6ǻ8NNcC7OcTh}G̨Iy֒Cĭkk7iټa}tf #^gHLUTV*&nǝwgC
߿9/Y67N7La-_Tٶ
]2i)ڇ>k#<Xi0Y& 4G?pY^=#Elfc-ِk̯;VF~ lGQV'1ٍ
/LFv{qA(h:}/.
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980126004746.437A-101000>
