Lines 93-100
This section covers the basics of configuring inetd.
Link Here
|
93 |
|
93 |
|
94 |
Configuration of inetd is done by editing [.filename]#/etc/inetd.conf#. |
94 |
Configuration of inetd is done by editing [.filename]#/etc/inetd.conf#. |
95 |
Each line of this configuration file represents an application which can be started by inetd. |
95 |
Each line of this configuration file represents an application which can be started by inetd. |
96 |
By default, every line starts with a comment (`#`), meaning that inetd is not listening for any applications. |
96 |
By default, every line starts with a comment (`+#+`), meaning that inetd is not listening for any applications. |
97 |
To configure inetd to listen for an application's connections, remove the `#` at the beginning of the line for that application. |
97 |
To configure inetd to listen for an application's connections, remove the `+#+` at the beginning of the line for that application. |
98 |
|
98 |
|
99 |
After saving your edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#: |
99 |
After saving your edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#: |
100 |
|
100 |
|
Lines 124-130
Once inetd is started, it needs to be notified whenever a modification is made t
Link Here
|
124 |
|
124 |
|
125 |
==== |
125 |
==== |
126 |
|
126 |
|
127 |
Typically, the default entry for an application does not need to be edited beyond removing the `#`. |
127 |
Typically, the default entry for an application does not need to be edited beyond removing the `+#+`. |
128 |
In some situations, it may be appropriate to edit the default entry. |
128 |
In some situations, it may be appropriate to edit the default entry. |
129 |
|
129 |
|
130 |
As an example, this is the default entry for man:ftpd[8] over IPv4: |
130 |
As an example, this is the default entry for man:ftpd[8] over IPv4: |
Lines 760-766
ellington has been setup as an YP master server without any errors.
Link Here
|
760 |
|
760 |
|
761 |
This will create [.filename]#/var/yp/Makefile# from [.filename]#/var/yp/Makefile.dist#. |
761 |
This will create [.filename]#/var/yp/Makefile# from [.filename]#/var/yp/Makefile.dist#. |
762 |
By default, this file assumes that the environment has a single NIS server with only FreeBSD clients. |
762 |
By default, this file assumes that the environment has a single NIS server with only FreeBSD clients. |
763 |
Since `test-domain` has a slave server, edit this line in [.filename]#/var/yp/Makefile# so that it begins with a comment (`#`): |
763 |
Since `test-domain` has a slave server, edit this line in [.filename]#/var/yp/Makefile# so that it begins with a comment (`+#+`): |
764 |
|
764 |
|
765 |
[.programlisting] |
765 |
[.programlisting] |
766 |
.... |
766 |
.... |
Lines 922-928
Since RPC is a broadcast-based service, any system running ypbind within the sam
Link Here
|
922 |
To prevent unauthorized transactions, man:ypserv[8] supports a feature called "securenets" which can be used to restrict access to a given set of hosts. |
922 |
To prevent unauthorized transactions, man:ypserv[8] supports a feature called "securenets" which can be used to restrict access to a given set of hosts. |
923 |
By default, this information is stored in [.filename]#/var/yp/securenets#, unless man:ypserv[8] is started with `-p` and an alternate path. |
923 |
By default, this information is stored in [.filename]#/var/yp/securenets#, unless man:ypserv[8] is started with `-p` and an alternate path. |
924 |
This file contains entries that consist of a network specification and a network mask separated by white space. |
924 |
This file contains entries that consist of a network specification and a network mask separated by white space. |
925 |
Lines starting with `#` are considered to be comments. |
925 |
Lines starting with `+#+` are considered to be comments. |
926 |
A sample [.filename]#securenets# might look like this: |
926 |
A sample [.filename]#securenets# might look like this: |
927 |
|
927 |
|
928 |
[.programlisting] |
928 |
[.programlisting] |
Lines 2017-2023
For more detailed information about Apache 2.X and its configuration directives,
Link Here
|
2017 |
=== Configuring and Starting Apache |
2017 |
=== Configuring and Starting Apache |
2018 |
|
2018 |
|
2019 |
In FreeBSD, the main Apache HTTP Server configuration file is installed as [.filename]#/usr/local/etc/apache2x/httpd.conf#, where _x_ represents the version number. |
2019 |
In FreeBSD, the main Apache HTTP Server configuration file is installed as [.filename]#/usr/local/etc/apache2x/httpd.conf#, where _x_ represents the version number. |
2020 |
This ASCII text file begins comment lines with a `#`. |
2020 |
This ASCII text file begins comment lines with a `+#+`. |
2021 |
The most frequently modified directives are: |
2021 |
The most frequently modified directives are: |
2022 |
|
2022 |
|
2023 |
`ServerRoot "/usr/local"`:: |
2023 |
`ServerRoot "/usr/local"`:: |