in reply to Re: Mysterious bad file descriptor after fork
in thread Mysterious bad file descriptor after fork

"Certain circumstances" refers to calling DBConnect_no_ok instead of DBConnect_ok before server start. I edited my post to better reflect that.

I will look into the return value of accept().

Thanks for the hint, will report back.

cat /dev/world | perl -e "(/(^.*? \?) 42\!/) && (print $1))"
errors->(c)
  • Comment on Re^2: Mysterious bad file descriptor after fork

Replies are listed 'Best First'.
Re^3: Mysterious bad file descriptor after fork
by gnork (Scribe) on Jul 10, 2007 at 19:48 UTC
    The return value of accept() is now checked and properly treated. The error persists, so it was not the root of the evil.

    Best rgds
    gnork

    cat /dev/world | perl -e "(/(^.*? \?) 42\!/) && (print $1))"
    errors->(c)
[reply]

In Section Seekers of Perl Wisdom