Your connection into the cluster can be personalized to your particular operating needs.
During login you may want the cluster to execute a
series of commands. Rather than type these
commands after each login, you can build a LOGIN/PROFILE. The LOGIN PROFILE commands are sent to the
node that you check into using cluster mail.
The user creates an cluster mail message addressed to the node (or
nodes) he connects to with a subject of "LOGIN/PROFILE"
and a body containing the list of commands.
Upon receipt of the mail, the AR-Cluster node saves the commands for
later execution. AR-Cluster will echo
back the text "LOGIN/PROFILE updated".
Sending an empty LOGIN/PROFILE mail message will
any clear previous LOGIN PROFILE commands.
AR-Cluster will echo back the text "LOGIN/PROFILE cleared".
For RF connections, we recommend keeping your
LOGIN/PROFILE file short. Configuring a
LOGIN/PROFILE that results in transferring a lot of traffic on a marginal RF
connection may cause timeouts and traffic congestion. Keep your LOGIN/PROFILE short so it produces a max of 20 lines
from the cluster.
Example
LOGIN/PROFILE:
sh/dx/10
sh/wwv/1
dir/new
Certain commands are stored on the node between logins. Thus LOGIN/PROFILE commands should not
contain any of the following commands: Filters, set/beep, set/name,
set/location, set/homenode, set/latlon, set/email, and enable commands for DX,
ANN, TALK, and WX.
Examples:
set/here
set/nohere
Examples:
set/beep
set/nobeep
Examples:
set/login_ann
set/nologin_ann
Examples:
set/macro 1=sh/dx
set/macro 2=sh/wwv
sh/macro