https://bugs.freedesktop.org/show_bug.cgi?id=48226
--- Comment #6 from Colin Guthrie <[email protected]> 2012-04-03 04:14:47 PDT --- (In reply to comment #5) > Okay, I misunderstood how the cookie works, and since the original reporter > found the locking issue to be portmap/lockd related, I guess this becomes > irrelevant (other than moving the sockets). Well I would still say the lock handling around .pulse-cookie could be more efficient anyway - e.g. in the vast majority of cases we just need to read it and then we're done. No need to lock in such situations really. Only when we need to overwrite it should we attempt to do any locking IMO. So I think the decided approach outlined on the ML thread still stands. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are the assignee for the bug. _______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
