|
|
|
sm.bak(4) -- Status monitor directories and file structures
|
|
The directories /etc/sm and /etc/sm.bak are generated by the rpc.statd daemon. Each entry in /etc/sm represents the name of the system to be monitored by the status monitor. Upon its recovery, the sta... |
|
sms.sme(4) -- SysMan Station event file
|
|
Introduction to System Management Event Files The SysMan Station Event file (.sme) describes all the events to which the SysMan Station daemon (smsd) should subscribe. In addition to event names, it a... |
|
|
ssh2_config(4) -- Configuration file for the Secure Shell client
|
|
The configuration file for the Secure Shell client reads configuration data from the following sources, in this order: the system's global configuration file (/etc/ssh2/ssh2_config) the user's confi... |
|
sshd-check-conf(4) -- Check what the configuration allows or denies based on incoming user and/or host name
|
|
The shd-check-conf file checks how sshd2 will react to an incoming user, based on the user name and the remote host name given as parameters. The following parameters are checked: AllowHosts DenyHosts... |
|
sshd2_config(4) -- Configuration file for the sshd2 daemon
|
|
The sshd2 daemon reads configuration data from the /etc/ssh2/sshd2_config file (or the file specified with the sshd2 -f command). The file contains keyword-argument pairs, one per line. Empty lines an... |
|
sshd2_subconfig(4) -- Describes the subconfiguration that can be used for the sshd2 daemon
|
|
You can specify configuration options in subconfiguration files that have the same format as the main configuration file. They are read after the daemon forks a new process to handle the connection. I... |
|
ssh_certificates(4) -- Describes the configuration files and keywords needed when using certificates with the Secure Shell ...
|
|
When using certificates with Secure Shell software, you need the ssh2_config Version 1.1 and sshd2_config Version 1.1 files and one or more special mapping files holding the user authorization data. (... |
|
ssh_externalkeys(4) -- Describes the external key providers that can be used with ssh2 software
|
|
For applications capable of using external keys, two strings must be specified: The provider name The initialization string for the provider These strings can be given on the command line or in the co... |
|
stab(4) -- Symbol table types
|
|
The stab.h header file defines some values of the n_type field of the symbol table of a.out files. These are the types for permanent symbols (that is, not local labels, etc.) used by the old debugger ... |
|
stanza(4) -- Stanza file format
|
|
A stanza file format is used in conjunction with the libAF(3) stanza file library. The stanza file syntax rules are as follows: Separate entries by one or more blank lines. A colon (:) terminates a en... |
|
state(4) -- Status monitor directories and file structures
|
|
The directories /etc/sm and /etc/sm.bak are generated by the rpc.statd daemon. Each entry in /etc/sm represents the name of the system to be monitored by the status monitor. Upon its recovery, the sta... |
|
statmon(4) -- Status monitor directories and file structures
|
|
The directories /etc/sm and /etc/sm.bak are generated by the rpc.statd daemon. Each entry in /etc/sm represents the name of the system to be monitored by the status monitor. Upon its recovery, the sta... |
|
Status(4) -- Contains information about the status of the uucp program contacts with remote systems
|
|
The /usr/spool/uucp/.Status directory contains information about the status of the uucp program contacts with remote systems. For each remote system contacted, the uucp program creates a file in the d... |
|
stl_comp(4) -- setld compression option files (*.comp)
|
|
Each software product that is distributed for installation by the setld utility can have an associated compression option file (productname.comp) where productname is the unique three-character produc... |
|
stl_ctrl(4) -- setld software subset control files (*.ctrl)
|
|
Each software subset that is distributed for installation with the setld utility has an associated subset control file (subsetname.ctrl), for example: OATODB100.ctrl. This file, created by kits utilit... |
