![]() |
![]()
| ![]() |
![]()
NAME.cloginrc - clogin configuration file DESCRIPTION.cloginrc contains configuration information for alogin(1), blogin(1), clogin(1), csblogin(1), elogin(1), flogin(1), fnlogin(1), hlogin(1), htlogin(1), jlogin(1), nlogin(1), nslogin(1), rivlogin(1), and wlogin(1), such as usernames, passwords, ssh encryption type, etc., and is read at run-time. Each line contains either white-space (blank line), a comment which begins with the comment character '#' and may be preceded by white-space, or one of the directives listed below. Each line containing a directive is of the form:
add <directive> <hostname glob> {<value>} [{<value>} ...] or include {<file>} Note: the braces ({}) surrounding the values is significant when the values include TCL meta-characters. Best common practice is to always enclose the values in braces. If a value includes a (left or right) brace, space character, ampersand or blackslash, those characters must be backslash-escaped, as in:
add user <hostname glob> {foo\}bar} add user <hostname glob> {foo\ bar} Other special characters may be escaped without error, if desired. As .cloginrc is searched for a directive matching a hostname, it is always the first matching instance of a directive, one whose hostname glob expression matches the hostname, which is used. For example; looking up the "password" directive for hostname foo in a .cloginrc file containing
add password * {bar} {table} add password foo {bar} {table} would return the first line, even though the second is an exact match. .cloginrc is expected to exist in the user's home directory and must not be readable, writable, or executable by "others". .cloginrc should be mode 0600, or 0640 if it is to be shared with other users who are members of the same unix group. See chgrp(1) and chmod(1) for more information on ownership and file modes. DIRECTIVESThe accepted directives are (alphabetically):
FILES$HOME/.cloginrc Configuration file described here. share/rancid/cloginrc.sample A sample .cloginrc. ERRORS.cloginrc is interpreted directly by Tcl, so its syntax follows that of Tcl. Errors may produce quite unexpected results. SEE ALSOclogin(1), glob(3), tclsh(1)
|