Experimental Physics and
Industrial Control System

I assume you did look at the man page...

*unix:</path/to/socket>*::
    Bind to a named unix domain socket that will be created at the specified
    absolute or relative path. The server process must have permission to
    create files in the enclosing directory.
    The socket file will be owned by the uid and primary gid of the procServ
    server process with permissions 0666 (equivalent to a TCP socket bound to
    localhost).

*unix:<user>:<group>:<perm>:</path/to/socket>*::
    Bind to a named unix domain socket that will be created at the specified
    absolute or relative path. The server process must have permission to
    create files in the enclosing directory.
    The socket file will be owned by the specified _<user>_ and _<group>_
    with _<perm>_ permissions.
    Any of _<user>_, _<group>_, and/or _<perm>_ may be omitted.
    E.g. "-P unix::grp:0660:/run/procServ/foo/control" will create the named
    socket with 0660 permissions and allow the "grp" group connect to it.
    This requires that procServ be run as root or a member of "grp".

*unix:@</path/to/socket>*::
    Bind to an abstract unix domain socket (Linux specific).
    Abstract sockets do not exist on the filesystem, and have no permissions
    checks.
    They are functionally similar to a TCP socket bound to localhost,
    but identified with a name string instead of a port number.

What additional information do you need?

Cheers,
~Ralph

On Sat, 21 May 2022 at 00:44, Han Lee via Tech-talk <tech-talk at aps.anl.gov> wrote:

Hi,

I am looking for any available documents regarding procServ unix socket options.

Does anyone have information for a dummy like me?

Best,

Han

--

Jeong Han Lee, Dr.rer.nat

Staff Scientist and Engineer

Lawrence Berkeley National Laboratory

1 Cyclotron Road Mailstop 46R0161

Berkeley, CA 94720, United States

Tel :+1-510-486-6163

Cell:+1-510-384-3868