Sponsored Content
Operating Systems OS X (Apple) Software Update reporting script Post 302306242 by [MA]Flying_Meat on Saturday 11th of April 2009 08:56:30 PM
Old 04-11-2009
I'm not seeing the -l option in man softwareupdate, but it ran without complaining in my one test (on a machine that needed no updates).

You should be able to grep the lines relating to software updates, then pipe to "wc -l"

Store that in a variable, then write the host name and update count to a file, presumable with an easily parsible delimiter (like "=" for instance).

Push the file to a central mutually accessible location, then cat the files.
From there you can create your report.

The important part is determining the unique character/s you want to grep for on the hosts, before writing the host specific reports. It's pretty easy to determine from the "man" output, and running the command on a few machines that actually need updates.
 

2 More Discussions You Might Find Interesting

1. SuSE

update package/software questions

Hi, In SUSE linux, it looks like that I can update the package using YAST or install the package from source. So, which way works better? Also, if i install the package of new version. Do i need to remove/delete the old version package, or I just need to change my environments and keep the old... (0 Replies)
Discussion started by: jianma
0 Replies

2. Fedora

Newby: How to actually update software?!

Hi All - 1) I work with bigdate for a living, use lots of neat software, SAS, SQL Server, etc. I know how to get my data and such, analyze it, etc... 2) I use UNIX at work (Solaris mostly) and can easily navigate around Unix and get the job done, vi and sas -nodms are about my fav, and some... (6 Replies)
Discussion started by: sas
6 Replies
KPROPLOG(1)						      General Commands Manual						       KPROPLOG(1)

NAME
kproplog - display the contents of the Kerberos principal update log SYNOPSIS
kproplog [-h] [-e num] DESCRIPTION
The kproplog command displays the contents of the Kerberos principal update log to standard output. It can be used to keep track of the incremental updates to the principal database, when enabled. The update log file contains the update log maintained by the kadmind process on the master KDC server and the kpropd process on the slave KDC servers. When updates occur, they are logged to this file. Subsequently any KDC slave configured for incremental updates will request the current data from the master KDC and update their principal.ulog file with any updates returned. The kproplog command can only be run on a KDC server by someone with privileges comparable to the superuser. It will display update entries for that server only. If no options are specified, the summary of the update log is displayed. If invoked on the master, all of the update entries are also dis- played. When invoked on a slave KDC server, only a summary of the updates are displayed, which includes the serial number of the last update received and the associated time stamp of the last update. OPTIONS
-h Display a summary of the update log. This information includes the database version number, state of the database, the number of updates in the log, the time stamp of the first and last update, and the version number of the first and last update entry. -e num Display the last num update entries in the log. This is useful when debugging synchronization between KDC servers. -v Display individual attributes per update. An example of the output generated for one entry: Update Entry Update serial # : 4 Update operation : Add Update principal : test@EXAMPLE.COM Update size : 424 Update committed : True Update time stamp : Fri Feb 20 23:37:42 2004 Attributes changed : 6 Principal Key data Password last changed Modifying principal Modification time TL data SEE ALSO
kpropd(8) KPROPLOG(1)
All times are GMT -4. The time now is 10:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy