Comment 8 for bug 1910209

While the behavior has "more impact" when running with openvswitch-dpdk as one common path to put the sockets is under /var/run/openvswitch the problem is only in openvswitch.
I updated the bug tasks accordingly.

@Yi: I've checked my setups why I haven't seen this before and indeed I usually use a path like
"/var/run/vhostuserclient/vhost-user-client-1" and it works fine - so using something like that might be more than just a workaround for you.

Never the less I happen to know that /var/run/openvswitch was in some guides in the past. I even fixed one stray reference in our own docs [2] now to fully use "/var/run/vhostuserclient/vhost-user-client-1" as shown above (its examples had a mix of paths up to now).
So thanks for the report for that alone !

The upstream OVS docs [1] usually seem to use a path like "/tmp/dpdkvhostclient0".
But even in there are examples of "/usr/local/var/run/openvswitch/vhost-user-1".
Reading that has made me realize that those paths with the pattern "/var/run/openvswitch" are all from the pre vhostuserclient time, and back then restarting OVS killed the connection anyway.
So it wasn't a problem back then, but if users keep using those paths with vhostuserclient - then it is a problem.

Adding a TL;DR to the bug description.

[1]: https://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/
[2]: https://ubuntu.com/server/docs/openvswitch-dpdk