1.\" $OpenBSD: intro.8,v 1.22 2014/03/13 10:12:11 florian Exp $ 2.\" $NetBSD: intro.8,v 1.3 1994/11/30 19:36:24 jtc Exp $ 3.\" 4.\" Copyright (c) 1983, 1991, 1993 5.\" The Regents of the University of California. All rights reserved. 6.\" 7.\" Redistribution and use in source and binary forms, with or without 8.\" modification, are permitted provided that the following conditions 9.\" are met: 10.\" 1. Redistributions of source code must retain the above copyright 11.\" notice, this list of conditions and the following disclaimer. 12.\" 2. Redistributions in binary form must reproduce the above copyright 13.\" notice, this list of conditions and the following disclaimer in the 14.\" documentation and/or other materials provided with the distribution. 15.\" 3. Neither the name of the University nor the names of its contributors 16.\" may be used to endorse or promote products derived from this software 17.\" without specific prior written permission. 18.\" 19.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 22.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 29.\" SUCH DAMAGE. 30.\" 31.\" @(#)intro.8 8.2 (Berkeley) 12/11/93 32.\" 33.Dd $Mdocdate: March 13 2014 $ 34.Dt INTRO 8 35.Os 36.Sh NAME 37.Nm intro 38.Nd introduction to system maintenance and operation commands 39.Sh DESCRIPTION 40The manual pages in section 8 contain information related to 41system operation and maintenance. 42They describe commands concerning file systems, 43such as 44.Xr edquota 8 , 45.Xr fsck 8 , 46.Xr mount 8 , 47and 48.Xr newfs 8 . 49They also cover commands concerning system backup/recovery, such as 50.Xr dump 8 51and 52.Xr restore 8 . 53.Pp 54There are pages which document the running of the system, such as 55.Xr afterboot 8 , 56.Xr ifconfig 8 , 57.Xr security 8 , 58and the configuration files located in 59.Pa /etc . 60Procedures concerning system failure are documented in 61.Xr crash 8 . 62.Pp 63Section 8 pages also describe network services and daemons. 64The rest of this page discusses some of the main daemons 65available on the 66.Ox 67system, 68and how to enable/disable them. 69.Pp 70System daemons are controlled by the script 71.Xr rc 8 , 72which is in turn configured by 73.Xr rc.conf 8 . 74For example the HTTP daemon 75.Xr nginx 8 76is controlled by the following line from 77.Xr rc.conf 8 : 78.Bd -literal -offset indent 79nginx_flags=NO 80.Ed 81.Pp 82Thus it is not started by default. 83To enable or disable daemon processes, 84administrators should edit the file 85.Xr rc.conf.local 8 , 86which overrides 87.Xr rc.conf 8 . 88So to enable 89.Xr nginx 8 , 90the following line might be added to 91.Pa /etc/rc.conf.local : 92.Bd -literal -offset indent 93nginx_flags="" 94.Ed 95or 96.Bd -literal -offset indent -compact 97nginx_flags="-u" 98.Ed 99.Pp 100As can be seen above, 101this method is also used to specify additional options. 102.Pp 103Below is a list of some of the daemons available. 104For further information, see 105.Xr rc 8 106and the individual pages for the utilities. 107.Ss Automounter daemon (amd) 108If using the 109.Xr amd 8 110package, 111go into the 112.Pa /etc/amd 113directory and set it up by 114renaming 115.Pa master.sample 116to 117.Pa master 118and editing it and creating other maps as needed. 119Alternatively, you can get your maps with YP. 120.Pp 121Relevant 122.Xr rc.conf 8 123variables: 124.Va amd_flags 125and 126.Va amd_master . 127.Ss BIND name server (DNS) 128If you are using the BIND name server, check the 129.Pa /etc/resolv.conf 130file. 131It may look something like: 132.Bd -literal -offset indent 133domain nts.umn.edu 134nameserver 128.101.101.101 135nameserver 134.84.84.84 136search nts.umn.edu. umn.edu. 137lookup file bind 138.Ed 139.Pp 140If using a caching name server, add the line "nameserver 127.0.0.1" first. 141.Pp 142Relevant 143.Xr rc.conf 8 144variables: 145.Va named_flags . 146.Ss Clock synchronisation 147In order to make sure the system clock is correct, 148it may be synchronised with a number of external sources. 149The utilities available are: 150.Xr ntpd 8 151and 152.Xr rdate 8 . 153.Pp 154Relevant 155.Xr rc.conf 8 156variables: 157.Va ntpd_flags . 158.Ss BOOTP/DHCP server 159If this is a 160BOOTP or DHCP 161server, edit 162.Pa /etc/dhcpd.conf 163as needed. 164See also 165.Xr diskless 8 . 166.Pp 167Relevant 168.Xr rc.conf 8 169variables: 170.Va bootparamd_flags , 171.Va dhcpd_flags , 172and 173.Va dhcrelay_flags . 174.Ss HP remote boot server 175Edit 176.Pa /etc/rbootd.conf 177if needed for remote booting. 178If you do not have HP computers doing remote booting, do not enable this. 179See also 180.Xr diskless 8 . 181.Pp 182Relevant 183.Xr rc.conf 8 184variables: 185.Va rbootd_flags . 186.Ss Kerberos 187If you are going to use 188.Xr kerberos 8 189for authentication, and you already have a 190Kerberos 191master, change directory to 192.Pa /etc/kerberosV 193and configure. 194Remember to get a 195.Pa keytab 196from the master so that the remote commands work. 197.Pp 198Relevant 199.Xr rc.conf 8 200variables: 201.Va kdc_flags , 202.Va kadmind_flags , 203and 204.Va kpasswdd_flags . 205.Ss nginx web server (HTTP) 206On 207.Ox 208it will 209.Xr chroot 2 210to 211.Pa /var/www . 212Detailed information is available in 213.Xr nginx 8 214and 215.Xr nginx.conf 5 . 216.Pp 217Relevant 218.Xr rc.conf 8 219variables: 220.Va nginx_flags . 221.Ss NFS server 222If this is an NFS server, 223edit 224.Pa /etc/exports . 225.Pp 226Relevant 227.Xr rc.conf 8 228variables: 229.Va mountd_flags 230and 231.Va nfsd_flags . 232.Ss Relay Daemon 233A relay daemon, 234.Xr relayd 8 , 235able to run as a 236load-balancer, application layer gateway, or transparent proxy. 237.Pp 238Relevant 239.Xr rc.conf 8 240variables: 241.Va relayd_flags . 242.Ss Routing Daemons 243Various daemons for managing routing tables are available: 244.Xr bgpd 8 , 245.Xr ospfd 8 , 246and 247.Xr ripd 8 . 248.Pp 249Relevant 250.Xr rc.conf 8 251variables: 252.Va bgpd_flags , 253.Va ospfd_flags , 254and 255.Va ripd_flags . 256.Ss RPC-based network services 257Several services depend on the RPC portmapper, 258.Xr portmap 8 , 259being running for proper operation. 260This includes YP and NFS exports, among other services. 261.Pp 262Relevant 263.Xr rc.conf 8 264variables: 265.Va portmap_flags . 266.Ss YP setup 267Check the YP domain name with the 268.Xr domainname 1 269command. 270If necessary, correct it by editing the 271.Pa /etc/defaultdomain 272file (see 273.Xr defaultdomain 5 ) . 274The 275.Pa /etc/netstart 276script reads this file on boot to determine and set the domain name. 277You may also set the running system's domain name with the 278.Xr domainname 1 279command. 280.Pp 281Relevant 282.Xr rc.conf 8 283variables: 284.Va ypbind_flags . 285.Pp 286After starting YP client services, perform the remaining YP activation 287as described in 288.Xr passwd 5 289and 290.Xr group 5 . 291.Pp 292In particular, to enable YP passwd support, you'll need to add the following 293line to 294.Pa /etc/master.passwd : 295.Pp 296.Dl +:*:::::::: 297.Pp 298You do this by using 299.Xr vipw 8 . 300.Pp 301There are many more YP man pages available to help you. 302You can find more information by starting with 303.Xr yp 8 . 304.Sh SEE ALSO 305.Xr afterboot 8 , 306.Xr rc 8 , 307.Xr rc.conf 8 308.Sh HISTORY 309The 310.Nm intro 311section manual page appeared in 312.Bx 4.2 . 313