Партнёры:
Хостинг:
rc.conf - system configuration information
The purpose of is not to run commands or perform system startup actions directly. Instead, it is included by the various generic startup scripts in /etc which conditionalize their internal actions according to the settings found there.
The /etc/rc.conf file is included from the file /etc/defaults/rc.conf which specifies the default settings for all the available options. Options need only be specified in /etc/rc.conf when the system administrator wishes to override these defaults. The file /etc/rc.conf.local is used to override settings in /etc/rc.conf for historical reasons. See the rc_conf_files variable below.
Options are set with ``name = value '' assignments that use sh(1) syntax. The following list provides a name and short description for each variable that can be set in the file:
If a filename is specified, the full path must be given.
Typical usage will require putting
ipfilter_enable="YES" ipnat_enable="YES" ipmon_enable="YES" ipfs_enable="YES"
into /etc/rc.conf and editing /etc/ipf.rules and /etc/ipnat.rules appropriately.
Note that ipfilter_enable and ipnat_enable can be enabled independently. ipmon_enable and ipfs_enable both require at least one of ipfilter_enable and ipnat_enable to be enabled.
Having
options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK
in the kernel configuration file is a good idea, too.
/var/log/ipflog 640 10 100 * Z /var/run/ipmon.pid
Typical usage will require putting
pf_enable="YES"
into /etc/rc.conf and editing /etc/pf.conf appropriately. Adding
"device pf"
builds support for pf(4) into the kernel, otherwise the kernel module will be loaded.
An ifconfig_ Aq interface variable is also assumed to exist for each value of interface When an interface name contains any of the characters ``.-/+ '' they are translated to ``_ '' before lookup. The variable can contain arguments to ifconfig(8), as well as special case-insensitive keywords described below. Such keywords are removed before passing the value to ifconfig(8) while the order of the other arguments is preserved.
One can configure more than one IPv4 address with the ipv4_addrs_ Aq interface variable. One or more IP addresses must be provided in Classless Inter-Domain Routing (CIDR) address notation, whose last byte can be a range like 192.168.0.5-23/24. In this case the address 192.168.0.5 will be configured with the netmask /24 and the addresses 192.168.0.6 to 192.168.0.23 with the non-conflicting netmask /32 as explained in the ifconfig(8) alias section. With the interface in question being ed0 an example could look like:
ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28"
It is also possible to add IP alias entries using ifconfig(8) syntax. Assuming that the interface in question was ed0 it might look something like this:
ifconfig_ed0_alias0="inet 127.0.0.253 netmask 0xffffffff" ifconfig_ed0_alias1="inet 127.0.0.254 netmask 0xffffffff"
And so on. For each ifconfig_ Ao interface Ac _alias Aq n entry that is found, its contents are passed to ifconfig(8). Execution stops at the first unsuccessful access, so if something like this is present:
ifconfig_ed0_alias0="inet 127.0.0.251 netmask 0xffffffff" ifconfig_ed0_alias1="inet 127.0.0.252 netmask 0xffffffff" ifconfig_ed0_alias2="inet 127.0.0.253 netmask 0xffffffff" ifconfig_ed0_alias4="inet 127.0.0.254 netmask 0xffffffff"
Then note that alias4 would not be added since the search would stop with the missing ``alias3 '' entry. Due to this difficult to manage behavior, the ifconfig_ Ao interface Ac _alias Aq n form is deprecated.
If the /etc/start_if. Aq interface file is present, it is read and executed by the sh(1) interpreter before configuring the interface as specified in the ifconfig_ Aq interface and ifconfig_ Ao interface Ac _alias Aq n variables.
If the ifconfig_ Aq interface contains the keyword ``NOAUTO '' then the interface will not be configured at boot or by /etc/pccard_ether when network_interfaces is set to ``AUTO ''
It is possible to bring up an interface with DHCP by adding ``DHCP '' to the ifconfig_ Aq interface variable. For instance, to initialize the ed0 device via DHCP, it is possible to use something like:
ifconfig_ed0="DHCP"
Also, if your interface needs WPA authentication, it is possible to add ``WPA '' to the ifconfig_ Aq interface variable.
Finally, you can add ifconfig(8) options in this variable, in addition to the /etc/start_if. Aq interface file. For instance, to initialize the wi0 device via DHCP, using WPA authentication and 802.11b mode, it is possible to use something like:
ifconfig_wi0="DHCP WPA mode 11b"
In addition to the ifconfig_ Aq interface form, a fallback variable ifconfig_DEFAULT may be configured. It will be used for all interfaces with no ifconfig_ Aq interface variable. This is intended to replace the no longer supported pccard_ifconfig variable.
It is also possible to rename interface by doing:
ifconfig_ed0_name="net0" ifconfig_net0="inet 10.0.0.1 netmask 0xffff0000"
fec_interfaces="fec0" fecconfig_fec0="em0 em1" ifconfig_fec0="DHCP"
The lockfile for each individual gbde(4) device can be overridden by setting the variable gbde_lock_ Aq device where device is the encrypted device without the ``/dev/ '' and ``.bde '' parts.
"0 4 * * * root /etc/rc.d/bgfsck forcestart"
to /etc/crontab
static_routes="mcast gif0local" route_mcast="-net 224.0.0.0/4 -iface gif0" route_gif0local="-host 169.254.1.1 -iface lo0"
Note that multicast routing daemons are no longer included in the Fx base system, however, both mrouted(8) and pim6dd(8) may be installed from the Fx Ports Collection.
If the mouse is attached to the PS/2 mouse port, choose ``auto '' or ``ps/2 '' regardless of the brand and model of the mouse. Likewise, if the mouse is attached to the bus mouse port, choose ``auto '' or ``busmouse '' All other protocols are for serial mice and will not work with the PS/2 and bus mice. If this is a USB mouse, ``auto '' is the only protocol type which will work.
Even if the mouse is not in the above list, it may be compatible with one in the list. Refer to the manual page for moused(8) for compatibility information.
It should also be noted that while this is enabled, any other client of the mouse (such as an X server) should access the mouse through the virtual mouse device, /dev/sysmouse and configure it as a ``sysmouse '' type mouse, since all mouse data is converted to this single canonical format when using moused(8). If the client program does not support the ``sysmouse '' type, specify the ``mousesystems '' type. It is the second preferred type.
jail_vjail_hostname="jail.example.com" jail_vjail_ip="192.168.1.100" jail_vjail_rootdir="/var/jails/vjail/root"
mdconfig_md0_cmd="tar xfzC /var/file.tgz \${_mp}"
autobridge_interfaces="bridge0" autobridge_bridge0="tap* dc0 vlan[345]"
|
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |