On 14 Nov 2016 14:26, Steve Dickson wrote: > On 11/14/2016 02:12 PM, Mike Frysinger wrote: > > On 14 Nov 2016 10:09, NeilBrown wrote: > >> On Sat, Nov 12 2016, Mike Frysinger wrote: > >>> 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. > > /var/run should work across systems i believe. at least BSD's support it. > > In the Red Hat distos /var/run is a symbolic link to /run and the systemd > folks have asked us to use /run instead of /var/run yes, but we already know that's not an acceptable default -- /run today is Linux specific. the question i was responding to here is if there's a portable location that is better than /tmp. Linux distros already know that for many packages they need to pass flags to get /run behavior. rpcbind is no different. -mike
Attachment:
signature.asc
Description: Digital signature
