This one time, at band camp, dean gaudet said: > a couple times a month i find a freshclam which has been stuck on a read > from fd 4 for a few days... fd 4 is its network socket, and it seems to be > stuck in the middle of a tcp session, probably the other end has > disappeared. there really should be an alarm(900) or something in > freshclam so that it'll die off eventually.
Yes, I agree. The proper implementation should be to fork a child, and the child sets a timeout of something approximating the amount of time in between checks (so that you don't have two children trying to update the database simultaneously). Then an alarm could just kill of the stuck process. I will look into it. Thanks for the report, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
