|
|
Installing and Administering Internet Services: HP 9000 Networking > Chapter 10 Using rdistStarting rdist |
|
After creating the distfile on the master host, you can start rdist from the command line or from a cron file. rdist must be run as root on the master host. There are two forms of the rdist command syntax. One form is the following:
-d var=value sets the value of the variable var to value. value can be an empty string, one name, or a list of names separated by tabs and/or spaces and enclosed by a pair of parentheses. The -d option is used to define variable definitions in the distfile. However, if you specify the -d option for a variable that is already defined in the distfile, the -d option has no effect (because the distfile overrides the -d option). -f distfile specifies distfile as the distfile to be used to update files and directories. If the distfile is not specified, rdist looks in the current working directory for the file distfile, then the file Distfile. -m host limits the updates to host, which is one of the hosts previously identified in the distfile. Multiple -m arguments may be specified. label performs only the command entries specified by label in the distfile. Other options are listed in Table 10-2 “rdist Command Line Options”. The other form of the rdist command syntax is:
-c pathname ... [login@]host[:destpath] updates file(s) in pathname on the remote host host. (The -c arguments are interpreted as a distfile.) login specifies the user name used to perform the update. destpath specifies the path name of the installed file on the remote host. Other options are listed in Table 10-2 “rdist Command Line Options”. Table 10-2 rdist Command Line Options
This section shows an example of what is displayed on the standard output on the master host when rdist is run. An example distfile is shown below:
rdist is started with no command line options. The display on the standard output on the master host is shown below:
Pluggable Authenticaion Modules (PAM) for authentication is supported on HP-UX. PAM support enables users who are not listed in /etc/passwd file to use the rexecd and remshd service. It also enbles you to use authentication methods other than the standard UNIX authentication. DCE integrated login and Kerberos are authentication mechanisms you can use in addition to standard UNIX authentication. The rexecd and remshd services will use the authentication mechanism specified in "OTHER" directive of the /etc/pam.conf file. To use other authentication methods, you must edit the /etc/pam.conf file. The /etc/pam.conf file is the configuration file for the Pluggable Authentication Module architecture (PAM). The pam.conf file contains a list of services. Each service is paired with a corresponding service module. When a service is requested, its associated module is invoked. Each entry in the /etc/pam.conf file has the following format:
Refer to the pam.conf manpage for a detailed description of each of the fields mentioned above. To use the rexec and remsh services enabled with PAM, add the following lines to the /etc/pam.conf file:
The remshd and rexecd services will use the above entries as configuration information for authenticating users. Adding the lines above tell rexec and remsh to use the UNIX authentication mechanism to authenticate the users. For every service (like rexec and remsh), it is possible to have more than one entry in the /etc/pam.conf file for each of the module types available. The module types supported include:
To enable DCE integrated logging authentication mechanism, add the following line to the /etc/pam.conf file:
The rexec service is not kerberised and will not work in the SIS environment. However, the remshd service is kerberised. To use the PAM modules in the SIS environment, add the following line to the /etc/pam.conf file.
Also in the Kerberos environment, remshd has command line options for combining UNIX method and Kerberos method of authentication. A combination of both Kerberos and UNIX authentication is available. These command line options can be set in the /etc/inetd.conf for the "kremshd" service. Refer to the kremshd(1m) manpage for a more detailed description of the options available. |
|