NAME

Host.list - host information file


SYNOPSIS

item=data . .

HOST


DESCRIPTION

This file describes hosts in a Unix network. The file is organized so as to make it easier to remotely manage hosts on such a network.

This file is used by the Unix::Sysadmin:: object framework. The file may be edited manually, but be sure you know what you are doing.


FILE STRUCTURE

The file is separated into stanzas, each consisting of one or more fields, one per line. Each field begins with ``item='', where item is a tag naming the field. For example, the following (incomplete) stanza shows the host and ip fields for an example host:

 hostname=guzzler
 ip=192.168.90.12

Each stanza is separated from the next by a separator token on a line by itself. The token for this file is HOST.


FIELDS

The following sections document each defined field's structure and purpose.

hostname

Unqualified hostname of host. Lowercase

 Example:
 hostname=guzzler

aliases

Colon seperated list of aliases for this host.

 Example:
 aliases=boozer:drunk

ip

Host's IP address

 Example:
 ip=192.168.90.12

os

OS name and version. A colon seperated list NAME:MAJOR:MINOR:TEENY, where 'NAME' is the OS name, 'MAJOR' is the major version, 'MINOR' is the minor verson and ``TEENY'' is the really minor version.

 Example:
 os=FreeBSD:2:2:8-RELEASE

arch

Hardware architecture as returned by 'uname -m'.

 Example:
 arch=i386

amtype

Automounter type. Either 'amd', 'autofs' or 'none'

 Example:
 amtype=amd

rp

Responsible person. Username or email alias of person to blame for trouble with this system.

 Example:
 rp=grumpy

upreserve

Password preserve list. A colon seperated list of user names and/or uids. The Unix::Sysadmin:: framework will preserve entries matching this list when generating password files for this host.

 Example:
 upreserve=0:root

umap

User remapping entries. Colon separated list of key=value pairs. If key is found in the existing passwd file for a host, it will be replaced by the contents of th value entry in the User.list database. In the following example, the user ``foo'' is mapped to user ``bar''. The result will be a ``foo'' user, with the rest of the passwd information replaced by user ``bar''.

 Example:
 umap=foo=bar

gpreserve

Group preserve list. A colon seperated list of group names and/or gids. The Unix::Sysadmin:: framework will preserve entries matching this list when generating group files for this host.

 Example:
 gpreserve=1:2:3:60001:60002:other:bin:sys:noaccess:nogroup

gmap

Group remapping entries. Colon separated list of key=value pairs. If key is found in the existing group file for a host, it will be replaced by the contents of th value entry in the Group.list database. In the following example, two groups are remapped. The group ``wheel'' is mapped to group ``root''. The result will be a ``wheel'' group, with its members set to those found in the Group.list entry for group ``root''. The group with GID 65534 will have it's members replaced by those in the Group.list entry for group 65533.

 Example:
 groupmap=65534=65533:wheel=root

sshkey

The ssh key to use when managing other hosts from this host.

 Example:
 sshkey=/root/.ssh/access

command

Specifies a Unix command override for this host. Normally the framework uses the Cmds classes (see the Unix::Sysadmin::Cmds manpage) to determine where various Unix commands are on a given operating system. With this clause, you can override the framework's idea of where commands live, or add commands that aren't in the Cmds classes on a host-by-host basis. (But if you are adding a standard command, you should probably add it to the Cmds source code so all hosts have access to it.) You can have any number of command= stanzas in a host record.

 Example
 command=EMACS:/opt/gnu/bin/emacs

file

Specifies a Unix file path override for this host. Normally the framework uses the Files classes (see the Unix::Sysadmin::Files manpage) to determine where various Unix files are on a given operating system. With this clause, you can override the framework's idea of where files live, or add files that aren't in the Files classes on a host-by-host basis. (But if you are adding a standard Unix file, you should probably add it to the Filess source code so all hosts have access to it.) You can have any number of file= stanzas in a host record.

 Example
 file=SLAPDC:/usr/local/slapd/slapd.conf

=head1 EXAMPLE

Here's a complete example of a host stanza for guzzler:

 hostname=guzzler
 aliases=boozer:drunk
 ip=192.168.90.12
 os=FreeBSD:2:2:8-RELEASE
 arch=i386
 amtype=amd
 rp=grumpy
 upreserve=0:root
 umap=foo=bar
 gpreserve=1:2:3:60001:60002:other:bin:sys:noaccess:nogroup
 groupmap=65534=65533:wheel=root
 sshkey=/root/.ssh/access
 command=EMACS:/opt/gnu/bin/emacs
 file=SLAPDC:/usr/local/slapd/slapd.conf
 HINF


SEE ALSO

Man(3) pages (programmer's docs):

the Unix::Sysadmin::Host manpage, the Unix::Sysadmin::User manpage, the Unix::Sysadmin::Automount manpage, the Unix::Sysadmin::Group manpage, the Unix::Sysadmin::Netgroup manpage, the Unix::Sysadmin::List manpage, the Unix::Sysadmin::Cmds manpage, the Unix::Sysadmin::Files manpage the Unix::Sysadmin::Utility manpage the Unix::Sysadmin::Config manpage, the Unix::Sysadmin::Scoped manpage

Man(4) pages (file formats):

the Unix::Sysadmin::Host.list manpage, the Unix::Sysadmin::User.list manpage, the Unix::Sysadmin::Automount.list manpage, the Unix::Sysadmin::Group.list manpage, the Unix::Sysadmin::Netgroup.list manpage

Man(1m) pages (manager's docs):

the Unix::Sysadmin manpage, the Unix::Sysadmin::Setup manpage the usasetup manpage

the usatest manpage

the usabackup manpage

the usaupdate manpage

the usapush manpage


AUTHOR

Howard Owen <hbo@egbok.com>