This chapter describes most of the parameters for setting default values for various system facilities.
The functioning of various system facilities is governed by a set of values that are read by the facility on startup. The values stored in a file for each facility are located in the /etc/default directory. Not every system facility has a file located in this directory.
For details, see the Setting cron Defaults section of cron(1M).
This file is not currently used.
Client usage of DHCP is provided by the dhcpagent daemon. When ifconfig identifies an interface that has been configured to receive its network configuration from DHCP, it starts the client daemon to manage that interface.
For more information, see the /etc/default/dhcpagent information in the FILES section of dhcpagent(1M).
File system administrative commands have a generic and file system-specific portion. If the file system type is not explicitly specified with the -F option, a default is applied. The value is specified in this file. For more information, see the Description section of default_fs(4).
For details, see the /etc/default/inetd information in the FILES section of inetd(1M), /etc/default/inetd.
Used by the /etc/rc2.d/S69inet script to control the sequence numbers used by TCP.
For details, see the /etc/default/init section of init(1M).
The CMASK variable referred to in the file is not documented in the man page. CMASK is the umask that init uses and that every process inherits from the init process. If not set, init uses the default umask it obtains from the kernel. The init process always attempt to apply a umask of 022 before creating any files, regardless of the setting of CMASK. All values in the file are placed in the environment of the shell that init invokes in response to a single user boot request. The init process also passes these values to any commands that it starts or restarts from the /etc/inittab file.
For details, see the /etc/default/keyserv information in the FILES section of keyserv(1M).
For details, see the Extended Description section of kbd(1).
For details, see the /etc/default/login information in the FILES section of login(1).
For details, see the Description section of nfslogd(1M).
For details, see the /etc/default/passwd information in the FILES section of passwd(1), /etc/default/passwd.
For details, see the /etc/default/power information in the FILES section of pmconfig(1M).
For details, see the /etc/default/rpc.nisd information in the FILES section of rpc.nisd(1M).
For details, see the /etc/default/su information in the FILES section of su(1M).
For details, see the /etc/default/syslogd information in the FILES section of syslogd(1M).
For details, see the /etc/default/sys-suspend information in the FILES section of sys-suspend(1M).
For a description of the -f function modifier, see tar(1).
If the TAPE environment variable is not present and the value of one of the arguments is a number and -f is not specified, the number matching the archiveN string is looked up in the /etc/default/tar file. The value of the archiveN string is used as the output device with the blocking and size specifications from the file.
For example:
% tar -c 2 /tmp/* |
Writes the output to the device specified as archive2 in the /etc/default/tar file.
The utmpd daemon monitors /var/adm/utmpx (and /var/adm/utmp in earlier versions of Solaris) to ensure that utmp entries inserted by non-root processes by pututxline(3C) are cleaned up on process termination.
Two entries in /etc/default/utmpd are supported:
SCAN_PERIOD - The number of seconds that utmpd sleeps between checks of /proc to see if monitored processes are still alive. The default is 300.
MAX_FDS - The maximum number of processes that utmpd attempts to monitor. The default value is 4096 and should never need to be changed.