<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Olly & Xapian Developers,<div><br></div><div>I've done some more investigation and I think I may have an explanation.</div><div><br></div><div>I was looking at the individual processes and noticed that the /bin/cat process status:</div><div><b><span class="Apple-style-span" style="font-weight: normal; "><b># cat /proc/<span class="Apple-style-span" style="font-weight: normal; "><b>8207</b></span>/status | grep SigIgn</b></span></b></div><div><b>SigIgn:</b><span class="Apple-tab-span" style="white-space:pre"><b> </b></span><b>0000000000000001 e.g. ignoring SIGHUP[1]</b></div><div><br></div><div>I looked at the process tree:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span> <u>PID</u></div><div><div><b> 8113 <u>8196</u> 8111 8108 ? -1 Sl 33 0:06 | | \_ Passenger ApplicationSpawner: /srv/www/www.oriontransfer.co.nz </b></div><div><b> 8196 <u>8207</u> 8111 8108 ? -1 S 33 0:00 | | | \_ /bin/cat</b></div></div><div><br></div><div>Then I checked the status of the parent process:</div><div><br></div><div><div><b># cat /proc/8196/status | grep SigIgn</b></div><div><b>SigIgn:</b><span class="Apple-tab-span" style="white-space:pre"><b> </b></span><b>0000000000000001</b></div></div><div><br></div><div>I can only assume that the <b>SigIgn</b> flag is being inherited by the process, and thus FlintLock <b>SIGKILL</b> is being ignored.</div><div><br></div><div>I would appreciate some feedback on this, if someone else can validate or review the issue.</div><div><br></div><div>I've forked the xapian tree on github. If I can make a change, how do I submit a patch?</div><div><br></div><div>Thanks,</div><div>Samuel</div><div><br></div><div>[1] man signal:</div><div><b> SIGHUP 1 Term Hangup detected on controlling terminal</b></div><div><b> or death of controlling process</b></div><div><br></div><div><div><div>On 8/04/2011, at 9:21 PM, Olly Betts wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Fri, Apr 08, 2011 at 05:33:02PM +1200, Samuel Williams wrote:<br><blockquote type="cite">I noticed that it was sent SIGHUP, but it didn't quit for some reason.<br></blockquote><blockquote type="cite">Maybe you need to change this to SIGKILL? I was wondering if you knew<br></blockquote><blockquote type="cite">what "= ? ERESTARTSYS (To be restarted)" meant?<br></blockquote><br>Currently drowning in GSoC applications (as the deadline looms), but<br>using SIGKILL is probably a sane change and could help. Can you try<br>that and see how you do?<br><br>I'll try to make some sense of the logs later.<br><br>Cheers,<br> Olly<br></div></blockquote></div><br></div></body></html>