>(Apache, MySQL, PostgreSQL, Postfix, Dovecot, Cyrus saslauthd, BIND, procmail, spamassassin, ClamAV, Perl and several modules, bash, awstats, modern Python and

>(Apache, MySQL, PostgreSQL, Postfix, Dovecot, Cyrus saslauthd, BIND, procmail, spamassassin, ClamAV, Perl and several modules, bash, awstats, modern Python and Ruby versions, and more that isn't coming to mind right now). Outside of Postgres AND MySQL on the same box... your requirements are actually pretty standard, and something I always deploy. I guess I'll leave it to others to comment - but that's basically my standard install, so I'm at a loss. I've never had it break, thought perhaps you had some odd corner-case package that wasn't properly being vetted out. Unfortunately we can't rewind time - I'd strongly suggest you post the bugs on the bug tracker in the future, because your experience is definitely not something I'd consider normal. >We're talking about a post in the DragonflyBSD list that discusses this very problem, the exact thing I'm belly aching about, is a thing that is acknowledged as a longstanding issue in ports by the developers who have made some changes to try to address the problem. Why are we arguing about whether it happens? Why are we arguing about whether it happens? Because you didn't report it. When I asked for specifics, you should've provided a link to the FreeBSD bug tracker where you reported the issue. Instead, we're talking about it on a social media site 7 years after the fact, with vague details about the packages that caused the issue. I literally don't have a horse in this race (I don't contribute to FreeBSD, I don't rely on it for my livelihood, I'm literally just a longtime luser) - but it honestly feels like you're attacking the project with unsubstantiated claims.