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.
writeChangesToLog[comment]=Log to /var/log/up2date which packages has been
added and removed
writeChangesToLog=1
Otherwise you can query the API to get all the events for a particular
system.
On Wed, Jan 9, 2019 at 5:24 AM p.cook...@bham.ac.uk
wrote:
> 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: p.cook...@bham.ac.uk
>
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
