[rancid] Re: FreeBSD 7.0 + Expect 5.43.0 -- Do I need to patch expect?
ecables at gmail.com
Fri Nov 14 23:47:39 UTC 2008
Is this something I can do when I discover the process is hung, or something
that has to be prepared before it hangs? For example, if I come back into
the office on Monday to find RANCID hung, is there anything I can do to
collect forensics as to what caused it to hang?
On Fri, Nov 14, 2008 at 3:26 PM, john heasley <heas at shrubbery.net> wrote:
> I have no idea what the problem is. I expect it'l require a mix of
> ktrace, gcore/gdb, and tcpdump to figure out what is causing tcl/expect
> to hang.
> Fri, Nov 14, 2008 at 11:25:29AM -0800, Eric Cables:
> > Are there any debugging options available to try and isolate the root
> > 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. :-)
> > --
> > Eric Cables
> > On Fri, Nov 14, 2008 at 11:18 AM, john heasley <heas at shrubbery.net>
> > > Fri, Nov 14, 2008 at 10:33:16AM -0800, Eric Cables:
> > > > I've been running into this problem quite frequently, about once a
> > > or
> > > > so rancid will hang for no apparent reason, and until I kill the
> > > it
> > > > will remain hung. I've read in the archives that Linux & Solaris
> have a
> > > > problem with expect that requires a patch, but does this also include
> > > > FreeBSD?
> > >
> > > Yes, some combinations of recent tcl / expect seem to have trouble on
> > > I'm not sure why, but the expect was pulled from distribution site for
> > > defects. the problem is that rolling back (via ports) seems to
> > > an old problem which itself had been correct in ports by rolling back,
> > > IIRC.
> > >
> > > I do not use freebsd and haven't had time to debug the problem. ports
> > > imho, too anxious to move forward with new tcl/expect versions and both
> > > too delicate for that.
> > >
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rancid-discuss