Are there any debugging options available to try and isolate the root cause of the problem? I could probably write up a shell script that finds hung processes and kills them, but that's certainly not the best option. :-)<br clear="all">
<br>--<br>Eric Cables<br>
<br><br><div class="gmail_quote">On Fri, Nov 14, 2008 at 11:18 AM, john heasley <span dir="ltr"><<a href="mailto:heas@shrubbery.net">heas@shrubbery.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Fri, Nov 14, 2008 at 10:33:16AM -0800, Eric Cables:<br>
<div><div></div><div class="Wj3C7c">> I've been running into this problem quite frequently, about once a week or<br>
> so rancid will hang for no apparent reason, and until I kill the process it<br>
> will remain hung. I've read in the archives that Linux & Solaris have a<br>
> problem with expect that requires a patch, but does this also include<br>
> FreeBSD?<br>
<br>
</div></div>Yes, some combinations of recent tcl / expect seem to have trouble on fbsd.<br>
I'm not sure why, but the expect was pulled from distribution site for<br>
defects. the problem is that rolling back (via ports) seems to resurrect<br>
an old problem which itself had been correct in ports by rolling back, IIRC.<br>
<br>
I do not use freebsd and haven't had time to debug the problem. ports is,<br>
imho, too anxious to move forward with new tcl/expect versions and both are<br>
too delicate for that.<br>
</blockquote></div><br>