Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have found the example of using the local sockets. The code from examle uses the path
#define UNIXSTR_PATH "/tmp/unix.str"
as the name of a socket. Is this a best practice of choosing the socket name? Should I use something like
/var/run/com.company.executable.socket
writing the daemon on Linux Ubuntu?
Putting it in
/var/runis fine, but the sockets are usually named after the executable itself and not in some Javaesque fashion.