parsec: Socket file location is not according to FHS

https://github.com/parallaxsecond/parsec/blob/b5e47603fb59bbde12c4e22fc4d5615004e9cfed/src/front/domain_socket.rs#L22 specifies the socket to be in /tmp/parsec/parsec.sock. However, according to the Filesystem Hierarchy Standard v2.3, the correct location for pid files and socket files is /var/run/ (System programs that maintain transient UNIX-domain sockets must place them in this directory.), with possibly an application-level folder if it has multiple files.

Could this perhaps get fixed, and maybe made configurable?

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 18 (10 by maintainers)

Most upvoted comments

Great, thanks!

Just published new versions: parsec-service 0.5.0 and parsec-client 0.10.0. Either of those two projects will not be compatible with lower versions of the other one 🚀

hug-dev on Oct 2, 2020

I believe this is all correct.

I think this point:

The service will not automatically delete the old socket after the update. That will have to be done manually.

can be expanded into:

The service will need to be stopped and manually uninstalled. New recommendations for secure deployment will have to be followed to install the service after the update.

We can provide instructions on how to uninstall in the same book page where the new instructions are written.

hug-dev on Sep 23, 2020