|
|
|
ftpusers(4) -- security file for ftpd(1M)
|
|
ftpd rejects remote logins to local user accounts that are named in /etc/ftpd/ftpusers. Each restricted account name must appear alone on a line in the file. The line cannot contain any white space. User accounts that specify a restricted login shell in /etc/passwd should be listed in /etc/ftpd/ftpusers because ftpd accesses local accounts without using their login shells. UUCP accounts should be ... |
|
gated-confi(4) -- GateDaemon Configuration Guide
|
|
Configuration Overview + Introduction + Statement Summary + Preferences and Route Selection + Trace Statements and Global Options + Directive Statements + Options Statements + Interface Statements and Configuration + Definition Statements |
|
|
gated.conf(4) -- GateDaemon Configuration Guide
|
|
Configuration Overview + Introduction + Statement Summary + Preferences and Route Selection + Trace Statements and Global Options + Directive Statements + Options Statements + Interface Statements and Configuration + Definition Statements |
|
gated.config(4) -- GateDaemon Configuration Guide
|
|
Configuration Overview + Introduction + Statement Summary + Preferences and Route Selection + Trace Statements and Global Options + Directive Statements + Options Statements + Interface Statements and Configuration + Definition Statements |
|
gettydefs(4) -- speed and terminal settings used by getty
|
|
The /etc/gettydefs file contains information used by getty to set up the speed and terminal settings for a line (see getty(1M)). It supplies information on what the login prompt should look like. It also supplies the speed to try next if the user indicates the current speed is not correct by typing a Break character. Each entry in /etc/gettydefs has the following format: label# # initial-flags # f... |
|
group(4) -- group file, grp.h
|
|
group contains for each group the following information: + group name + encrypted password + numerical group ID + comma-separated list of all users allowed in the group This is an ASCII file. Fields are separated by colons, and each group is separated from the next by a new-line. No spaces should separate the fields or parts of fields on any line. If the password field is null, no password is asso... |
|
hosts(4) -- host name data base
|
|
The file /etc/hosts associates Internet (IP) addresses with official host names and aliases. This allows a user to refer to a host by a symbolic name instead of an Internet address. Note: This file must contain all addresses for local interfaces that ifconfig needs at boot time (see ifconfig(1M)). When using the name server (see named(1M)), or Network Information Service (see ypserv(1M)), this fil... |
|
hosts.equiv(4) -- security files authorizing access by remote hosts and users on local host
|
|
The /etc/hosts.equiv file and files named .rhosts found in users' home directories specify remote hosts and users that are "equivalent" to the local host or user. Users from equivalent remote hosts are permitted to access a local account using rcp or remsh or to rlogin to the local account without supplying a password (see rcp(1), remsh(1), and rlogin(1)). The security provided by hosts.equiv i... |
|
inetd.conf(4) -- configuration file for inetd
|
|
On invocation, the inetd daemon reads its configuration information from the /etc/inetd.conf configuration file, and possibly at some later time in response to a SIGHUP signal (see inetd(1M)). Each line in the file is treated either as a comment or as configuration information for a given service Comments are denoted by a # at the beginning of a line. Noncomment lines contain seven or nine require... |
|
inetd.sec(4) -- optional security file for inetd
|
|
When inetd accepts a connection from a remote system, it checks the address of the host requesting the service against the list of hosts to be allowed or denied access to the specific service (see inetd(1M)). The file inetd.sec allows the system administrator to control which hosts (or networks in general) are allowed to use the system remotely. This file constitutes an extra layer of security in ... |
|
inetsvcs.conf(4) -- configuration file for secure internet services
|
|
The internet services, ftp, rcp, remsh, rlogin and telnet, use the /etc/inetsvcs.conf configuration file to decide their behavior (i.e., whether to allow network authentication using Kerberos V5 or not). The contents of the file decide whether the secure internet services are to be enabled or not. This configuration file is updated by the program inetsvcs_sec. The default entry in the file is as f... |
|
info(4) -- diskless client configuration information file
|
|
The info file is a POSIX shell sourceable file which contains parameter definitions used at boot time. Typically, it will be an empty file and default values will be used for all parameters. Following is the list of parameters which can be defined in the info file: ROOT_SERVER_IP Specifies the IP address of the client's private root server. If this is not specified, the client's private root ser... |
|
inittab(4) -- script for the boot init process
|
|
The /etc/inittab file supplies the script to the boot init daemon in its role as a general process dispatcher (see init(1M)). The process that constitutes the majority of boot init's process dispatching activities is the line process /usr/sbin/getty that initiates individual terminal lines. Other processes typically dispatched by boot init are daemons and shells. The inittab file is composed of e... |
|
inode_vxfs(4) -- format of a VxFS file system inode
|
|
A VxFS inode is typically 256 bytes in length, but an inode can also be 512 bytes. You specify the inode size with mkfs. An inode entry has the following format: i_mode The mode and type of file. i_nlink The number of links to the file. i_uid The inode owner. i_gid The inode group. i_size The size in bytes of the file. Eight bytes are allocated. i_atime Time of last access, in struct timeval forma... |
|
intro(4) -- introduction to file formats
|
|
This section outlines the formats of various files. The C struct declarations for the file formats are given where applicable. Usually, these structures can be found in directories /usr/include or /usr/include/sys. |
