On Mon, Oct 21, 2013 at 03:41:38PM +0200, Eric Faurot wrote: > On Mon, Oct 21, 2013 at 02:31:49PM +0200, Jason A. Donenfeld wrote: > > > > Hi, > > I am now on bad terms and have a bit of a tarnished reputation with > > family, friends, and importantly, with clients. OpenSMTPD leaks. I > > don't know exactly where or how, but it does. I've been running it on a > > system with 256megs of ram, and seemingly randomly, it will eat up all > > the ram and then OOM. I've now put it on a system with a gig and a half > > of memory and written some auto restarter scripts. But this shouldn't > > be required. A gig and a half and fancy restarter scripts for an MTA? > > C'mon. I'm not sure how I should even go about debugging this to be > > constructive, as it's running on a mission critical production server. > > So, can we plug these? How can we plug these? What do we do? This > > problem is serious and lots of people are furious at me, and I can't > > just keep apologizing. > > Jason > > Thank you so much for the quality of your bug report. So here is an > idea to plug the leak: take a piece of paper, write the license on it, > roll it, and stick it up some sphincter on your server. > > Seriously... >
Could not have put it better... I've never seen such a crap bug report, there's not a single information that we could possibly use to figure out what the issue is and help you. Nope there's just bitching about a leak you experience with an operating system we must guess, with an opensmtpd version we must guess, on a proc we must guess... and we have to hurry because C'mon it tarnishes your reputation. You have got to be kidding. -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
