Hello Jonathan,<div><br></div><div>you can specify &#39;rundir&#39; just like you used &#39;pidfile&#39; before, the only difference is, that it</div><div>will be a directory and UNIX socket would be stored there as well.</div>

<div><br></div><div>e.g.</div><div>knot-1.conf: system { rundir &quot;/var/run/knot1&quot;; }</div><div>knot-2.conf: system { rundir &quot;/var/run/knot2&quot;; }</div><div>etc.</div><div><br></div><div>All instances could still share the same &#39;storage&#39; as before, or use separate storage for each instance, whatever suits you the best. Or am I missing something?</div>

<div><br></div><div>Cheers,</div><div>Marek</div><div><br><div class="gmail_quote">On 2 July 2013 18:47,  <span dir="ltr">&lt;<a href="mailto:jh@netriplex.com" target="_blank">jh@netriplex.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hello Knot folks:<br>
<br>
“The &#39;rundir&#39; obsoletes &#39;pidfile&#39; config option, as the PID file will<br>
always be placed in &#39;rundir&#39;.&quot;<br>
<br>
This is cool, unless you want to run multiple instances of KNOT on a single<br>
machine.  Can you reconsider this?<br>
<br>
Jonathan<br>
<br>
<br>
_______________________________________________<br>
knot-dns-users mailing list<br>
<a href="mailto:knot-dns-users@lists.nic.cz">knot-dns-users@lists.nic.cz</a><br>
<a href="https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users" target="_blank">https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users</a><br>
</blockquote></div><br></div>