0

I'm learning something about X11. And I was wondering what would happen if I'd deleted the directory "/tmp/.X11-unix". I tried it but actually, nothing special happened. Every GUI app runs unaffected. Why ?

I thought X client communicated with X server through unix domain socket, and the socket pathname is "/tmp/.X11-unix/X0".

My os is Ubuntu 14.04.

Any help will be appreciated.

Thomas Dickey
  • 51,086
  • 7
  • 70
  • 105
waterbully
  • 19
  • 1
  • 1

2 Answers2

3

Just because an entry in the file system is deleted does not mean the file descriptor stops working.

When a GUI application is started it connects to /tmp/.X11-unix/X0 and gets a file descriptor. From now on it is using the file descriptor, /tmp/.X11-unix/X0 is no longer needed by this application and, therefore, if you delete it, nothing happens to running applications.

However, trying to start new applications would not work any longer.

Linux has an extension that allows using names that are not bound to the file system: abstract names, see unix(7) for a description. Since these do not use the file system it does not matter at all if the file system entry has been deleted.

It looks like X supports both types of sockets. So clients can choose which one they want to use. So after removing the socket from the file system new clients that use the abstract name can still be started whereas new clients that use the socket in the file system will fail to start. However, old clients will continue to run in both cases.

Meixner
  • 615
  • 5
  • 8
0

The X server creates the directory and opens the socket in that directory. Clients do not open the socket directly but use the connect function (which does reference the path of the socket device). The socket continues to exist as long as the X server process has it open. The clue is in this wording from the connect manual page:

The connect() system call connects the socket referred to by the file descriptor sockfd to the address specified by addr. The addrlen argument specifies the size of addr. The format of the address in addr is determined by the address space of the socket sockfd; see socket(2) for further details.

That is, the address given in the connect call is not necessarily a filesystem path that applications can test by other means but is simply something known to the kernel when applications ask to open the socket.

Thomas Dickey
  • 51,086
  • 7
  • 70
  • 105
  • Thanks for your answer. But I'm still a little confused, could you please show me an example? I guess an GUI app should have the following code: /* create a socket */ int sockfd = socket(AF_UNIX, SOCK_STREAM, 0); struct sockaddr_un address; address.sun_family = AF_UNIX; strcpy(address.sun_path, "/tmp/.X11-unix/X0"); /* connect to the server */ int result = connect(sockfd, (struct sockaddr *)&address, sizeof(address)); – waterbully Jun 26 '15 at 11:47
  • X does not open the filesystem path. It opens a socket. **[Here](http://cgit.freedesktop.org/xcb/libxcb/tree/src/xcb_util.c)** is a pointer to Xcb's code which you might want to study. – Thomas Dickey Jun 26 '15 at 22:48