(In reply to comment #8) > Can you explain more? Is it to preserve the file between reboots?
/var/run is the right place to store socket files according to the current Filesystem Hierarchy Standard: http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA It is also recommended by others: http://stackoverflow.com/questions/7580346/where-to-place-unix-domain-af-unix-sockets-end-points-files
But after testing the patch, I discovered that /var/run is not writable by non-root. So this won't work for Audacity which is launched by any user.
The socket file won't be preserved between reboots. Only data in /var/tmp would be preserved.
> Will every Linux distro have /var/run/? "Yann Le Doaré" claimed recently > on -devel that Linux "AlbatrOS" did not have /var/tmp/.
Every Linux distro should have /var/run (at least if they want to comply with the FHS).
(In reply to comment #8)
> Can you explain more? Is it to preserve the file between reboots?
/var/run is the right place to store socket files according to the current Filesystem Hierarchy Standard: refspecs. linuxfoundation .org/FHS_ 2.3/fhs- 2.3.html# VARRUNRUNTIMEVA RIABLEDATA stackoverflow. com/questions/ 7580346/ where-to- place-unix- domain- af-unix- sockets- end-points- files
http://
It is also recommended by others: http://
But after testing the patch, I discovered that /var/run is not writable by non-root. So this won't work for Audacity which is launched by any user.
The socket file won't be preserved between reboots. Only data in /var/tmp would be preserved.
> Will every Linux distro have /var/run/? "Yann Le Doaré" claimed recently
> on -devel that Linux "AlbatrOS" did not have /var/tmp/.
Every Linux distro should have /var/run (at least if they want to comply with the FHS).