[Bug 19438] New: totem should default to socket in /tmp instead of home directory

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=19438
Ubuntu | totem

           Summary: totem should default to socket in /tmp instead of home
                    directory
           Product: Ubuntu
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: totem
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: dilinger at voxel.net
         QAContact: desktop-bugs at lists.ubuntu.com


Totem creates a (unix domain) socket that it uses for communicating with other
totem processes when it starts up.  This socket by default is placed in the
user's home directory (unless overridden by the environment variable
BACON_SOCKET_DIR).

The problem is, home directories are frequently shared across multiple machines,
via network filesystems such as NFS and OpenAFS.  Within the context of those
filesystems, a socket makes absolutely no sense, and sometimes will cause totem
to refuse to start at all (OpenAFS doesn't allow socket creation, so
bacon_message_connection_new() fails to create a new socket called
~dilinger/.totem.dilinger, and totem then refuses to start up).

It seems like /tmp is a much better location for things like sockets, as /tmp is
rarely shared between machines, and pretty much is guaranteed to be writable. 
So, I would recommend using /tmp/.totem.$USER.$RANDOM as the socket, and then
have totem check for /tmp/.totem.$USER.* upon startup.  I'll follow up w/ a
patch shortly.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.