BatchLogin (2.0) BLTRC Configuration Specification

   /export/home/bob/.batch2/bltrc

This document explains some of the more common settings available.

Syntax

# 
# Written by /opt/fericyde/bl2/batchlogin on Thu Mar 25 13:22:57 EST 2004
# 
DEFAULTLIST=myservers.blf
SCRIPT=SHELL.exp
TERMLOGIN=termstart.sh
PWUPDEF=c
PWUPTIME=5
BL_COLOR="WB"
#  Turn off display for non blt sessions
# NODISPLAY=YES
#

VARNAME=[value]

Variables

This is a "hook" variable that determines if bl2 should start with the users' display toggled on or off. There's a manual menu setting (DISPLAY) in BatchLogins' main menu -- if this variable is set to YES, that menu option is executed before every run. This allows for a default behavior of no Xwindow functionality for users that are more keyboard focused.

You can have any color combination you want, as long as it's either black on white or white on black. The two relevant settings are "WB" or "BW". Set to WB and you get white text on a black background. Set to BW and you get black text on a white background. WB is the default, if this variable is not in the bltrc.

It's important to note that the above variables control the behavior of "stock" scripts supplied by the BatchLogin auto-configure process. The SHELL.exp and termstart.sh programs look for these variables and behave accordingly. This means that you can still hack and slash away on either of those programs to have any color you want. It's not all that hard, just read the programs, the comments and color call-outs are for the most part self explanatory.

The exception is the call-out for the escape sequences in the SHELL.exp. It was found to be easier to capture a prompt setting and set it via escape sequence (see the stock SHELL.exp for more). To capture and set a prompt in similar fashion, use whatever method you want for setting a prompt, and echo "$PS1" into a file somewhere. Use vi on that and import it (carefully) into your shell -- following similar escaping methods for special characters, and similar results should be available.

An example prompt (with color) is shown below:

#WHITEONBLACK#
export PS1="$(tput setaf 4)+-+ $(tput bold)$(tput setaf 2)\$USER$(tput setaf 7)@
$(tput setaf 3)$(uname -n)$(tput setaf 7):$(tput setaf 5)\$PWD$(tput setaf 4)$(t
put rmso) +-+
$(tput setaf 7)# "

Note, all but the last line of the above would typically go in a users' .profile -- not in either the SHELL.exp -or- termstart.sh. Also note that the last line $(tput setaf 7)# " is the only broken line in the statement. The rest all goes on one line (starting with export PS1=). This is meant to provide an example color prompt only.

This is a "hook" variable that determines if bl2 should start with the users' display toggled on or off. There's a manual menu setting (DISPLAY) in BatchLogins main menu -- if this variable is set to YES, that menu option is executed before every run. This allows for a default behavior of no Xwindow functionality for users that are more keyboard focused.

It has the added benefit of pretty much preventing annoying guardian Xwindow dialog boxes from being displayed (where would they go?), thus, speeding up greatly the more text-focused operations that are typical for an administrator.

Timeout/pw behavior values

This is the default update behavior [c=continue] [u=update].

This is the default behavior when the node name mismatches connect value. Essentially, BatchLogin looks at the name you called the system from the outside and does a "uname -n" for comparison. If the two don't match, BatchLogin treats it as a red flag that something isn't right.

This is the default behavior when the password update routine fails. Possible Values are [s=shell] [p=pause] [a=abort] [r=hit return] [c=continue].

Select the time the program will wait for a password update decision. Enter update timeout in seconds (-1=forever)[10]:

Select the time the program wait if an error happens. Enter error timeout in seconds (-1=forever)[10]:

Enter password run-time timeout in seconds (-1=forever)[10]:

This variable turns on RSA log file encryption permanently (or until it is commented out). See the logging help page for more.