The dmaudit command is intended primarily for interactive use; some steps, such as configuration, must be done interactively. dmaudit uses a series of menus to display information and to solicit input from you.
For dmaudit to display its menus properly, it needs to know the dimensions of your screen. By default, it uses the values found in the environment variables LINES and COLUMNS. If the variables are not defined, dmaudit assumes a screen length of 24 lines and a width of 80 columns. You can either set these variables manually or use the resize command; see the resize(1) man page for further information. C shell users normally enter something similar to the following to set the screen size environment variables:
eval `resize -c`
Sometimes dmaudit invokes an editor to request additional information from you. It uses the editor defined in the environment variable VISUAL (which is read first) or EDITOR; if neither is defined, it uses the vi(1) command by default. If you want to use an editor other than the default, set one of the two environment variables before starting dmaudit. For example, a C shell user who wants to use the emacs(1) editor could enter the following:
setenv VISUAL emacs
Occasionally dmaudit needs to display more information than can fit on your screen. In these cases, it uses a page-wait mechanism to retain the current screen of data until you are ready to continue. Your screen fills with data down to the last line, which appears as follows:
Enter <CR> to continue:
When you are done examining the current screen, press ENTER to view the next screen of data. If you are not interested in the remaining data, you may enter the first character of the next menu item and press ENTER to skip directly to processing the next menu item. There is no way to page back to a previous screen after you have pressed ENTER.
The page-wait feature is needed for users with terminals whose data would otherwise scroll off the screen before they could read it. If you are using a windowing system such as the X Window System environment, you can minimize the occurrence of page waits by running dmaudit in a window that contains as many lines as possible and by using the scroll bars available in the X Window System environment.