2 Čec
2013
2 Čec
'13
18:47
Hello Knot folks:
The 'rundir' obsoletes 'pidfile' config option, as the PID file will
always be placed in 'rundir'."
This is cool, unless you want to run multiple instances of KNOT on a single
machine. Can you reconsider this?
Jonathan
2 Čec
2 Čec
22:21
Hello Jonathan,
you can specify 'rundir' just like you used 'pidfile' before, the only
difference is, that it
will be a directory and UNIX socket would be stored there as well.
e.g.
knot-1.conf: system { rundir "/var/run/knot1"; }
knot-2.conf: system { rundir "/var/run/knot2"; }
etc.
All instances could still share the same 'storage' as before, or use
separate storage for each instance, whatever suits you the best. Or am I
missing something?
Cheers,
Marek
On 2 July 2013 18:47, <jh(a)netriplex.com> wrote:
Hello Knot folks:
“The 'rundir' obsoletes 'pidfile' config option, as the PID file will
always be placed in 'rundir'."
This is cool, unless you want to run multiple instances of KNOT on a single
machine. Can you reconsider this?
Jonathan
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
4 Čec
4 Čec
18:20
Hello Jonathan,
“The 'rundir' obsoletes 'pidfile'
config option, as the PID file will
always be placed in 'rundir'."
The 'pidfile' option is back (commit 3fea146). If the pidfile is not
specified, it defaults to '$(rundir)/knot.pid'. So both old and new
configs should work.
Jan
3971
days inactive
3973
days old
2 comments
3 participants
participants (3)
-
Jan Včelák -
jh＠netriplex.com -
Marek Vavruša