[nSLUG] Rating a Linux distribution by the response to the same bug
me at joedunn.com
Mon Jun 6 13:10:47 ADT 2011
Did you call support to have this bug triaged? Customer support will work
with you to get this to the right place and update you directly on
On Jun 6, 2011, at 10:58 AM, D G Teed <donald.teed at gmail.com> wrote:
Awhile ago I reported a bug in Debian 6, which was already known in samba's
winbind pam plugin, and had been fixed in samba upstream.
It impacted our use of saslauthd with postfix+TLS. The impact was
fairly significant: a resource leak would cause the service to fail
every few days.
The response from Debian developers was quite good I thought.
The bug was diagnosed, starting with only symptom information,
within the first day. Debian developers offered patched sources
the next day. Nine days later there were test packages built.
Within about one month and a half, the fixed samba packages
were in general release.
The bug history for Debian can be seen here:
Some months later, we've been bitten by the same bug, but in Redhat's
samba within Redhat Enterprise 6, this time impacting saslauthd with cyrus.
I've supplied Redhat with much better initial report of the problem
than I had in the Debian case, which should save them any time
comprehending what the impact is, how widespread this would be,
and what to do about it.
Here is the link to the Redhat bug report:
We're at 10 days since this has been reported to Redhat. The
only activity I've seen on the bug was the addition of a CC
and a link to the upstream bug report at Samba.
Since the bug is known, there might not be much reason for Redhat
to respond. However, it would be nice if they offered a test package.
In a prior samba bug with CIFS, it took us 10 months to get a fix,
and it was merely in a general Redhat release.
It will be interesting to see how soon Redhat can deliver a solution
compared to Debian for the identical bug. The problem is known,
the solution isn't risky, and the delivery to a solution path should be easy
nSLUG mailing list
nSLUG at nslug.ns.ca
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG