Technical article 105105

Why does sar(ADM) -o produce .l and .1 files?

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

I am running sar(ADM) using the -o option, for example:

sar -o /tmp/sar_data t n

where /tmp/sar_data will contain the data reported by sar(ADM), and data will be sampled at n intervals of t seconds.

This command creates the files:
/tmp/sar/sar_data
/tmp/sar/sar_data.1
/tmp/sar/sar_data.l
What are the .1 and .l files for?  These were not created
on previous releases of SCO products.

Solution

sar(ADM) in releases prior to SCO OpenServer Release 5.0
logged all details into a single data file.

On SCO OpenServer 5.0 systems the files created are as follows:

/tmp/sar/sar_data.n

This contains data relating to CPU n, where n is 1 for the first CPU, 2 for the second CPU, and so on.

/tmp/sar/sar_data.l
This contains data relating to latches. See the -L option to
sar(ADM) and Chapter 7 of the Performance Guide for further
details on latches.
/tmp/sar/sar_data

This contains all other data logged by sar(ADM).

From the Xinuos technical article database, record 105105. Reproduced with permission. The original is at www.sco.com/ta/105105, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.