Bug#891838: Starting kresd services with wildcard doesn't work

2018-06-07 Thread Sakirnth Nagarasa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Daniel On 05/24/2018 05:04 PM, Daniel Kahn Gillmor wrote: > let me know whether that works for you, Sakirnth! With the "--all" option in systemctl globbing works to start all kresd instances. Command: systemctl --all start 'kresd@*.service

Bug#891838: Starting kresd services with wildcard doesn't work

2018-05-24 Thread Daniel Kahn Gillmor
Control: forwarded 891838 https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/587 Hi Sakirnth-- On Thu 2018-03-01 12:41:34 +0100, Sakirnth Nagarasa wrote: > In my setup I use 4 instances of kresd@.service. The instances are > created with the following command: > > systemctl enable

Bug#891838: Starting kresd services with wildcard doesn't work

2018-03-01 Thread Sakirnth Nagarasa
Package: knot-resolver Version: 2.1.1-1 Severity: minor Hello, In my setup I use 4 instances of kresd@.service. The instances are created with the following command: systemctl enable --now kresd@1.service kresd@2.service kresd@3.service kresd@3.service The problem is when I stop all kresd