<div dir="ltr"><div dir="ltr">Logging on the client isn't enabled by default, but I believe you can get that information by enabling it in the /etc/sysconfig/rhn/up2date config file.<div> </div><div><div>writeChangesToLog[comment]=Log to /var/log/up2date which packages has been added and removed</div><div>writeChangesToLog=1</div></div><div> </div><div>Otherwise you can query the API to get all the events for a particular system. </div></div></div> <div class="gmail_quote"><div dir="ltr">On Wed, Jan 9, 2019 at 5:24 AM <a href="mailto:P.Cookson@bham.ac.uk">P.Cookson@bham.ac.uk</a> <<a href="mailto:P.Cookson@bham.ac.uk">P.Cookson@bham.ac.uk</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div lang="EN-GB"> <div class="gmail-m_-2318441653903323227WordSection1"> Good morning all I’ve found that /var/log/yum.log, on client systems, isn’t updated when patching RHEL 6/7 systems from a Spacewalk server (v2.8). I know details of patching activities can be found in the Schedule > Completed Actions or yum history, after the event, but is there any log on client or server that can be monitored from the command line actually during patching? It’s just to monitor the patching activity, really, rather than a need to trace a problem or similar. If not, I presume that’s because the details you see in Schedule > Actions are actually being directly written to the embedded PostgreSQL database? Regards Philip Cookson Linux Administrator IT Services ERI Building Edgbaston Birmingham B15 2TT Tel: 0121 414 4731 Email: <a href="mailto:p.cookson@bham.ac.uk" target="_blank">p.cookson@bham.ac.uk</a> </div> </div> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></blockquote></div>