|
Lines 267-273
Link Here
|
| 267 |
</sect2> |
267 |
</sect2> |
| 268 |
|
268 |
|
| 269 |
<sect2 id="network-inetd-conf"> |
269 |
<sect2 id="network-inetd-conf"> |
| 270 |
<!-- XXX This section isn't very clear, and could do with some lovin' --> |
270 |
<!-- XXX This section is not very clear and could do with some tlc --> |
| 271 |
<title><filename>inetd.conf</filename></title> |
271 |
<title><filename>inetd.conf</filename></title> |
| 272 |
|
272 |
|
| 273 |
<para>Configuration of <application>inetd</application> is |
273 |
<para>Configuration of <application>inetd</application> is |
|
Lines 819-838
Link Here
|
| 819 |
<para>Please refer to <xref linkend="configtuning-rcd"/> for |
819 |
<para>Please refer to <xref linkend="configtuning-rcd"/> for |
| 820 |
more information about using rc scripts.</para> |
820 |
more information about using rc scripts.</para> |
| 821 |
|
821 |
|
| 822 |
<para>Alternatively, a reboot will make FreeBSD set everything |
822 |
<para>NFS services can now be started by running the following |
| 823 |
up properly. A reboot is not necessary though. |
823 |
command, on the <acronym>NFS</acronym> server, as |
| 824 |
Executing the following commands as <username>root</username> |
824 |
<username>root</username>:</para> |
| 825 |
should start everything up.</para> |
|
|
| 826 |
|
825 |
|
| 827 |
<para>On the <acronym>NFS</acronym> server:</para> |
826 |
<screen>&prompt.root; <userinput>service nfsd start</userinput></screen> |
| 828 |
|
827 |
|
| 829 |
<screen>&prompt.root; <userinput>rpcbind</userinput> |
|
|
| 830 |
&prompt.root; <userinput>nfsd -u -t -n 4</userinput> |
| 831 |
&prompt.root; <userinput>mountd -r</userinput></screen> |
| 832 |
|
| 833 |
<para>On the <acronym>NFS</acronym> client:</para> |
828 |
<para>On the <acronym>NFS</acronym> client:</para> |
| 834 |
|
829 |
|
| 835 |
<screen>&prompt.root; <userinput>nfsiod -n 4</userinput></screen> |
830 |
<screen>&prompt.root; <userinput>service nfsclient restart</userinput></screen> |
| 836 |
|
831 |
|
| 837 |
<para>Now everything should be ready to actually mount a remote |
832 |
<para>Now everything should be ready to actually mount a remote |
| 838 |
file system. In these examples the server's name will be |
833 |
file system. In these examples the server's name will be |
|
Lines 1609-1615
Link Here
|
| 1609 |
good reason, never propagate passwords for |
1604 |
good reason, never propagate passwords for |
| 1610 |
<username>root</username> and other administrative |
1605 |
<username>root</username> and other administrative |
| 1611 |
accounts to all the servers in the NIS domain. Therefore, |
1606 |
accounts to all the servers in the NIS domain. Therefore, |
| 1612 |
before the the NIS maps are initialized, configure the |
1607 |
before the NIS maps are initialized, configure the |
| 1613 |
primary password files:</para> |
1608 |
primary password files:</para> |
| 1614 |
|
1609 |
|
| 1615 |
<screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput> |
1610 |
<screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput> |
|
Lines 1649-1655
Link Here
|
| 1649 |
Questions will all be asked at the beginning of the procedure. |
1644 |
Questions will all be asked at the beginning of the procedure. |
| 1650 |
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput> |
1645 |
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput> |
| 1651 |
Ok, please remember to go back and redo manually whatever fails. |
1646 |
Ok, please remember to go back and redo manually whatever fails. |
| 1652 |
If you don't, something might not work. |
1647 |
If not, something might not work. |
| 1653 |
At this point, we have to construct a list of this domains YP servers. |
1648 |
At this point, we have to construct a list of this domains YP servers. |
| 1654 |
rod.darktech.org is already known as master server. |
1649 |
rod.darktech.org is already known as master server. |
| 1655 |
Please continue to add any slave servers, one per line. When you are |
1650 |
Please continue to add any slave servers, one per line. When you are |
|
Lines 1711-1717
Link Here
|
| 1711 |
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput> |
1706 |
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput> |
| 1712 |
|
1707 |
|
| 1713 |
Ok, please remember to go back and redo manually whatever fails. |
1708 |
Ok, please remember to go back and redo manually whatever fails. |
| 1714 |
If you don't, something might not work. |
1709 |
If not, something might not work. |
| 1715 |
There will be no further questions. The remainder of the procedure |
1710 |
There will be no further questions. The remainder of the procedure |
| 1716 |
should take a few minutes, to copy the databases from ellington. |
1711 |
should take a few minutes, to copy the databases from ellington. |
| 1717 |
Transferring netgroup... |
1712 |
Transferring netgroup... |
|
Lines 1756-1762
Link Here
|
| 1756 |
ypxfr: Exiting: Map successfully transferred |
1751 |
ypxfr: Exiting: Map successfully transferred |
| 1757 |
|
1752 |
|
| 1758 |
coltrane has been setup as an YP slave server without any errors. |
1753 |
coltrane has been setup as an YP slave server without any errors. |
| 1759 |
Don't forget to update map ypservers on ellington.</screen> |
1754 |
Remember to update map ypservers on ellington.</screen> |
| 1760 |
|
1755 |
|
| 1761 |
<para>There should be a directory called |
1756 |
<para>There should be a directory called |
| 1762 |
<filename>/var/yp/test-domain</filename>. Copies of the |
1757 |
<filename>/var/yp/test-domain</filename>. Copies of the |