When you are on the window
screen, the computer monitor
should be displaying a small
white window with black and
green printing, if you have not
logged in. The host name of your
computer is on the top line of the
window.
|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.naic.edu/~astro/aovlbi/fsdoc/manuals/operref.html
Дата изменения: Sat Mar 30 19:09:33 2002 Дата индексирования: Sun Dec 23 02:11:12 2007 Кодировка: Поисковые слова: п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п |
VLBI Software Documentation
Field System
Operators' Reference
N. R. Vandenberg
NVI, Inc./GSFC
Operations Manual
NASA/Goddard Space Flight Center Version 9.0
Space Geodesy Program October 1, 1995
This manual is a reference for operation of Field System versions 9.0 and later. The sections of
this manual describe how to boot the computer, how to start the Field System and how to use its
features. Reference is made to other manuals that cover certain topics in more detail.
The book Running Linux, supplied with the new SWT computers, is a useful reference and
introduction to Linux.
Please refer to the Computer Reference manual for a list of useful books on Linux system
administration.
The following books are recommended for a good introduction to UNIX:
Introducing UNIX System V, by Rachel Morgan and Henry McGilton, McGraw-Hill Book Co.,
1987.
A Practical Guide to UNIX System V, by Mark Sobell, Benjamin/Cummings Publishing Co.,
1985.
2.0 Re-booting and Powering Down Linux
When you power up the PC, Linux will automatically boot. The boot process takes quite some
time so be patient. Many system messages are displayed as various services are brought up. If
you see any error messages, however, please note them and inform one of us (see section 1.3 in
the Computer Reference manual).
If you need to re-boot the computer while it is running, please take the following precautions and
follow these steps:
1. Log everyone off the computer before re-booting. This will ensure the integrity of the file
system. If the computer is hung up, obviously this is not possible. Sometimes when the machine
appears hung up at the Field System computer screen, you may still be able to log in via the
network using telnet or rlogin. The root user can reboot from a remote login.
2. At a login prompt on a virtual console (get there with Ctrl-Alt F1), type the user ID
powerdown.
**** IMPORTANT ****
The powerdown command must be used before shutting the computer off. Linux has a file
system that it builds when booting. This system must be "unbuilt" before shutting the computer
off. powerdown does this. This command may be given either at the login prompt or as a
command give by the user.
3. You will see a sequence similar to the following:
Broadcast message from root...
The system is going down NOW!
...
System is halted.
If you have an AMI FastSCSI hard disk controller in your computer and you have not reduced its
write-back delay to zero, you must WAIT 30 SECONDS. The hard disk light on the front of the
CPU will flash. Before powering off the CPU, wait until this light goes out. This will take about
30 seconds. The AMI FastSCSI Controller uses a write-back cache algorithm to speed write
operations. Some write operations may still be pending in cache at any time. The 30 second wait
is required to avoid loss of data.
4. Boot by pressing the reset button or cycling the power.
If the system is re-booted or powered off/on without using the powerdown command, the next
time it is booted the system goes through a cleanup of the file systems. This will take a few
minutes, noticeably longer than the normal boot-up sequence. Don't be alarmed, usually the
system is able to clean up the file systems automatically and without data loss. If problems arise,
please refer to the section on Manual Disk Recovery in the Computer Reference manual.
The Field System versions 9.0 and later use the X Window System (or X for short) to display and
manage the Field System programs. The Field System could be run outside of a windows
environment but the current configuration of the software assumes that X is running.
This section describes how to log in to the computer. If there is no prompt displayed for login, or
if the computer is not running, refer to the previous section about re-booting.
If there is no window display on the terminal, you may be on a different screen. You can move
around among virtual terminals or "virtual consoles" by doing the following:
type Ctrl-Alt then F1 for virtual terminal 1, black and white
type Ctrl-Alt then F2 for virtual terminal 2, black and white
type Ctrl-Alt then F3 for virtual terminal 3, black and white
type Ctrl-Alt then F4 for virtual terminal 4, black and white
type Ctrl-Alt then F5 for virtual terminal 5, black and white
type Ctrl-Alt then F6 for virtual terminal 6, black and white
type Ctrl-Alt then F7 to return to the X window screen
When you are on the window
screen, the computer monitor
should be displaying a small
white window with black and
green printing, if you have not
logged in. The host name of your
computer is on the top line of the
window.
Type the operator's login ID oper followed by Enter. Then type the operations password
followed by Enter. If you mis-type, an error message Login failed, please try
again appears and you can try again.
Once you have successfully logged in, the screen goes blank for a few seconds as the system
organizes the windows and resources you will need.
The display is ready for you to begin operations when you see a window on the screen, which has
the title login shell at the top. You will be able to type in this window if it has a green
border. If it does not have a green border, you can activate it if you move the mouse to the
window and click button 1 (see next section) or type Ctrl-Esc with the mouse
anywhere.
4.0 Window Basics
This section describes the basic operations you can do with the windows as they are set up for the
Field System. For a general user's guide to the X Window System using fvwm window manager,
refer to the first few sections of Running Linux. Most of the general information appearing in
O'Reilly volume 3 about X/Motif also applies to fvwm.
The Field System makes use of the X Window System with the fvwm window manager. It
provides the "look and feel" of the operator interface. The "look and feel" of fvwm is very
similar to that of the OSF/Motif mwm window manager used in earlier versions of the Field
System. Both fvwm and mwm are distinguished from other window managers by the elaborate
border that appears around the window. Only a few of the features of the border are described in
this section; refer to the Running Linux manual or the O'Reilly book for more information.
4.1 Parts of the Display
Root The gray background part of the screen is referred to as the "root" area. When the mouse
or trackball pointer is moved to the root area the pointer appears as a thick x. When the pointer is
moved to a window area the pointer appears as a thin I-beam.
Active window The window whose border is colored green is called the "active window." This
is the only window that will accept keyboard input. There may be only one active window at a
time. This is also called the window that has the "focus." In the Field System you must click on a
window to activate it, or type Ctrl-Esc to cycle to the next window in the stack and activate it.
Background windows Windows other than the active window are called "background
windows." Their borders are colored khaki.
Icons An "iconified" window is one that has been set aside for the time being. An "icon" is a
small window, usually placed along the lower edge of the screen, that is a reduced copy of the
original window.
Scroll bars All of the windows which display scrolling lines of output or input have a "scroll
bar" inside their left border. The purpose of the scroll bar is to allow you to review lines which
have scrolled up off the window. The use of the scroll bar is described in section 4.8.
A mouse or trackball is the input device for controlling the window displays. In the following
discussions, only the mouse is referred to for simplicity, although there is no functional
difference between the results if you use either device. The object that moves around on the
screen when you move the mouse is called the "pointer."
The Field System uses three buttons on the mouse. The left button is button 1, the center one is
button 2, and the rightmost one is button 3. If you have a two-button mouse, the left button is
button 1, the right is button 3, and the functionality of button 2 is achieved by pressing both
buttons simultaneously.
Care should be taken in using a mouse. Random button pushing while the mouse is moving can
have unpredictable results! Before moving the mouse around, first think about what you want to
do. Move the pointer until you see the appropriate shape, depending on whether you stop on a
window or the root area. Only then should you push the mouse button.
The buttons are used in a variety of ways to achieve different effects. In some cases you press and
release a button (called a "click"), in others you click twice, in others you hold the button down,
and in still others you hold down a key such as Alt or Ctrl and then click or hold the button.
Some common uses of the buttons to achieve certain functions are described in the following
sections.
Operators should keep the window display on the screen while the Field System is running,
otherwise the Field System will eventually stop. If you need to edit a file, check mail, etc., open a
new window (see next section) and use it to do what you need rather than switching to a different
virtual console.
If you want to return to the console display, type Ctrl-Alt followed by F1. You will be
switched to the black and white screen. You return to the window display by typing Ctrl-Alt
then F7.
The sessions that are run in windows are independent of sessions run on other screens.
Windows are stacked according to the order in which they were first opened. Typing Ctrl-Esc
allows you to activate a window which is adjacent on the stack of windows to the currently active
window. This is a convenient way to see a window that is not visible, i.e. it is hidden behind
another window.
4.4 Root Menu
The Root Menu is displayed when you move the pointer to
the root area and press and hold down button 1.
You select any of the options in the menu by moving the pointer
down the list until the desired option is highlighted, then release
the button.
The New Window option opens a new xterm window in the
middle of the screen. This is a utility window that you can use
for editing files, copying files, FTP, etc. When you are finished
with the window, make sure the window is active and then type
exit to exit. The placement of the window -- in the center of
the screen, obscuring the working windows below it --
indicates that it is a temporary window and should be closed
when you are finished with your work.
The Refresh option redraws the entire screen.
The Utilities option displays a sub-menu of certain system utilities that you may find useful
or diverting. More information on their use can be found in the O'Reilly volume 3.
The Restart option re-starts the window manager. This can be useful if you cannot activate
any of the visible windows or you are experiencing other unexpected window behavior.
Restarting the window manager does not affect programs that are already running, such as the
Field System.
The Extras option presents the standard Linux fvwm button 1 menu.
If you want to type into a window that is not active, move the pointer anywhere onto the desired
window or its border and click button 1. The window border will be highlighted in green
and you can type in that window. The former active window's border is changed to the khaki
color.
Another way to activate a window is to type Ctrl-Esc. Each time you type Ctrl-Esc the
next window in the stack is activated.
4.6 Closing a Window
When you "close" a window you remove it from the display and kill any process it is running. To
close a window, move the pointer to the square button in the upper left corner of the window and
click button 1. The "window menu" will be displayed. If the window had not been active
it is now activated and its border is colored green. Move down the list to Delete, and click
button 1 again. The window will disappear.
If you change your mind about wanting to use the window menu, simply move the pointer off the
menu and click button 1. The menu will disappear.
4.7 Iconifying and Restoring Windows
To iconify a window, move the mouse cursor and click on the smaller of the two buttons in the
upper right corner of the window. The icon will be placed in the lower right corner of the root
area; icons accumulate along the bottom of the display from the right.
Icons can be buried beneath full-sized windows, so don't be alarmed if the window you just
iconified seems to have disappeared. If you hold down button 3 you will see a list of all
windows; iconified ones are listed in parentheses. You can then select a window and if it is
iconified it will automatically be restored.
If the icon is visible, you can restore an iconified window to its original size, with a double click
on the icon.
You cannot iconify certain of the Field System windows: the login shell, the operator
input, log output, or fmset.
The scroll bar on the left edge of a window shows how full the buffer is that holds the lines that
have scrolled up off the window. As more lines scroll up, the gray hatched part of the scroll bar,
called the "thumb," is reduced in size. For the Field System, the number of lines in the scroll bar
buffer depends on the window. There are 500 lines allocated for the log display window, 100 for
the operator input window, and a smaller number for normal xterm windows.
To scroll backwards through previous output, first place the pointer on the thumb. The pointer
changes to a horizontal arrow. Now while you hold down button 2 you can move the
pointer up and down to scroll up and down through the buffer. You do not have to keep the
pointer within the thumb as long as you hold down button 2. Alternatively, with the pointer
placed in the scroll bar area, you can click button 3 to scroll up in the buffer by one page
per click. If you click button 1 you will scroll down in the buffer by one page.
When you stop scrolling the window remains fixed. The next time you type in the window or the
next time some output is printed in the window the display jumps down to the bottom of the
buffer.
A window does not need to be active for the scroll bar to work, but it will be activated when you
start to use the scroll bar.
4.9 Dumping a Window
The command xwd can be used to dump a window to a file. The command xuwd will "un-dump" it to display it on the screen. Follow these steps:
1. Enter xwd > win1 to dump a window to a file called win1.
2. The pointer turns into a crosshair. Click button 1 inside the window you want to save.
3. You will hear a beep as xwd starts to write the file. After it has completed, you will hear a
second beep.
To display a window dumped into a file, use these steps:
1. Enter xwud < win1 to see the window dumped into the file called win1.
2. An image of the saved window will appear. The string xwd: which appears in the title bar to
indicate that this is only an image of the window.
3. When you are finished viewing the window, type q to quit xwud.
If you install a printer, you can also dump a window to a printer.
4.10 Logging Out
When you want to log out of the Linux system, follow these steps:
If the Field System is running, shut it down cleanly using the terminate command.
Log out of the login window with the command logout or exit.
If you want to shut the computer off, please refer to the power down procedures in section 2.
This section describes how to start the Field System, what to expect to see on the screen, and
how to enter commands.
5.1 Starting fs
The Field System is started from the login shell xterm window by simply typing the
command fs at a system prompt. All of the initialization information will appear in this window.
If there is an error-free start-up of the Field System, the screen will have two visible windows
labeled login shell and operator input.
If any errors occur as the Field System starts up, an error message will be printed in the window
where you typed the fs command. Common start-up errors are missing control files, errors in
modified control files, and missing station program executable files. Refer to the Control Files
and Initialization manual for the details of what happens as the Field System starts up and for
the control file formats.
The window titled operator input is a 5-line by 80-character window at the bottom of the
screen. The operator input program, oprin, is running in this window. oprin's prompt is
always displayed in this window and you can enter input any time the window is active, i.e. when
it has the green border. If oprin's window is not active, i.e. it has a khaki border, move the
pointer to the window and click button 1.
Refer to the Experiment Operations manual for the common types of operator input that are
necessary to run an experiment.
As operator input commands are processed by the Field System, they are logged and displayed in
the other window on the screen (see next section).
You can review recent operator input commands by using the scroll bar or mouse button 3 (see
section 4.8).
You can also recall previous lines by using the Up-arrow and Down-arrow keys and then
edit them. You can edit the current line by moving the cursor with the Left-arrow and
Right-arrow keys. The characters you type will be inserted at the cursor position and the
Backspace and Delete keys can be used to delete characters to the left or right of the cursor,
respectively. When you have selected the command you want and have finished editing it, press
Enter to send it to the FS.
You can also use the SNAP "command completion" facility. Type the first few letters of the
SNAP command you want and then press the Tab key. If what you have typed is the
unambiguous beginning of a SNAP command, oprin will complete typing the command name.
If what you typed is ambiguous, you will hear a beep. In this case if you press Tab again all the
possible matches will be shown to you. If you type more characters until the choice is
unambiguous and press Tab again, then the command will be completed for you. For example, if
you type ter and press Tab, the line will be completed to read terminate. When you have
finished constructing your command, press Enter to send it to the Field System.
The window titled login shell is a 24-line by 99-character window placed at the top of the
screen. The program ddout is running in this window. All of the log output appears in this
window, including commands, responses, and errors. In addition this window displays
communications echoes, extended display responses, and extended error messages. Refer to the
logex manual for the format of the log entries.
This window is an output-only window and need never be activated once the Field System is
running. If it is accidentally activated, i.e., you see a green border around it, just activate another
window, usually the operator input window.
Use the scroll bar or button 3 to review portions of the log that have scrolled up off the window
(see section 4.8).
5.4 Terminating the Field System
When you are finished running the Field System, shut it down by activating the operator
input window and typing the terminate command. You can simply type ter Tab to get
the command name completed for you. All of the Field System programs will automatically be
terminated.
6.0 Operator Programs
This section describes the programs available for the operator to run.
6.1 Operator Menu
To display the programs available for operator activation, move the pointer to the root area and
press and hold down button 2. You will see the Operator Menu displayed.
You can run any of these programs by moving the
pointer down until the desired program is highlighted,
and then releasing the button.
The menu also shows you that there are single
keystrokes that activate these programs, once you are
familiar with the options. In the menu, C-S-
indicates that you should press Ctrl-Shift before
you type the command character. For example, typing
Ctrl-Shift-P will activate pfmed just as if you
had moved the pointer, displayed the menu, and
selected the Pfmed option from the menu.
Refer to the Computer Reference manual for information on how to customize this menu for
your station. The basic information is found in the manual page man fvwm.
6.2 Pfmed Option
Selecting the Pfmed option in the operator's menu or typing Ctrl-Shift-P will start the
pfmed program running in an xterm window placed in the center of the screen. pfmed is the
program that edits procedures and manages procedure libraries.
Refer to the pfmed manual for the available commands and for a description of how pfmed
interacts with the Field System.
When you are finished editing procedures with pfmed, type ex after the prompt to exit. The
window will be closed.
6.3 Monit Options
All three types of system monitor displays are available in the operator's menu. monit will only
run when the Field System is running.
Menu option Monit: time displays the date and time only, in a window placed in the upper
right corner of the screen.
Menu option Monit: status displays the system status information, in a window at upper
right, partially obscuring the log/display window.
Menu option Monit: Tsys displays the system temperatures in both IF channels and in all
video converters or baseband converters. It is placed just under the Monit: status display,
partially obscuring the log/display window.
Any of the monit windows can be closed using the methods described in section 4 above. All of
monit's windows are automatically closed when the Field System shuts down.
6.4 Setcl Option
This option should only be used when the Field System is at a quiet time. In other words, when
not many procedures or commands are running. This option will set the Field System time based
on the formatter time and if something is running that is time dependent, then something
disruptive could possibly happen and the Field System time may be set to an incorrect value.
Refer to the setcl manual.
6.5 Fmset Option
This option starts program fmset, used to set the VLBA or Mark IV formatter time. Refer to the
fmset manual.
This section describes the naming conventions for files used by the Field System that are
imported or exported to other locations.
The naming conventions for files used by the Field System are summarized in the table below.
The contents of each type of file are described following the table. The purpose of standardized
file names is that the file name will immediately indicate what it contains without the need to
examine the contents of the file. If you use these conventions, the Field System will
automatically assume or use the appropriate extension.
File names have two parts, the root and extension. There is a unique extension for each type of
file. The root of the file name is either the experiment code alone or the experiment code
followed by the station ID. In the table expcod is the 5- or 6-character code for the experiment
found in the master observing schedules. x is the one-character station ID.
| Type of File | Format of File Name | Example |
| schedule | expcod.skd or .drg | ppms1.skd |
| schedule notes | expcod.txt | ppms1.txt |
| station schedule summary | expcodx.lst | ppms1a.lst |
| station SNAP schedule files | expcodx.snp | ppms1a.snp |
| station special files | expcodx.pnt | rd9102p.pnt |
| field log file | expcodx.log | ppms1a.log |
| summary file | expcodx.sum | ppms1a.sum |
| procedure library | expcodx.prc | ppms1a.prc |
| weather data file | expcodx.wx | rd9102p.wx |
| cable data file | expcodx.cb | ppms1a.cb |
8.2 Types of Files
The file types listed in the table above each have a purpose within the VLBI system. This section
describes each file and provides a reference to the Field System manual in which the description
of the file format is found.
schedule
The schedule file contains all of the information about a particular experiment. It includes the
parameters with which the schedule was made, source positions and fluxes, complete station
information, frequency sequences, head position offsets, and the detailed observing schedule.
This file is often referred to as the "network" schedule file because it contains information for the
entire network of stations. This file is also called the "drudg file" when it is an output from
PCSCHED. Reference: Schedule File Format manual.
schedule notes
The schedule notes provide a summary of the schedule and written notes describing the purpose
of the experiment, the type of schedule being used, and any special procedures to follow for this
experiment.
station schedule summary
The station schedule summary is a listing of each observation a particular station participates in
for the experiment. It is generated by drudg using the station SNAP file. Normally the summary
is in the form of a printed listing, but it may also be directed to a file. Reference: drudg manual.
station SNAP file
The SNAP file for a station contains the SNAP commands to be executed for an experiment. It is
generated by drudg using the schedule file. This is the file that the Field System reads to run an
experiment. Reference: drudg manual.
station special files
Some stations require special files to run an experiment. These are often referred to as "pointing"
files because they were originally the interface to antenna pointing control programs. These files
are generated by drudg using the schedule file. Reference: drudg manual.
field log file
The Field System generates a log file that contains every SNAP command issued by the operator
or by the schedule, and all responses with monitor information. Reference: logex manual.
station summary file
The station summary file is normally generated at the correlator by program vlogx. A field
version of this program, flogx, had a brief existence but is no longer used. Reference: Mark III
Processing and Analysis Files memo (attached to this manual).
procedure library
Collections of procedures are found in procedure libraries. Reference: pfmed manual.
Appendix: Boot Messages
This appendix contains a listing of Linux boot messages and an explanation for each one.
A.1 Message List
The list below shows the typical messages you will see on the Field System computer screen
when it starts up and boots the Linux operating system. These messages were recorded using a
TAG 486DX-50 computer; the messages you see may differ slightly depending on the expansion
card models you have in your computer. The lines have been numbered to allow for easy
referencing from the accompanying notes in the next section.
1: LILO
2: Loading Linux...
3: Uncompressing Linux...done.
4: Now booting the kernel
5: Console: colour EGA+ 80x25, 1 virtual console (max 63)
6: Calibrating delay loop.. ok - 25.04 BogoMips
7: Serial driver version 4.11 with no serial options enabled
8: tty00 at 0x03f8 (irq = 4) is a 16550A
9: tty01 at 0x02f8 (irq = 3) is a 16550A
10: DigiBoard PC/Xx Driver V1.3: PC/Xi (64K) I/O=0x120 Mem=0xd0000 Ports=8
11: lp1 at 0x0378, using polling driver
12: Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
13: FDC 0 is a post-1991 82077
14: BusLogic SCSI: buslogic detect: configuring EISA/VESA/PCI HA at port 0x330, IRQ 14,
+BIOS 0xC8000, ID 7
15: BusLogic SCSI: buslogic detect: Model Number: Unknown
16: BusLogic SCSI: buslogic detect: firmware revision: 0.5
17: scsi0 : BusLogic SCSI driver 1.15
18: scsi : 1 host.
19: Vendor: SEAGATE Model: ST31230N Rev: 0290
20: Type: Direct-Access ANSI SCSI revision: 02
21: Detected scsi disk sda at scsi0, id 2, lun 0
22: scsi : detected 1 SCSI disk total.
23: SCSI Hardware sector size is 512 bytes on device sda
24: Memory: 14936k/16384k available (816k kernel code, 384k reserved, 248k data)
25: This processor honours the WP bit even when in supervisor mode. Good.
26: Swansea University Computer Society NET3.019
27: Swansea University Computer Society TCP/IP for NET3.019
28: IP Protocols: ICMP, UDP, TCP
29: 3c503.c:v1.10 9/23/93 Donald Becker (becker@cesdis.gsfc.nasa.gov)
30: eth0: 3c503 at 0x310, 02 60 8c d9 10 b4
31: eth0: 3C503 using programmed I/O (REJUMPER for SHARED MEMORY).
32: Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
33: Checking 'hlt' instruction... Ok.
34: Linux version 1.2.9 (root@bigbang) (gcc version 2.6.3) #2 Mon Jun 12 13:06:21 GMT 995
35: Partition check:
36: sda: sda1 sda2 sda3
37: VFS: Mounted root (ext2 filesystem) readonly.
38: Adding Swap: 17404k swap-space
A.2 Notes
The numbered notes in this section correspond to the numbered lines in section A.1.
Line 1:The word LILO, "Linux Loader" is printed character by character. Each character is
printed before or after LILO performs some specific action. If LILO fails at some point, the
letters printed so far can be used to identify the problem.
Line 6: The "BogoMips" figure illustrates relative CPU performance, but as the name indicates,
it should not be taken as an accurate way to predict how much faster a given processor is when
compared to another.
Lines 8, 9: Please check that you see the UART type printed as 16550A. 16450 and 16550
ports cannot be reliably used for MCB and/or 115200 baud upgraded Mark III data buffer.
Line 10: Is present in this form only if you have a DigiBoard serial board in your computer and it
has been correctly set up according to the Computer Reference manual. If you do not have a
DigiBoard in your computer you will see an error message stating that a DigiBoard cannot be
found. This can be ignored.
Line 11: This line shows the name of your printer port, lp0, lp1, or lp2. "Polling driver"
refers to the default setting that does not require an IRQ line for the port.
Lines 14--16: This line shows you the hardware settings detected on your AMI FastSCSI
(BusLogic-compatible) controller card.
Lines 19--21: Three lines are printed per each SCSI device (hard disk, CD-ROM, tape drive) you have connected on your SCSI bus. The field id tells you which SCSI ID number is used by a
given device.
Line 24: Tells you how much memory is left after the Linux kernel has been loaded (first figure)
and the total amount of RAM detected in your computer (second figure).
Lines 29--31: These lines show the detected settings of your 3C503 Ethernet card. Please note that the text REJUMPER for SHARED MEMORY is not an error message. On the contrary, if you have a DigiBoard serial card in your computer, you should check that this message appears! If 3C503 tries to use shared memory and there is a DigiBoard in your computer, networking becomes unreliable and can hang up your computer.