This commit is contained in:
gferg 2001-03-25 21:55:14 +00:00
parent a610645b6a
commit f50eba91c5
1 changed files with 48 additions and 13 deletions

View File

@ -1,3 +1,5 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
]>
<article>
@ -138,8 +140,8 @@ located at the LDP Home Page.
</para>
<para>
Postings on the Usenet News groups, including the FAQ, are archived on
<ulink url="http://www.deja.com/usenet/">
<literal>http://www.deja.com/usenet/</literal></ulink>. Search for
<ulink url="http://groups.google.com/">
<literal>http://groups.google.com/</literal></ulink>. Search for
``<literal>comp.os.linux.*</literal>,''
``<literal>alt.uu.comp.os.linux.*</literal>, or whatever is
appropriate, to retrieve articles from the Linux News groups.
@ -3732,11 +3734,19 @@ client, but there is a Java client at
<title>Solutions to Common Miscellaneous Problems</title>
<sect2 label="7.1">
<title id="ppp-connection-dies-when-sending">
File Transfers over PPP Connections Seem to Hang.</title>
FTP Transfers Seem to Hang.</title>
<para>
This is due, apparently, to some form of buffer overrun. It occurs
both with Linux and Microsoft servers. On Linux systems, The problem
seems to occur most commonly with the distribution's server software.
FTP transfers that die suddenly are due, apparently, to some form of
overrunning buffer. It occurs both with Linux and Microsoft servers.
On Linux systems, The problem seems to occur most commonly with the
distribution's server software.
</para>
<para>
If you receive
<literal>ftp: connection refused</literal> errors, then the problem
is likely due to a lack of authentication. Refer to
``<xref linkend="ftp-wont-login"
endterm="ftp-wont-login">.''
</para>
<para>
One remedy is to be replacing the distribution FTP server with the
@ -3747,7 +3757,8 @@ Linux port of the OpenBSD FTP server. The home page is:
<para>
To install the BSD server, follow the installation instructions, and
refer to the manual pages for <filename>inetd</filename> and
<filename>inetd.conf</filename>. Be sure to tell
<filename>inetd.conf</filename>. (If you have the newer
<filename>xinetd</filename>, see below.) Be sure to tell
<filename>inetd</filename> to run the BSD daemon alone, not as a
subprocess of, for example, <filename>tcpd</filename>. Comment
out the line that begins ``<literal>ftp</literal>'' in the
@ -3772,6 +3783,18 @@ or sending (as root) a <literal>SIGHUP</literal> to
<para><screen>
# kill -HUP inetd
</screen></para>
<para>
To configure <filename>xinetd</filename>, create an entry in
<filename>/etc/xinetd.d</filename> per the instructions in the
<filename>xinetd.conf</filename> manual page. Make sure,
again, that the command-line arguments for <filename>ftpd</filename>
are correct, and that you have installed the <filename>/etc/ftpusers</filename>
and <filename>/etc/pam.d/ftp</filename> files. Then restart
<filename>xinetd</filename> with the command:
<literal>/etc/rc.d/init.d/xinetd restart</literal>. The command
should report ``OK,'' and the restart will be noted in the
system message log.
</para>
</sect2>
<sect2 label="7.2">
@ -3868,13 +3891,13 @@ addresses using it.
<para>
If the host machine doesn't respond to FTP or Telnet clients at all,
then the server daemon is not installed correctly, or at all. Refer
to the manual pages: <literal>inetd</literal>,
<literal>inetd.conf</literal>, <literal>ftpd</literal>, and
<literal>telnetd</literal>.
to the manual pages: <literal>inetd</literal> and
<literal>inetd.conf</literal> on older systems, or
<literal>xinetd</literal> and <literal>xinetd.conf</literal>, as well
as <literal>ftpd</literal>, and <literal>telnetd</literal>.
</para>
</sect2>
<sect2 label="7.5">
<title id="track-of-bookmarks-netscape">
How Do I Keep Track of All My Bookmarks in Netscape?</title>
@ -4331,7 +4354,7 @@ something like that. Get a recent version.
<title id="lilo-boot-kernel-image">
How Do I Get LILO to Boot the Kernel Image?</title>
<para>
From kernel versions 1.1.80 on, the compressed kernel image, which is
>From kernel versions 1.1.80 on, the compressed kernel image, which is
what LILO needs to find, is in <filename>arch/i386/boot/zImage</filename>, or
<filename>arch/i386/boot/bzImage</filename> when it is built,
and is normally stored in the
@ -6997,7 +7020,7 @@ Pluggable Authentication Modules library, in which case there should
be an authorization file <filename>/etc/pam.d/ftp</filename>. A
generic authorization file looks like this. (The line break on the
first ``auth'' line is for readability. The entry is actually a single,
long line:)
long line).
</para>
<para><screen>
#%PAM-1.0
@ -7012,6 +7035,12 @@ long line:)
Also, make sure the <filename>/etc/ftpusers</filename> file, or whatever
users file is named in the first ``auth'' line, is configured correctly.
</para>
<para>
Btw, the sample <filename>ftp</filename> file above is actually
the<filename>ftpd/ftp.pam.sample</filename> file from the
<filename>ftpd-BSD-0.3.1.tar.gz</filename> package. Many thanks
to David A. Madore for this much needed port.
</para>
</sect2>
</sect1>
@ -7578,3 +7607,9 @@ as educators and learners.
</sect1>
</article>
___________________________________
thanks for submitting into linuxdoc