18 Čen
2013
18 Čen
'13
11:20
On 18/06/2013 04:05, Robert Edmonds wrote:
Okay, but this can be left to packagers. On RedHat/CentOS, /var/run is
not a tmpfs, but is created as part of the system installation. Most
RPMs then install their own /var/run/$DAEMON directory. For any systems
where /var/run is on tmpfs, the packager can build the appropriate logic
in knot's startup script.
Regards,
Anand
a slightly different way to do this would be what
unbound does, which is
to have separate configure settings for the "run-dir" (e.g.,
/var/run/unbound) and files that default to being placed within the
"run-dir" like the pidfile.
Yes, that's an even better suggestion. Thanks Robert.
An RPM or DEB
package maintainer could then have the package create
/var/lib/knot and /var/run/knot with the correct ownership and
permissions. At least, that's what I do with my BIND and NSD packages.
directories under /var/run should be created in the daemon's init
script, not in the package. on many systems /var/run is a tmpfs.