Just to state my reasoning for thinking it is a GDM bug: gdm creates a file in /tmp/.gdm_socket, but /tmp has the sticky bit set, meaning that anyone else can delete other people's files, not possible without the sticky bit set.
/var/run is used for other programs to create sockets, and according to the Linux File Hierarchy Standard, is the correct place: http://www.pathname.com/fhs/pub/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA This would entirly justify the (acceptable) behaviour of the bootclean script, run from wherever and whenever in the boot process. FHS exists to prevent these classes of races/design bugs from occuring. Comments/suggestions? What arguments are against having the socket in /var/run? -- gdm's socket in /tmp is deleted by bootclean https://launchpad.net/bugs/79620 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
