2015-08-16 21:33:37 +0200, Ansgar Burchardt: > Package: debian-policy > > User-level applications should not use sockets below $HOME by default: the > filesystem used for $HOME might not support them, as is the case for NFS > or OpenAFS. [...]
I don't know about OpenAFS, but sockets are supported on NFS. If they weren't, diskless systems wouldn't work. I'd argue if OpenAFS doesn't support sockets, it's not a Unix file system. What is true is that you can't have a process listen on a socket on NFS on one system, and another process connecting to that same socket on a different system and expect that to become a network connection. The solution to that, like all host-specific files is to embed the host name in the file path (like ~/.Xdefaults-myhost). Now I agree there's no strong reasone to want sockets in $HOME, other than it's an obvious place owned by the user and it makes in obvious that it should be the user responsible for cleaning-up after them. -- Stephane
