Tru64 UNIX Collect

[+]Year:Month:Day:Hour:Minute:Second

For example: +2010:11:18:23:30:00. Every time string field except the Second field is optional.

The optional plus (+) sign at the beginning of the time string indicates that time is relative to the beginning of the data collection period. If + is not specified, the -C option indicates absolute time. When time string fields are absent and absolute format is specified, the values from the beginning of collection are used.

If start_time is omitted, the start of the collection period is used. If end_time is omitted, the end of the collection period is used.
 

You can also use regular expressions to specify a group of disks. For example dsk* selects all disks. For information on regular expressions, refer to the grep(1) reference page or the Programming Support Tools guide.
 

# collect -e cf

The option letters map to the following subsystems:

p –proc
Specifies that the Process Statistics (RSS and VSZ in megabytes) are excluded from data collection. When included, this data appears similar to the following in the output from the collect command:
 

# MEMORY STATISTICS=
 

l –LSM volume
Specifies that LSM volume data is excluded from data collection. When included, this data appears similar to the following in the output from the collect command (Collect displays one volume at a time):
 

# RECORD 1 (943046665:0)
(Fri Nov 30 16:24:25 2000) ##

See also the -s option, which you use to specify subsystems that must be included in data collection.
 

As the file created is in binary format, you must use the Collect utility's -p option to replay the contents of the file.

See also the -a option, which enables you to simultaneously direct the output from the Collect utility to stdout (usually the terminal from which the Collect utility is invoked). You can also specify other data collection options with the -f option, such as -s or -n, to control what information is recorded in the file.
 

h &nd hourly at [0-59] minutes
An hourly rollover at the specified minute.
A value of -Hh3 will roll over the Collect log every hour at three minutes past the hour. For example: 0.03, 1:03, 2:03, and 3:03.

d –daily at [00:00-23:59] hours and minutes
A daily roll-over at the specified hour and minute in 24-hour time format.

For example, a value of -Hd14:2 will roll over the Collect log every day at system time 14:02 (2:02 PM).

w –weekly at [0-6@00:00-23:59] days, hours, and minutes
A weekly roll-over at the specified day, hour and minute in seven-day 24-hour time format. A value of Zero in the day field represents Sunday.

For example, a value of -Hw1@10:25 will roll over the Collect log every Monday at 10:25 AM.

m –monthly at [1-31@00:00-23:59] date, hours, and minutes
A monthly roll-over at the specified date, hour and minute in 31-day, 24–hour time format.

For example, a value of -Hm3@21:15 will roll over the Collect log every third day of the month at 21:15 (9:15 PM).

As for the value of time, you can specify day and week values for how_long. For example, -Hd14:12,2d5w will roll over the log every day at 14:12 (2:15 PM) and keep the log for 2 days and 5 weeks.
 

When you use this option, the initialization message echoed by the Collect utility is updated to confirm the value of I, as follows:

# collect -i 2:8
Initializing (2.0 seconds) (float OK)
#collect -i 5:12
PROC_INTERVAL must be
evenly divisible by INTERVAL

Note that in the second command, an error message is displayed as the value of PI must always be evenly divisible by the value of I.
 

-M [suspend_value,resume_value]

In the following example, Collect suspends disk writes when free disk space falls below 250 MB, and resumes writing when free disk space rises above 300 MB:

# collect -M 250,300
 

–t (time)
Shows absolute system and user time (T in data recorded for the process subsystem, the way the ps command does. The default is to show a one-second normalized delta since the last sample, thus making graphs of these time values more useful.

–m (memory)
Shows 8192 byte pages instead of megabytes (MB) for absolute memory values.

–f (force)
Do not prompt before overwriting an existing output file.

–n (nice)
Do not allow the Collect utility to set high scheduling priority for itself using nice.

–z (zipped)
Do not write a compressed (zipped) output file.

–l (lock)
Prevents the Collect utility from locking its pages into memory.

–q (queue)
Causes the Collect utility to use instantaneously measured queue lengths, instead of calculated averages.
 

To convert data files created using previous versions of Collect, use the -f option to specify an output_datafile.
 

pid [pid,...pid]
Collect data only for processes in list. Specify % to include the process for the collect command.

Ppid [pid,...pid]
Collect data only for processes whose parent PID (PPID) is specified, or that are members of a process group (PGID) with the same ID.

Ccommand [command,...command]
Collect data only for processes whose process names contain above string. This can be a partial string, but must match exactly. Regular expressions are not allowed.

Uuser/UID[user/UID,...user/UID]
Collect data only for processes owned by the specified users. User identifiers (UIDs) can be used in place of the user name. See the /etc/passwd file for a list of user account names and associated UIDs.
 

Do not enter a space between letters when specifying options. For example, the following command specifies that only the CPU and file system data are included:

# collect -s cf

Note that if you specify a subsystem that is not available on the local system, only a RECORD N header will be displayed. The following example shows what happens when t (tape) is specified, but no tape device exists on the system:

# collect -s t
.
.
#### RECORD 4 (943046239:0)
(Fri Nov 19 16:17:19 1999) ####
#### RECORD 5 (943046249:0)
(Fri Nov 19 16:17:29 1999) ####
 

cariad > collect -v
No objects found of type
hardware/tape

  found 4 Disks, 0 Tapes
  found CPU 0 at slot [0]
  found CPU 1 at slot [1]
  max_procs = 16384
  SAMPLE: 0
  Initializing (10.0 seconds)
 

-p number_unit

Where number is an integer representing the number of write instances and unit is one of the time options (wdhm), such as in the following examples:

-W 1h

Collect writes data to disk once per hour.

-W 1h30m

Collect writes data to disk every 90 minutes.