CentOS - May 2016 - yum update (first in a long time) - /var/log/dovecot no longer used

Me again,

Another change to my Centos 7.2 system since my 'yum update' yesterday
is
that /var/log/dovecot is no longer written to.

If I do 'systemctl status dovecot' I can see log entries. How can I now
do the
equiv or 'tail -f <logfile>'

Also, why has this changed, and where is it documented?

On Thu, 5 May 2016, Gary Stainburn wrote:
> Another change to my Centos 7.2 system since my 'yum update'
yesterday is
> that /var/log/dovecot is no longer written to.
>
> If I do 'systemctl status dovecot' I can see log entries. How can I
now do
> the equiv or 'tail -f <logfile>'
>
> Also, why has this changed, and where is it documented?
I'd take a stab at:

journalctl -fu dovecot

The full RHEL7 System Administrators Guide is well worth a read, but here's
the bit you're probably after.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-Using_the_Journal.html

Or maybe:

https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs

jh

On Thursday 05 May 2016 15:19:47 John Hodrien wrote:
>
> I'd take a stab at:
>
> journalctl -fu dovecot
>
> The full RHEL7 System Administrators Guide is well worth a read, but
here's
> the bit you're probably after.
>
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht
>ml/System_Administrators_Guide/s1-Using_the_Journal.html
>
> Or maybe:
>
> https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-v
>iew-and-manipulate-systemd-logs
>
> jh
Thanks John.  Another example of systemd project creep - AKA systemd's plan 
for world domination