BAST - Pass partition definition file

SYNOPSIS

$PASSDIR/BAST

DESCRIPTION

The BAST file defines the number of satellite passes that can be kept online, and where the data for each pass is stored. Pass data is stored in 1-relative numbered pass partitions, where pass partition N corresponds to pass N in the online pass catalog.

A pass partition can be (1) a whole individual raw disk partition, (2) a subset of a larger raw disk partition, (3) a plain UNIX disk file, or (4) /dev/null if the data is only processed during reception. Raw disk partitions perform better than plain UNIX files, since I/O bypasses the normal UNIX file system buffer pool.

The automatic scheduling system of TeraScan requires at least 2 pass partitions, even if they correspond to the same file. Two pass partitions should not refer to the same file, unless that file is /dev/null.

If using raw disk partitions, permissions should be set to read-write for all TeraScan users. Also, make sure that the raw partitions do not overlap each other and are distinct from partitions containing UNIX file systems!!

This file has the following format; lines beginning with # are ignored:

pass_number start_block end_block chain_list filename
pass_number start_block end_block chain_list filename
etc.

where

pass_number - 1-relative pass number. Pass partition N corresponds to pass N in the online pass catalog.

start_block - 0-relative start block number, usually 0 unless the partition is a subset of a larger partition. Blocks are 512-bytes long.

end_block - 0-relative end block number. For example, if the partition contains 1000 blocks, and start_block is 0, then end_block is 999.

chain_list - Comma-separated list of telemetry chain numbers. If this list contains N, then data from telemetry chain N can be stored in this partition.

filename - Name of raw UNIX disk partition device file or plain UNIX file. This name should be fully qualified.

EXAMPLE

The following example shows a four pass-partition configuration under SunOS 4.1.3. Note that the first record indicates the number of partitions. Note also data from chain 1 can only be stored in the first two partitions, and that data from chains 2 and 3 can only be stored in the last two partitions.

1 0 255358 1   /dev/rsd1a
2 0 255358 1   /dev/rsd1b
3 0 255358 2,3 /dev/rsd1c
4 0 255358 2,3 /dev/rsd1d 

Last Update: $Date: 2001/08/16 23:28:16 $