ufficient for Pacemaker to order after it, but here we see rsyslog
doesn't use it. I suppose we could order after both syslog.service and
rsyslog.service; I don't think that would hurt.
>> -Original Message-----
>> From: Ken Gaillot [mailto:kgail...@redhat.com]
>> Sent: Satur
, 2016 12:16 AM
>> To: users@clusterlabs.org
>> Subject: Re: [ClusterLabs] "After = syslog.service" it is not working?
>>
>> On 01/28/2016 12:48 AM, 飯田 雄介 wrote:
>>> Hi, All
>>>
>>> I am building a cluster in the following environments.
>>
29, 2016 12:16 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] "After = syslog.service" it is not working?
>
> On 01/28/2016 12:48 AM, 飯田 雄介 wrote:
> > Hi, All
> >
> > I am building a cluster in the following environments.
> > RHEL7.2
> > Pacemake
Hi, All
I am building a cluster in the following environments.
RHEL7.2
Pacemaker-1.1.14
The OS while it is running the Pacemaker was allowed to shutdown.
Logs at this time Pacemaker in the stop was not output to the syslog.
This "After = syslog.service" does not work is set to start-up script,