On Sat, Nov 12 2016, Mike Frysinger wrote: > [ Unknown signature status ] > On 11 Nov 2016 14:36, NeilBrown wrote: >> rpcbind can save state in a file to allow restart without forgetting >> about running services. >> >> The default location is currently "/tmp" which is an over-used >> directory that isn't really suitable for system files. >> The modern preferences would be a subdirectory of "/run", which can >> be selected with a ./configure option. That subdirectory would still need >> to be created by something. > > the portable path is /var/cache instead of /run. i don't think libtirpc > should be configuring itself to assume Linux by default. In principle I agree. But is /var/cache really a good choice? We don't want the state files to persist over a reboot, and I strongly suspect that /var/cache is designed to do exactly that. Are there agree standards that are broader than Linux that we can look to? FHS defines /var/run (or even /run) but I suspect it is linux-only. https://en.wikipedia.org/wiki/Unix_filesystem#Conventional_directory_layout only suggests /tmp as something that won't survive reboot. Maybe we should continue to use the /tmp filesystem, but move to a subdirectory: /tmp/rpcbind ?? Thanks, NeilBrown
Attachment:
signature.asc
Description: PGP signature
