Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#5993 closed defect (fixed)

Socket path can't be too long

Reported by: minondoa Owned by: minondoa
Priority: major Milestone: DRM4G-2.5.1
Component: DRM4G Keywords: drm4g, socket, path
Cc: carlos

Description (last modified by minondoa)

Make sure that the path in which the socket files are created doesn't exceed 108 characters in Unix systems and 104 in MacOS.

If not an exception such as this will occur:

unix_listener: <socket_path> too long for Unix domain socket

Change History (4)

comment:1 Changed 6 years ago by minondoa

  • Description modified (diff)

comment:2 Changed 6 years ago by minondoa

  • Resolution set to fixed
  • Status changed from new to closed

If the custom path is too long, it will then create the sockets in "~/.ssh/drm4g".

comment:3 Changed 6 years ago by minondoa

To clarify, this only happens when a resource is configured to use OpenSSH as the communicator. Normally the socket files would be created under $DRM4G_DIR/.drm4g/var/sockets, but in the case that the path is too long, they will be created in ~/.ssh/drm4g.

comment:4 Changed 5 years ago by minondoa

  • Milestone changed from DRM4G_multiplexing_openssh to DRM4G-2.5.1

Milestone renamed

Note: See TracTickets for help on using tickets.