I have actually setup a server running testing (and thus samba 3.0.22) which runs in the very same domain than the sarge server (with 3.0.14a) which experiences this #349521 bug.
So, next time the sarge server is forced to restart winbind, I'll know about it and then, I'll be able to check whether the testing server still experiences the same problem. If it doesn't, I'll hereby declare the bug as fixed somewhere between 3.0.14a and 3.0.22 and close it with Version control pointing to 3.0.22 (in doubt).
signature.asc
Description: Digital signature
