https://bugs.freedesktop.org/show_bug.cgi?id=48226
Colin Guthrie <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Colin Guthrie <[email protected]> 2012-04-03 02:13:52 PDT --- Why would the cookie be in the runtime dir? The cookie is meant to be long lasting, e.g. we don't regenerate it on boot and it can be copied around. The runtime dir should be used for sockets and such like. If we do have a "cookie in runtime dir" approach we should copied it the first time if it doesn't exist, but that in itself may result in the same locking problems... should only happen once per boot, but then what is you update you're ~/.pulse-cookie and a client starts... should it compare timestamps etc? I'm not sure this is correct. But we certainly DO want to support the runtime dir generally. We have to be careful however, as on non-systemd systems, the fallback value for XDG_RUNTIME_DIR set by gnome did NOT consider NFS and actually used the XDG_CACHE_HOME which could easily reside on an NFS share. We should certainly NOT create our sockets on an NFS share. cf http://pulseaudio.org/ticket/928 (specifically http://pulseaudio.org/ticket/928#comment:8) -- 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
