On Tue, 04.11.14 21:42, Tomasz Torcz (to...@pipebreaker.pl) wrote:
On Tue, Nov 04, 2014 at 08:56:48PM +0100, Jan Včelák wrote:
Hi!
OK. I will remove the syslog. But I will have to keep network.target for
now as we support non-Linux systems as well. Adding support for rtnl or
Hi!
OK. I will remove the syslog. But I will have to keep network.target for
now as we support non-Linux systems as well. Adding support for rtnl or
IP_FREEBIND would mean duplicating a lot of code... probably.
Note that invoking IP_FREEBIND is just a single setsockopt() line...
You are
On Tue, Nov 04, 2014 at 08:56:48PM +0100, Jan Včelák wrote:
Hi!
OK. I will remove the syslog. But I will have to keep network.target for
now as we support non-Linux systems as well. Adding support for rtnl or
IP_FREEBIND would mean duplicating a lot of code... probably.
Note that
On Mon, 15.09.14 13:03, Jan Včelák (jan.vce...@nic.cz) wrote:
After=syslog.target is redundant since a long time. Consider removing
this. And After=network.target usually doesn't do what one might thing
it does and with well written software that listens to rtnl or uses
IP_FREEBIND not
On Tue, Sep 16, 2014 at 01:22:39PM +0200, Jan Včelák wrote:
Hi Colin,
This approach gives you nice flexibility and control over instance
units, but still gives you the ability to start/stop individual
instances and control all of them at once too!
Yes, you are right. I tried this and
Hi Colin,
This approach gives you nice flexibility and control over instance
units, but still gives you the ability to start/stop individual
instances and control all of them at once too!
Yes, you are right. I tried this and it works pretty well.
However, the knot.target can be used only for
After=syslog.target is redundant since a long time. Consider removing
this. And After=network.target usually doesn't do what one might thing
it does and with well written software that listens to rtnl or uses
IP_FREEBIND not even necessary...
OK. I will remove the syslog. But I will have to
Jan Včelák wrote on 15/09/14 12:03:
3.) In case of multiple instances, is there a way to control them all at
once?
Use PartOf= for this...
OK. Thanks. I will take a look at it!
Just for a few more hints here:
You would create a knot.target unit which is just a standard target
Hello list!
I have a few questions regarding a proper way to setup and use template
instantiated services.
We develop an authoritative DNS server called Knot DNS. Currently, we provide
knot.service unit file to start a single instance of the server. However, some
of our users need multiple
On Tue, 26.08.14 16:43, Jan Včelák (jan.vce...@nic.cz) wrote:
knot.service:
[Unit]
Description=Knot DNS Server
After=syslog.target network.target
[Service]
ExecStart=/usr/sbin/knotd -c /etc/knot/knot.conf
ExecReload=/usr/sbin/knotc -c /etc/knot/knot.conf reload
[Install]
10 matches
Mail list logo