Grant,
Thanks for the pointer and the patch. I could see this turning into a
configuration option when (if?) I get time to finish up the latest
version into a "real" release.
It's interesting, though, to explore *why* this works. If I had to
guess, you probably run nzbperl as a daemon and feed it files via
filesystem queue?
In any case, this option really *shouldn't* cause nzbperl to do anything
special. It's already supposed to gracefully handle the case where the
remote side (server or socks proxy or whatever) closes the
connection...if the FIN packet never comes in, though, something much
more nefarious is going on. ;)
In the few cases that I've seen this kind of thing in the wild, it's
been caused by bad firewall/nat rules or a remote process dumping core.
-jason