[Spacewalk-list] OSAD auditing

[Andy Ingham]

I've always just done a super simplistic:

	spacecmd system_details *.duke.edu > temp.txt

Followed by a

	grep -c offline temp.txt

Followed, if need be, by searching through the temp file to see the actual
hosts.

Andy

Andy Ingham
IT Infrastructure
Fuqua School of Business
Duke University






On 11/18/13 11:17 AM, "Paul Robert Marino" <prmarino1 at gmail.com> wrote:

It could be done via the API's

http://www.spacewalkproject.org/documentation/api/1.9/handlers/SystemHandle
r.html#listActiveSystems

http://www.spacewalkproject.org/documentation/api/1.9/handlers/SystemHandle
r.html#listInactiveSystems

http://www.spacewalkproject.org/documentation/api/1.9/handlers/SystemHandle
r.html#getDetails

but I don't know of a tool that does it out of the box.

On Mon, Nov 18, 2013 at 9:29 AM, Coffman, Anthony J
<Tony.Coffman at snapon.com> wrote:
> Is there any easy way to audit for offline OSAD agents at a mass level
> (hundreds of machines)?
>
>
>
> The method I¹ve been using is to schedule a hardware refresh for the
>group
> and then manually going to look at systems that don¹t complete the
>action in
> a short period of time.  Surely , there must be a better way?
>
>
>
> Thanks,
>
> --Tony Coffman
>
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list