Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IBM Aix Performance Toolbox xmservd misbehavior

Status
Not open for further replies.
Aug 1, 2002
4
US
Am using IBM Performance Toolbox to capture utilization metrics. Configuration file xmservd.cf set to roll logs weekly and delete data older than 35 days. Old logs not being deleted and new logs hold more than a weeks worth of data.

1) Why?
2) Recommended procedure for recycling xmservd (filtd too)?
3) Recommended settings for xmservd process startup?

Have tried redbooks, IBM site, threatening to replace the software with BMX patrol, and prayer. Any and all help gratefully received.
 
Perf Toolbox must be bad if you are considering BMC Patrol. =)

To your question, the man page I found indicates that you must start xmservd with inetd and so you must put your options in /etc/inetd.conf. Apparently there are two log files, /etc/perf/xmservd.log1 and 2, and their size is determined by the -s option to xmservd. Default is 100,000 bytes, minimum is 5000 and maximum is 10,000,000.

hth IBM Certified -- AIX 4.3 Obfuscation
 
It's not the xmservd.log1 and log2 files that contain the utilization recordings. The recording files are called azizo.yymmdd, but xmservd must be doing the work, since that filtd are the only persistent processes running.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top