Re: beacon 0.9.58 dies after a while - broken pipe?
This may or may not be relevant, but I got this this AM
Use of uninitialized value in scalar chop at ./beacon line 1596.
HOST_LOOKUP delete failed 0x427c401d, UNKN,
I am running beacon-0.9.58-2. Line 1596 is
chop $reverse_tld; # Whack trailing "."
The beacon did not die and continues to run, seemingly OK.
Marshall
On Thu, 29 Jul 2004 10:04:42 -0500
John Kristoff <jtk@northwestern.edu> wrote:
> On Sat, 24 Jul 2004 17:34:56 -0500
> Mitch Kutzko <mitch@ncsa.uiuc.edu> wrote:
>
> > Hi -- Has anybody else seen this behavior? Is it reproducible? Any details?
>
> I also have seen this, but haven't been able to pinpoint it. I was
> running it as follows to see if I could capture anything in a log:
>
> ${BEACON} >> ${LOGFILE} 2>&1 < /dev/null & > /dev/null
>
> but so far nothing, it just dies without any messages. There doesn't
> seem to be any particular pattern, but it also doesn't seem to take
> long for it to die on my system. I'm going to enable $DEBUG and see
> if that tells me anything.
>
> FYI... $debugfile in the beacon Perl script doesn't seem to ever be
> used.
>
> John
>