Current best practice is not to use /tmp for Unix domain sockets.
Move the socket communication to DPDK runtime directory.
To quote systemd:
/run (traditionally /var/run) where privileged daemons can store
runtime data, such as communication primitives. This is where your
daemon should place its sockets.
See:
http://0pointer.net/blog/projects/tmp.html
https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html*
Stephen Hemminger (4):
net/af_xdp: replace /tmp with /run/dpdk
examples/vm_power_manager: replace /tmp with /run/dpdk
net/nfp: replace /tmp with /run/dpdk
net/cnxk: move socket from /tmp to /run/dpdk
doc/guides/sample_app_ug/vm_power_management.rst | 13 ++-----------
drivers/net/af_xdp/rte_eth_af_xdp.c | 2 +-
drivers/net/cnxk/cnxk_eswitch.h | 2 +-
drivers/net/nfp/nfp_cpp_bridge.c | 4 ++--
examples/vm_power_manager/channel_manager.h | 2 +-
5 files changed, 7 insertions(+), 16 deletions(-)
--
2.51.0
