From owner-freebsd-ports Mon May 8 13:40: 4 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 4A88D37B74F for ; Mon, 8 May 2000 13:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA06637; Mon, 8 May 2000 13:40:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 8 May 2000 13:40:01 -0700 (PDT) Message-Id: <200005082040.NAA06637@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Kris Kennaway Subject: Re: ports/18446: fetchmail doesn't close its sockets properly Reply-To: Kris Kennaway Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/18446; it has been noted by GNATS. From: Kris Kennaway To: mavetju@chello.nl Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/18446: fetchmail doesn't close its sockets properly Date: Mon, 8 May 2000 13:32:14 -0700 (PDT) On Mon, 8 May 2000 mavetju@chello.nl wrote: > If you run fetchmail in daemon-mode, it will not close its > TCP sessions properly. With lsof you will see more and more > lines with this: This is something which should be taken up with the fetchmail developers. FreeBSD doesn't typically do bug-fixing of ports unless a patch is submitted, and maintainers are only expected to work with what's given to them by the developers and get it running on FreeBSD. Good luck! Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message