I'm trying to setup two CentOS7 systems with automatic security updates to run as my kubernetes nodes. I've also centralized all my outgoing mail through my mailgun service, so I've been using the cli tool "mailx", which I have configured with my credentials. Coming from Fedora32 and CentOS7, dnf-automatic had a helpful emission target that was "email_command". By default it sent notifications using this command. With yum-cron, all I see is "email", which doesn't appear to use the "mail" command.
I would like to set up something myself to send the daily yum activity, but it's not clear at all where I should expect the yum-cron "stdio" output to end up at. I "started" the service, which is really just creates sentincal file to allow the yum.daily cron entry to run. However, when I look at /var/log/yum, there's nothing there of interest. I can see that it claims to have run, but I have no idea what it did.
Is there another place I should be looking for what this actually did?
Separately, I'm looking for a way to confirm its behavior. I was able to do this on my dnf systems by downgrading a package, but if I use `yum downgrade X` on this CentOS7 system...it just reports success and does nothing. Any ideas about that one?
-GN
Le 17/08/2020 à 10:49, Gunnar Niels a écrit :
I'm trying to setup two CentOS7 systems with automatic security updates to run as my kubernetes nodes. I've also centralized all my outgoing mail through my mailgun service, so I've been using the cli tool "mailx", which I have configured with my credentials. Coming from Fedora32 and CentOS7, dnf-automatic had a helpful emission target that was "email_command". By default it sent notifications using this command. With yum-cron, all I see is "email", which doesn't appear to use the "mail" command.
I'm using yum-cron on all my CentOS servers, and mail notifications work just fine.
I've written a little blog article on how to configure everything:
https://blog.microlinux.fr/yum-cron-centos-7/
Cheers,
Niki
I'm trying to setup two CentOS7 systems with automatic security updates to run as my kubernetes nodes. I've also centralized all my outgoing mail through my mailgun service, so I've been using the cli tool "mailx", which I have configured with my credentials. Coming from Fedora32 and CentOS7, dnf-automatic had a helpful emission target that was "email_command". By default it sent notifications using this command. With yum-cron, all I see is "email", which doesn't appear to use the "mail" command.
I'm using yum-cron on all my CentOS servers, and mail notifications work just fine.
That wasn't really the question; I'm not challenging that the email emitter type notifications don't work.
I'm asking where the results of the yum-cron job are actually written to so I can see what it did. I want this because I want the `email_command` type functionality that's found in dnf-automatic with future OS versions, but is not present in yum-cron.
-GN
Le 18/08/2020 à 03:00, Gunnar Niels a écrit :
I'm asking where the results of the yum-cron job are actually written to so I can see what it did.
Well, that's your answer. Here's the content of an email sent by Yum-Cron. So you everything that happened under the hood:
The following updates will be applied on nestor.microlinux.lan: =============================================================================== Package Arch Version Repository Size =============================================================================== Updating: curl x86_64 7.29.0-57.el7_8.1 updates 271 k libcurl x86_64 7.29.0-57.el7_8.1 updates 223 k libsss_idmap x86_64 1.16.4-37.el7_8.4 updates 155 k libsss_nss_idmap x86_64 1.16.4-37.el7_8.4 updates 162 k sos noarch 3.8-9.el7.centos updates 517 k sssd-client x86_64 1.16.4-37.el7_8.4 updates 211 k systemd x86_64 219-73.el7_8.9 updates 5.1 M systemd-libs x86_64 219-73.el7_8.9 updates 416 k systemd-python x86_64 219-73.el7_8.9 updates 143 k systemd-sysv x86_64 219-73.el7_8.9 updates 94 k
Transaction Summary =============================================================================== Upgrade 10 Packages The updates were successfully applied
Cheers,
Niki
On 8/18/20 1:00 AM, Nicolas Kovacs wrote:
Le 18/08/2020 à 03:00, Gunnar Niels a écrit :
I'm asking where the results of the yum-cron job are actually written to so I can see what it did.
Well, that's your answer. Here's the content of an email sent by Yum-Cron. So you everything that happened under the hood:
That doesn't answer my question. I'm *not* using email, or asking what the output looks like.
I'm asking: if I use stdio as the emitter, where can I expect that output to be written to in the system?
- GN
Am 19.08.2020 um 11:03 schrieb Gunnar Niels gunnar.s.niels@gmail.com:
On 8/18/20 1:00 AM, Nicolas Kovacs wrote:
Le 18/08/2020 à 03:00, Gunnar Niels a écrit :
I'm asking where the results of the yum-cron job are actually written to so I can see what it did.
Well, that's your answer. Here's the content of an email sent by Yum-Cron. So you everything that happened under the hood:
That doesn't answer my question. I'm *not* using email, or asking what the output looks like.
I'm asking: if I use stdio as the emitter, where can I expect that output to be written to in the system?
The command
journalctl -t yum
will show you the updates that were applied.
-
Gunnar Niels -
Marc Balmer -
Nicolas Kovacs