On 06/08/2016 09:11 AM, Ken Gaillot wrote:
> On 06/08/2016 03:26 AM, Jan Pokorný wrote:
>> On 07/06/16 14:48 -0500, Dimitri Maziuk wrote:
>>> next question: I'm on centos 7 and there's no more /etc/init.d/>> anything>. With lennartware spreading, is there a coherent plan to deal
>>> with former
On 06/08/2016 10:11 AM, Dmitri Maziuk wrote:
> On 2016-06-08 09:11, Ken Gaillot wrote:
>> On 06/08/2016 03:26 AM, Jan Pokorný wrote:
>
>>> Pacemaker can drive systemd-managed services for quite some time.
>>
>> This is as easy as changing lsb:dovecot to systemd:dovecot.
>
> Great! Any chance
On 2016-06-08 09:11, Ken Gaillot wrote:
On 06/08/2016 03:26 AM, Jan Pokorný wrote:
Pacemaker can drive systemd-managed services for quite some time.
This is as easy as changing lsb:dovecot to systemd:dovecot.
Great! Any chance that could be mentioned on
On 06/08/2016 03:26 AM, Jan Pokorný wrote:
> On 07/06/16 14:48 -0500, Dimitri Maziuk wrote:
>> next question: I'm on centos 7 and there's no more /etc/init.d/> anything>. With lennartware spreading, is there a coherent plan to deal
>> with former LSB agents?
>
> Pacemaker can drive
On 07/06/16 14:48 -0500, Dimitri Maziuk wrote:
> next question: I'm on centos 7 and there's no more /etc/init.d/ anything>. With lennartware spreading, is there a coherent plan to deal
> with former LSB agents?
Pacemaker can drive systemd-managed services for quite some time.
Provided that the
Hi all,
next question: I'm on centos 7 and there's no more /etc/init.d/. With lennartware spreading, is there a coherent plan to deal
with former LSB agents?
Specifically, should I roll my own RA for dovecot or is there one in the
works somewhere?
TIA,
--
Dimitri Maziuk
Programmer/sysadmin
