Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Mar 2008 03:30:30 GMT
From:      Gabor Pali <pgj@FreeBSD.org>
To:        Perforce Change Reviews <perforce@FreeBSD.org>
Subject:   PERFORCE change 137766 for review
Message-ID:  <200803150330.m2F3UURb070125@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=137766

Change 137766 by pgj@disznohal on 2008/03/15 03:30:26

	Add initial Hungarian translation of Chapter 27: Network Servers.

Affected files ...

.. //depot/projects/docproj_hu/books/handbook/network-servers/chapter.sgml#3 edit

Differences ...

==== //depot/projects/docproj_hu/books/handbook/network-servers/chapter.sgml#3 (text+ko) ====

@@ -4,90 +4,115 @@
      $FreeBSD: doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v 1.102 2007/11/28 21:26:59 remko Exp $
 -->
 
-<chapter id="network-servers">
+<!-- The FreeBSD Hungarian Documentation Project
+     Translated by: PALI, Gabor <pgj@FreeBSD.org>
+     Original Revision: 1.102                     -->
+
+<chapter id="network-servers" lang="hu">
   <chapterinfo>
     <authorgroup>
       <author>
-        <firstname>Murray</firstname>
+	<firstname>Murray</firstname>
 	<surname>Stokely</surname>
-	<contrib>Reorganized by </contrib>
+	<contrib>&Uacute;jraszervezte: </contrib>
       </author>
     </authorgroup>
-    <!-- 23 July 2004 -->
   </chapterinfo>
 
-  <title>Network Servers</title>
+  <title>H&aacute;l&oacute;zati szerverek</title>
 
   <sect1 id="network-servers-synopsis">
-    <title>Synopsis</title>
+    <title>&Aacute;ttekint&eacute;s</title>
 
-    <para>This chapter will cover some of the more frequently used
-      network services on &unix; systems.  We will cover how to
-      install, configure, test, and maintain many different types of
-      network services.  Example configuration files are included
-      throughout this chapter for you to benefit from.</para>
+    <para>Ebben a fejezetben a &unix; t&iacute;pus&uacute; rendszerekben
+      leggyakrabban alkalmazott h&aacute;l&oacute;zati
+      szolg&aacute;ltat&aacute;sok k&ouml;z&uuml;l fogunk
+      n&eacute;h&aacute;nyat bemutatni.  Ennek sor&aacute;n
+      megismerj&uuml;k a h&aacute;l&oacute;zati
+      szolg&aacute;ltat&aacute;sok k&uuml;l&ouml;nb&ouml;z&#245;
+      t&iacute;pusainak telep&iacute;t&eacute;s&eacute;t,
+      be&aacute;ll&iacute;t&aacute;s&aacute;t, tesztel&eacute;s&eacute;t
+      &eacute;s karbantart&aacute;s&aacute;t.  A fejezet
+      tartalm&aacute;t folyamatosan p&eacute;ld&aacute;kkal
+      igyeksz&uuml;nk illusztr&aacute;lni.</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>A fejezet elolvas&aacute;sa sor&aacute;n
+      megismerj&uuml;k:</para>
 
     <itemizedlist>
 
       <listitem>
-	<para>How to manage the <application>inetd</application>
-	  daemon.</para>
+	<para>hogyan dolgozzunk az <application>inetd</application>
+	  d&eacute;monnal</para>
       </listitem>
 
       <listitem>
-	<para>How to set up a network file system.</para>
+	<para>hogyan &aacute;ll&iacute;tsuk be a h&aacute;l&oacute;zati
+	  &aacute;llom&aacute;nyrendszereket</para>
       </listitem>
 
       <listitem>
-	<para>How to set up a network information server for sharing
-	  user accounts.</para>
+	<para>hogyan &aacute;ll&iacute;tsunk be egy
+	  h&aacute;l&oacute;zati inform&aacute;ci&oacute;s szervert a
+	  felhaszn&aacute;l&oacute;i hozz&aacute;f&eacute;r&eacute;sek
+	  megoszt&aacute;s&aacute;ra</para>
       </listitem>
 
       <listitem>
-	<para>How to set up automatic network settings using DHCP.</para>
+	<para>hogyan &aacute;ll&iacute;tsuk be automatikusan a
+	  h&aacute;l&oacute;zati hozz&aacute;f&eacute;r&eacute;s&uuml;nket
+	  a DHCP haszn&aacute;lat&aacute;val</para>
       </listitem>
 
       <listitem>
-	<para>How to set up a domain name server.</para>
+	<para>hogyan &aacute;ll&iacute;tsunk be n&eacute;vfelold&oacute;
+	  szervereket</para>
       </listitem>
 
       <listitem>
-	<para>How to set up the <application>Apache</application> HTTP Server.</para>
+	<para>hogyan &aacute;ll&iacute;tsuk be az
+	  <application>Apache</application> webszervert</para>
       </listitem>
 
       <listitem>
-	<para>How to set up a File Transfer Protocol (FTP) Server.</para>
+	<para>hogyan &aacute;ll&iacute;tsuk be az
+	&aacute;llom&aacute;nyok &aacute;tvitel&eacute;&eacute;rt
+	  felel&#245;s (FTP) szervert</para>
       </listitem>
 
       <listitem>
-	<para>How to set up a file and print server for &windows;
-	  clients using <application>Samba</application>.</para>
+	<para>a <application>Samba</application>
+	  haszn&aacute;lat&aacute;val hogyan &aacute;ll&iacute;tsunk be
+	  &windows;-os kliensek sz&aacute;m&aacute;ra
+	  &aacute;llom&aacute;ny- &eacute;s
+	  nyomtat&oacute;szervert</para>
       </listitem>
 
       <listitem>
-	<para>How to synchronize the time and date, and set up a
-	  time server, with the NTP protocol.</para>
+	<para>az NTP protokoll seg&iacute;ts&eacute;g&eacute;vel hogyan
+	  egyeztess&uuml;k az id&#245;t &eacute;s d&aacute;tumot, hogyan
+	  &aacute;ll&iacute;tsunk be egy id&#245;szervert</para>
       </listitem>
 
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>A fejezet elolvas&aacute;s&aacute;hoz aj&aacute;nlott:</para>
 
     <itemizedlist>
       <listitem>
-	<para>Understand the basics of the
-	  <filename>/etc/rc</filename> scripts.</para>
+	<para>az <filename>/etc/rc</filename> szkriptek alapjainak
+	  ismerete</para>
       </listitem>
 
       <listitem>
-	<para>Be familiar with basic network terminology.</para>
+	<para>az alapvet&#245; h&aacute;l&oacute;zati fogalmak
+	  ismerete</para>
       </listitem>
 
       <listitem>
-      <para>Know how to install additional third-party
-        software (<xref linkend="ports">).</para>
+	<para>a k&uuml;ls&#245; fejleszt&eacute;s&#251; szoftverek
+	  telep&iacute;t&eacute;s&eacute;nek ismerete (<xref
+	  linkend="ports">)</para>
       </listitem>
 
     </itemizedlist>
@@ -96,233 +121,298 @@
   <sect1 id="network-inetd">
     <sect1info>
       <authorgroup>
-        <author>
-          <firstname>Chern</firstname>
-          <surname>Lee</surname>
-          <contrib>Contributed by </contrib>
-        </author>
+	<author>
+	  <firstname>Chern</firstname>
+	  <surname>Lee</surname>
+	  <contrib>K&eacute;sz&iacute;tette: </contrib>
+	</author>
       </authorgroup>
       <authorgroup>
 	<author>
-	  <contrib>Updated for &os; 6.1-RELEASE by </contrib>
-	  <othername>The &os; Documentation Project</othername>
+	  <contrib>A &os; 6.1-RELEASE v&aacute;ltozat&aacute;hoz
+	    igaz&iacute;totta: </contrib>
+	  <othername>A &os; dokument&aacute;ci&oacute;s
+	    projekt</othername>
 	</author>
       </authorgroup>
     </sect1info>
 
-    <title>The <application>inetd</application> <quote>Super-Server</quote></title>
+    <title>Az <application>inetd</application>
+      <quote>szuperszerver</quote></title>
 
     <sect2 id="network-inetd-overview">
-      <title>Overview</title>
+      <title>&Aacute;ttekint&eacute;s</title>
 
-      <para>&man.inetd.8; is sometimes referred to as the <quote>Internet
-	Super-Server</quote> because it manages connections for
-	several services.  When a
-	connection is received by <application>inetd</application>, it
-	determines which program the connection is destined for, spawns
-	the particular process and delegates the socket to it (the program
-	is invoked with the service socket as its standard input, output
-	and error descriptors).  Running
-	<application>inetd</application> for servers that are not heavily used can reduce the
-	overall system load, when compared to running each daemon
-	individually in stand-alone mode.</para>
+      <para>Az &man.inetd.8; d&eacute;mont gyakran csak <quote>internet
+	szuperszerverk&eacute;nt</quote> nevezik, mivel a helyi
+	szolg&aacute;ltat&aacute;sok kapcsolatainak
+	kezel&eacute;s&eacute;&eacute;rt felel&#245;s.  Amikor az
+	<application>inetd</application> fogad egy csatlakoz&aacute;si
+	k&eacute;relmet, akkor eld&ouml;nti r&oacute;la, hogy ez melyik
+	programhoz tartozik &eacute;s elind&iacute;t egy
+	p&eacute;ld&aacute;nyt bel&#245;le, majd &aacute;tadja neki a
+	csatlakoz&aacute;st (az &iacute;gy megh&iacute;vott program a
+	szabv&aacute;ny bemenet&eacute;hez, kimenet&eacute;hez &eacute;s
+	hibajelz&eacute;si csatorn&aacute;j&aacute;hoz kapja meg a
+	csatlakoz&aacute;s le&iacute;r&oacute;it).  Az
+	<application>inetd</application> haszn&aacute;lat&aacute;val
+	&uacute;gy tudjuk cs&ouml;kkenteni a rendszer&uuml;nk
+	terhel&eacute;s&eacute;t, hogy a csak alkalmank&eacute;nt
+	megh&iacute;vott szolg&aacute;ltat&aacute;sokat nem futtatjuk
+	teljesen f&uuml;ggetlen &ouml;n&aacute;ll&oacute;
+	m&oacute;dban.</para>
 
-      <para>Primarily, <application>inetd</application> is used to
-	spawn other daemons, but several trivial protocols are handled
-	directly, such as <application>chargen</application>,
-	<application>auth</application>, and
+      <para>Az <application>inetd</application> d&eacute;mont
+	els&#245;sorban m&aacute;s d&eacute;monok
+	elind&iacute;t&aacute;s&aacute;ra haszn&aacute;ljuk, de
+	n&eacute;h&aacute;ny trivi&aacute;lis protokollt
+	k&ouml;zvetlen&uuml;l is k&eacute;pes besz&eacute;lni, mint
+	p&eacute;ld&aacute;ul a <application>chargen</application>,
+	<application>auth</application> &eacute;s a
 	<application>daytime</application>.</para>
 
-      <para>This section will cover the basics in configuring
-	<application>inetd</application> through its command-line
-	options and its configuration file,
-	<filename>/etc/inetd.conf</filename>.</para>
+      <para>Ebben a fejezetben az <application>inetd</application>
+	be&aacute;ll&iacute;t&aacute;s&aacute;nak alapjait foglaljuk
+	&ouml;ssze mind parancssoros m&oacute;dban, mind pedig az
+	<filename>/etc/inetd.conf</filename> konfigur&aacute;ci&oacute;s
+	&aacute;llom&aacute;nyon kereszt&uuml;l.</para>
+
     </sect2>
 
     <sect2 id="network-inetd-settings">
-      <title>Settings</title>
+      <title>Be&aacute;ll&iacute;t&aacute;sok</title>
 
-      <para><application>inetd</application> is initialized through
-	the &man.rc.8; system.  The
-	<literal>inetd_enable</literal> option is set to
-	<literal>NO</literal> by default, but may be turned on
-	by <application>sysinstall</application> during installation,
-	depending on the configuration chosen by the user.
-	Placing:</para>
+      <para>Az <application>inetd</application>
+	m&#251;k&ouml;d&eacute;se az &man.rc.8; rendszeren kereszt&uuml;l
+	inicializ&aacute;lhat&oacute;.  Az
+	<literal>inetd_enable</literal> ugyan alapb&oacute;l a
+	<literal>NO</literal> &eacute;rt&eacute;ket veszi fel, vagyis
+	tiltott, de a <application>sysinstall</application>
+	haszn&aacute;lat&aacute;val m&aacute;r ak&aacute;r a
+	telep&iacute;t&eacute;s sor&aacute;n bekapcsolhat&oacute;
+	att&oacute;l f&uuml;gg&#245;en, hogy a felhaszn&aacute;l&oacute;
+	milyen konfigur&aacute;ci&oacute;t v&aacute;lasztott.  Ha
+	teh&aacute;t a:</para>
 
-	<programlisting>inetd_enable="YES"</programlisting>
+      <programlisting>inetd_enable="YES"</programlisting>
 
-      <para>or</para>
+      <para>vagy</para>
 
-	<programlisting>inetd_enable="NO"</programlisting>
+      <programlisting>inetd_enable="NO"</programlisting>
 
-      <para>into
-	<filename>/etc/rc.conf</filename> will enable or disable
-	<application>inetd</application> starting at boot time.
-	The command:</para>
+      <para>sort tessz&uuml;k az <filename>/etc/rc.conf</filename>
+	&aacute;llom&aacute;nyba, akkor azzal rendre az
+	<application>inetd</application> d&eacute;mont
+	ind&iacute;thatjuk el vagy tilthatjuk le a rendszer
+	ind&iacute;t&aacute;sa sor&aacute;n.  Az</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/inetd rcvar</userinput></screen>
 
-      <para>
-	can be run to display the current effective setting.</para>
+      <para>paranccsal lek&eacute;rdezhetj&uuml;k a pillanatnyilag
+	&eacute;rv&eacute;nyes be&aacute;ll&iacute;t&aacute;st.</para>
+
+      <para>Emellett m&eacute;g az <application>inetd</application>
+	d&eacute;monnak az <literal>inetd_flags</literal>
+	v&aacute;ltoz&oacute;n kereszt&uuml;l
+	k&uuml;l&ouml;nb&ouml;z&#245; parancssori param&eacute;tereket
+	is &aacute;t tudunk adni.</para>
 
-      <para>Additionally, different command-line options can be passed
-	to <application>inetd</application> via the
-	<literal>inetd_flags</literal> option.</para>
     </sect2>
 
     <sect2 id="network-inetd-cmdline">
-      <title>Command-Line Options</title>
+      <title>Parancssori param&eacute;terek</title>
 
-      <para>Like most server daemons, <application>inetd</application>
-	has a number of options that it can be passed in order to
-	modify its behaviour.  The full list of options reads:</para>
+      <para>Hasonl&oacute;an a legt&ouml;bb szerverhez, az
+	<application>inetd</application> viselked&eacute;s&eacute;t is
+	befoly&aacute;solni tudjuk a parancssorban
+	&aacute;tadhat&oacute; k&uuml;l&ouml;nb&ouml;z&#245;
+	param&eacute;terekkel.  Ezek teljes list&aacute;ja a
+	k&ouml;vetkez&#245;:</para>
 
-      <para><command>inetd</command> <option>[-d] [-l] [-w] [-W] [-c maximum] [-C rate] [-a address | hostname]
-           [-p filename] [-R rate] [-s maximum] [configuration file]</option></para>
+      <para><command>inetd</command> <option>[-d] [-l] [-w] [-W] [-c
+	maximum] [-C ar&aacute;ny] [-a c&iacute;m | n&eacute;v] [-p
+	&aacute;llom&aacute;ny] [-R ar&aacute;ny] [-s maximum]
+	[konfigur&aacute;ci&oacute;s
+	&aacute;llom&aacute;ny]</option></para>
 
-      <para>Options can be passed to <application>inetd</application> using the
-	<literal>inetd_flags</literal> option in
-	<filename>/etc/rc.conf</filename>.  By default,
-	<literal>inetd_flags</literal> is set to
-	<literal>-wW -C 60</literal>, which turns on TCP wrapping for
-	<application>inetd</application>'s services, and prevents any
-	single IP address from requesting any service more than 60 times
-	in any given minute.</para>
+      <para>Ezek a param&eacute;terek az
+	<filename>/etc/rc.conf</filename> &aacute;llom&aacute;nyban az
+	<literal>inetd_flags</literal> seg&iacute;ts&eacute;g&eacute;vel
+	adhat&oacute;ak meg az <application>inetd</application>
+	r&eacute;sz&eacute;re.  Alap&eacute;rtelmez&eacute;s szerint az
+	<literal>inetd_flags</literal> &eacute;rt&eacute;ke <literal>-wW
+	-C 60</literal>, ami az <application>inetd</application>
+	&aacute;ltal biztos&iacute;tott szolg&aacute;ltat&aacute;sok TCP
+	burkol&aacute;s&aacute;t kapcsolja be, illetve egy
+	IP-c&iacute;mr&#245;l nem engedi a felk&iacute;n&aacute;lt
+	szolg&aacute;ltat&aacute;sok el&eacute;r&eacute;s&eacute;t
+	percenk&eacute;nt hatvann&aacute;l t&ouml;bbsz&ouml;r.</para>
 
-      <para>Novice users may be pleased to note that
-	these parameters usually do not need to be modified,
-	although we mention the rate-limiting options below as
-	they be useful should you find that you are receiving an
-	excessive amount of connections.  A full list of options
-	can be found in the &man.inetd.8; manual.</para>
+      <para>A kezd&#245; felhaszn&aacute;l&oacute;k &ouml;r&ouml;mmel
+	nyugt&aacute;zhatj&aacute;k, hogy ezeket az
+	alapbe&aacute;ll&iacute;t&aacute;sokat nem sz&uuml;ks&eacute;ges
+	m&oacute;dos&iacute;taniuk, hab&aacute;r a
+	k&eacute;s&#245;bbiekben majd f&eacute;ny der&uuml;l arra, hogy
+	a kiszolg&aacute;l&aacute;s gyakoris&aacute;g&aacute;nak
+	szab&aacute;lyoz&aacute;sa remek v&eacute;dekez&eacute;st
+	ny&uacute;jthat t&uacute;lzottan nagy mennyis&eacute;g&#251;
+	kapcsol&oacute;d&aacute;si k&eacute;relem ellen.  A
+	megadhat&oacute; param&eacute;terek teljes list&aacute;ja az
+	&man.inetd.8; man oldal&aacute;n olvashat&oacute;.</para>
 
       <variablelist>
 	<varlistentry>
-	  <term>-c maximum</term>
+	  <term>-c <replaceable>maximum</replaceable></term>
 
 	  <listitem>
-	    <para>Specify the default maximum number of simultaneous
-	      invocations of each service; the default is unlimited.
-	      May be overridden on a per-service basis with the
-	      <option>max-child</option> parameter.</para>
+	    <para>Az egyes szolg&aacute;ltat&aacute;sokhoz egyszerre
+	      fel&eacute;p&iacute;thet&#245; kapcsolatok
+	      alap&eacute;rtelmezett maxim&aacute;lis
+	      sz&aacute;m&aacute;t adja meg.  Alapb&oacute;l ezt a
+	      d&eacute;mont nem korl&aacute;tozza.  A
+	      <option>max-child</option>
+	      be&aacute;ll&iacute;t&aacute;ssal ez ak&aacute;r
+	      szolg&aacute;ltat&aacute;sonk&eacute;nt k&uuml;l&ouml;n is
+	      megadhat&oacute;.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>-C rate</term>
+	  <term>-C <replaceable>ar&aacute;ny</replaceable></term>
 
 	  <listitem>
-	    <para>Specify the default maximum number of times a
-	      service can be invoked from a single IP address in one
-	      minute; the default is unlimited.  May be overridden on a
-	      per-service basis with the
+	    <para>Korl&aacute;tozza, hogy egyetlen IP-c&iacute;mr&#245;l
+	      alapb&oacute;l h&aacute;nyszor h&iacute;vhat&oacute;ak meg
+	      az egyes szolg&aacute;ltat&aacute;sok egy percen
+	      bel&uuml;l.  Ez az &eacute;rt&eacute;k alapb&oacute;l
+	      korl&aacute;tlan.  A
 	      <option>max-connections-per-ip-per-minute</option>
-	      parameter.</para>
+	      be&aacute;ll&iacute;t&aacute;ssal ez
+	      szolg&aacute;ltat&aacute;sonk&eacute;nt is
+	      defini&aacute;lhat&oacute;.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>-R rate</term>
+	  <term>-R <replaceable>ar&aacute;ny</replaceable></term>
 
 	  <listitem>
-	    <para>Specify the maximum number of times a service can be
-	      invoked in one minute; the default is 256.  A rate of 0
-	      allows an unlimited number of invocations.</para>
+	    <para>Megadja, hogy egy szolg&aacute;ltat&aacute;st egy perc
+	      alatt mennyiszer lehet megh&iacute;vni.  Ez az
+	      &eacute;rt&eacute;k alap&eacute;rtelmez&eacute;s szerint
+	      256.  A 0 megad&aacute;s&aacute;val
+	      elt&ouml;r&ouml;lj&uuml;k ezt a t&iacute;pus&uacute;
+	      korl&aacute;toz&aacute;st.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>-s maximum</term>
+	  <term>-s <replaceable>maximum</replaceable></term>
 
 	  <listitem>
-	    <para>Specify the maximum number of times a service can be
-	      invoked from a single IP address at any one time; the
-	      default is unlimited.  May be overridden on a per-service
-	      basis with the <option>max-child-per-ip</option>
-	      parameter.</para>
+	    <para>Annak maximum&aacute;t adja meg, hogy egyetlen
+	      IP-c&iacute;mr&#245;l egyszerre az egyes
+	      szolg&aacute;ltat&aacute;sokat mennyiszer tudjuk
+	      el&eacute;rni.  Alapb&oacute;l ez korl&aacute;tlan.
+	      Szolg&aacute;ltat&aacute;sonk&eacute;nt ezt a
+	      <option>max-child-per-ip</option> param&eacute;terrel
+	      tudjuk fel&uuml;lb&iacute;r&aacute;lni.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 id="network-inetd-conf">
-      <!-- XXX This section isn't very clear, and could do with some lovin' -->
-      <title><filename>inetd.conf</filename></title>
+      <title>Az <filename>inetd.conf</filename>
+	&aacute;llom&aacute;ny</title>
 
-      <para>Configuration of <application>inetd</application> is
-	done via the file <filename>/etc/inetd.conf</filename>.</para>
+      <para>Az <application>inetd</application>
+	be&aacute;ll&iacute;t&aacute;s&aacute;t az
+	<filename>/etc/inetd.conf</filename> konfigur&aacute;ci&oacute;s
+	&aacute;llom&aacute;nyon kereszt&uuml;l v&eacute;gezhetj&uuml;k
+	el.</para>
 
-      <para>When a modification is made to
-	<filename>/etc/inetd.conf</filename>,
-	<application>inetd</application> can be forced to re-read its
-	configuration file by running the command:</para>
+      <para>Amikor az <filename>/etc/inetd.conf</filename>
+	&aacute;llom&aacute;nyban m&oacute;dos&iacute;tunk valamit, az
+	<application>inetd</application> d&eacute;mont a
+	k&ouml;vetkez&#245; paranccsal meg kell k&eacute;rn&uuml;nk,
+	hogy olvassa &uacute;jra:</para>
 
       <example id="network-inetd-reread">
-	<title>Reloading the <application>inetd</application>
-	  configuration file</title>
+	<title>Az <application>inetd</application>
+	  konfigur&aacute;ci&oacute;s &aacute;llom&aacute;ny&aacute;nak
+	  &uacute;jraolvas&aacute;sa</title>
 
 	<screen>&prompt.root; <userinput>/etc/rc.d/inetd reload</userinput></screen>
       </example>
 
-      <para>Each line of the configuration file specifies an
-	individual daemon.  Comments in the file are preceded by a
-	<quote>#</quote>.  The format of each entry in
-	<filename>/etc/inetd.conf</filename> is as follows:</para>
+      <para>A konfigur&aacute;ci&oacute;s &aacute;llom&aacute;ny minden
+	egyes sora egy-egy d&eacute;mont &iacute;r le.  A
+	megjegyz&eacute;seket egy <quote>#</quote> jel vezeti be.  Az
+	<filename>/etc/inetd.conf</filename> &aacute;llom&aacute;ny
+	bejegyz&eacute;seinek form&aacute;tuma az al&aacute;bbi:</para>
 
-      <programlisting>service-name
-socket-type
-protocol
+      <programlisting><replaceable>szolg&aacute;ltat&aacute;s-neve</replaceable>
+<replaceable>csatlakoz&aacute;s-t&iacute;pusa</replaceable>
+<replaceable>protokoll</replaceable>
 {wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]
-user[:group][/login-class]
-server-program
-server-program-arguments</programlisting>
+<replaceable>felhaszn&aacute;l&oacute;</replaceable>[:<replaceable>csoport</replaceable>][/<replaceable>bejelentkez&eacute;si-oszt&aacute;ly</replaceable>]
+<replaceable>szerver-program</replaceable>
+<replaceable>szerver-program-param&eacute;terei</replaceable></programlisting>
 
-      <para>An example entry for the &man.ftpd.8; daemon
-	using IPv4 might read:</para>
+      <para>Az IPv4 protokollt haszn&aacute;l&oacute; &man.ftpd.8;
+	d&eacute;mon bejegyz&eacute;se p&eacute;ld&aacute;ul &iacute;gy
+	n&eacute;z ki:</para>
 
       <programlisting>ftp     stream  tcp     nowait  root    /usr/libexec/ftpd       ftpd -l</programlisting>
 
       <variablelist>
 	<varlistentry>
-	  <term>service-name</term>
+	  <term>szolg&aacute;ltat&aacute;s-neve</term>
 
 	  <listitem>
-	    <para>This is the service name of the particular daemon.
-	      It must correspond to a service listed in
-	      <filename>/etc/services</filename>.  This determines
-	      which port <application>inetd</application> must listen
-	      to.  If a new service is being created, it must be
-	      placed in <filename>/etc/services</filename>
-	      first.</para>
+	    <para>Ez az adott d&eacute;mon &aacute;ltal k&eacute;pviselt
+	      szolg&aacute;ltat&aacute;st nevezi meg, aminek szerepelnie
+	      kell az <filename>/etc/services</filename>
+	      &aacute;llom&aacute;nyban.  Ez hat&aacute;rozza meg, hogy
+	      az <application>inetd</application> milyen porton figyelje
+	      a be&eacute;rkez&#245; kapcsolatokat.  Ha egy &uacute;j
+	      szolg&aacute;ltat&aacute;st hozunk l&eacute;tre, akkor azt
+	      el&#245;sz&ouml;r az <filename>/etc/services</filename>
+	      &aacute;llom&aacute;nyba kell felvenn&uuml;nk.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>socket-type</term>
+	  <term>csatlakoz&aacute;s-t&iacute;pusa</term>
 
 	  <listitem>
-	    <para>Either <literal>stream</literal>,
-	      <literal>dgram</literal>, <literal>raw</literal>, or
-	      <literal>seqpacket</literal>.  <literal>stream</literal>
-	      must be used for connection-based, TCP daemons, while
-	      <literal>dgram</literal> is used for daemons utilizing
-	      the <acronym>UDP</acronym> transport protocol.</para>
+	    <para>Ennek az &eacute;rt&eacute;ke
+	      <literal>stream</literal>, <literal>dgram</literal>,
+	      <literal>raw</literal>, vagy <literal>seqpacket</literal>
+	      lehet.  A <literal>stream</literal> t&iacute;pust
+	      haszn&aacute;lja a legt&ouml;bb kapcsolat-orient&aacute;lt
+	      TCP d&eacute;mon, mik&ouml;zben a <literal>dgram</literal>
+	      t&iacute;pus az <acronym>UDP</acronym>
+	      sz&aacute;ll&iacute;t&aacute;si protokollt
+	      alkalmaz&oacute; d&eacute;monok eset&eacute;ben
+	      haszn&aacute;latos.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>protocol</term>
+	  <term>protokoll</term>
 
 	  <listitem>
-	    <para>One of the following:</para>
+	    <para>Valamelyik a k&ouml;vetkez&#245;k
+	      k&ouml;z&uuml;l:</para>
 
 	    <informaltable frame="none" pgwide="1">
 	      <tgroup cols="2">
 		<thead>
 		  <row>
-		    <entry>Protocol</entry>
-		    <entry>Explanation</entry>
+		    <entry>Protokoll</entry>
+		    <entry>Magyar&aacute;zat</entry>
 		  </row>
 		</thead>
 		<tbody>
@@ -344,11 +434,11 @@
 		  </row>
 		  <row>
 		    <entry>tcp46</entry>
-		    <entry>Both TCP IPv4 and v6</entry>
+		    <entry>TCP IPv4 &eacute;s v6</entry>
 		  </row>
 		  <row>
 		    <entry>udp46</entry>
-		    <entry>Both UDP IPv4 and v6</entry>
+		    <entry>UDP IPv4 &eacute;s v6</entry>
 		  </row>
 		</tbody>
 	      </tgroup>
@@ -360,246 +450,340 @@
 	  <term>{wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]</term>
 
 	  <listitem>
-	    <para><option>wait|nowait</option> indicates whether the
-	      daemon invoked from <application>inetd</application> is
-	      able to handle its own socket or not.
-	      <option>dgram</option> socket types must use the
-	      <option>wait</option> option, while stream socket
-	      daemons, which are usually multi-threaded, should use
-	      <option>nowait</option>.  <option>wait</option> usually
-	      hands off multiple sockets to a single daemon, while
-	      <option>nowait</option> spawns a child daemon for each
-	      new socket.</para>
+	    <para>A <option>wait|nowait</option>
+	      be&aacute;ll&iacute;t&aacute;s mondja meg, hogy az
+	      <application>inetd</application> d&eacute;monb&oacute;l
+	      megh&iacute;vott d&eacute;mon saj&aacute;t maga
+	      k&eacute;pes-e kezelni kapcsolatokat.  A
+	      <option>dgram</option> t&iacute;pus&uacute; kapcsolatok
+	      eset&eacute;ben egy&eacute;rtelm&#251;en a
+	      <option>wait</option> be&aacute;ll&iacute;t&aacute;st kell
+	      haszn&aacute;lni, mik&ouml;zben a <option>stream</option>
+	      haszn&aacute;lat&aacute;n&aacute;l, ami
+	      &aacute;ltal&aacute;ban t&ouml;bb sz&aacute;lon
+	      t&ouml;rt&eacute;nik, a <option>nowait</option>
+	      megad&aacute;sa javasolt.  A <option>wait</option>
+	      hat&aacute;s&aacute;ra &aacute;ltal&aacute;ban egyetlen
+	      d&eacute;monnak adunk &aacute;t t&ouml;bb
+	      csatlakoz&aacute;st, m&iacute;g a <option>nowait</option>
+	      minden kapcsolathoz egy &uacute;jabb
+	      p&eacute;ld&aacute;nyt ind&iacute;t el.</para>
 
-	    <para>The maximum number of child daemons
-	      <application>inetd</application> may spawn can be set
-	      using the <option>max-child</option> option.  If a limit
-	      of ten instances of a particular daemon is needed, a
-	      <literal>/10</literal> would be placed after
-	      <option>nowait</option>.  Specifying <literal>/0</literal>
-	      allows an unlimited number of children</para>
+	    <para>Az <application>inetd</application> &aacute;ltal
+	      ind&iacute;that&oacute; p&eacute;ld&aacute;nyokat a
+	      <option>max-child</option> megad&aacute;s&aacute;val
+	      korl&aacute;tozhatjuk.  Ha teh&aacute;t mondjuk az adott
+	      d&eacute;mon sz&aacute;m&aacute;ra legfeljebb
+	      p&eacute;ld&aacute;ny l&eacute;trehoz&aacute;s&aacute;t
+	      enged&eacute;lyezz&uuml;k, akkor a <option>nowait</option>
+	      ut&aacute;n <literal>/10</literal>
+	      be&aacute;ll&iacute;t&aacute;st kell megadnunk.  A
+	      <literal>/0</literal> haszn&aacute;lat&aacute;val
+	      korl&aacute;tlan mennyis&eacute;g&#251;
+	      p&eacute;ld&aacute;nyt
+	      enged&eacute;lyezhet&uuml;nk.</para>
 
-	    <para>In addition to <option>max-child</option>, two other
-	      options which limit the maximum connections from a single
-	      place to a particular daemon can be enabled.
-	      <option>max-connections-per-ip-per-minute</option> limits
-	      the number of connections from any particular IP address
-	      per minutes, e.g. a value of ten would limit any particular
-	      IP address connecting to a particular service to ten
-	      attempts per minute.  <option>max-child-per-ip</option>
-	      limits the number of children that can be started on
-	      behalf on any single IP address at any moment. These
-	      options are useful to prevent intentional or unintentional
- 	      excessive resource consumption and Denial of Service (DoS)
-	      attacks to a machine.</para>
+	    <para>A <option>max-child</option> mellett m&eacute;g
+	      tov&aacute;bbi k&eacute;t m&aacute;sik
+	      be&aacute;ll&iacute;t&aacute;s j&ouml;het
+	      sz&aacute;m&iacute;t&aacute;sba az egyes d&eacute;monok
+	      &aacute;ltal kezelhet&#245; kapcsolatok maxim&aacute;lis
+	      sz&aacute;m&aacute;nak
+	      korl&aacute;toz&aacute;s&aacute;ban.  A
+	      <option>max-connections-per-ip-per-minute</option> az
+	      egyes IP-c&iacute;mekr&#245;l befut&oacute;
+	      lekezelhet&#245; kapcsolatok percenk&eacute;nti
+	      sz&aacute;m&aacute;t szab&aacute;lyozza, &iacute;gy pl.
+	      ha itt a tizes &eacute;rt&eacute;ket adjuk meg, akkor az
+	      adott szolg&aacute;ltat&aacute;shoz egy
+	      IP-c&iacute;mr&#245;l percenk&eacute;nt csak
+	      t&iacute;zszer f&eacute;rhet&uuml;nk hozz&aacute;.  A
+	      <option>max-child-per-ip</option> az egyes
+	      IP-c&iacute;mekhez egyszerre elind&iacute;that&oacute;
+	      p&eacute;ld&aacute;nyok sz&aacute;m&aacute;ra &iacute;r
+	      el&#245; egy korl&aacute;tot.  Ezek a param&eacute;terek
+	      seg&iacute;tenek meg&oacute;vni rendszer&uuml;nket az
+	      er&#245;forr&aacute;sok akaratos vagy akaratlan
+	      kimer&iacute;t&eacute;s&eacute;t&#245;l &eacute;s a DoS
+	      (Denial of Service) t&iacute;pus&uacute;
+	      t&aacute;mad&aacute;sokt&oacute;l.</para>
 
-	    <para>In this field, either of <option>wait</option> or
-	      <option>nowait</option> is mandatory.
-	      <option>max-child</option>,
-	      <option>max-connections-per-ip-per-minute</option> and
-	      <option>max-child-per-ip</option> are
-	      optional.</para>
+	    <para>Ebben a mez&#245;ben a <option>wait</option> vagy
+	      <option>nowait</option> valamelyik&eacute;t
+	      k&ouml;telez&#245; megadni.  A <option>max-child</option>,
+	      <option>max-connections-per-ip-per-minute</option>
+	      &eacute;s <option>max-child-per-ip</option>
+	      param&eacute;terek ellenben elhagyhat&oacute;ak.</para>
 
-	    <para>A stream-type multi-threaded daemon without any
+	    <para>A <option>stream</option> t&iacute;pus&uacute;
+	      t&ouml;bb sz&aacute;lon fut&oacute; d&eacute;monok a
 	      <option>max-child</option>,
-	      <option>max-connections-per-ip-per-minute</option> or
-	      <option>max-child-per-ip</option> limits
-	      would simply be: <literal>nowait</literal>.</para>
+	      <option>max-connections-per-ip-per-minute</option> vagy
+	      <option>max-child-per-ip</option>
+	      korl&aacute;toz&aacute;sa n&eacute;lk&uuml;l
+	      egyszer&#251;en csak &iacute;gy adhat&oacute;ak meg:
+	      <literal>nowait</literal>.</para>
 
-	    <para>The same daemon with a maximum limit of ten daemons
-	      would read: <literal>nowait/10</literal>.</para>
+	    <para>Ha ugyanezt a d&eacute;mont t&iacute;z kapcsolatra
+	      lekorl&aacute;tozzuk, akkor a k&ouml;vetkez&#245;t kell
+	      megadnunk: <literal>nowait/10</literal>.</para>
 
-	    <para>The same setup with a limit of twenty
-	      connections per IP address per minute and a maximum
-	      total limit of ten child daemons would read:
+	    <para>Amikor pedig IP-c&iacute;menk&eacute;nt 20 kapcsolatot
+	      enged&eacute;lyez&uuml;nk percenk&eacute;nt &eacute;s
+	      mind&ouml;ssze 10 p&eacute;ld&aacute;nyt, akkor:
 	      <literal>nowait/10/20</literal>.</para>
 
-	    <para>These options are utilized by the default
-	      settings of the &man.fingerd.8; daemon,
-	      as seen here:</para>
+	    <para>Az im&eacute;nti be&aacute;ll&iacute;t&aacute;sok a
+	      &man.fingerd.8; d&eacute;mon alap&eacute;rtelmezett
+	      param&eacute;terein&eacute;l is
+	      megtal&aacute;lhat&oacute;ak:</para>
 
 	    <programlisting>finger stream  tcp     nowait/3/10 nobody /usr/libexec/fingerd fingerd -s</programlisting>
 
-	    <para>Finally, an example of this field with a maximum of
-	      100 children in total, with a maximum of 5 for any one
-	      IP address would read:
+	    <para>V&eacute;gezet&uuml;l enged&eacute;lyezz&uuml;k 100
+	      p&eacute;ld&aacute;nyt, melyek k&ouml;z&uuml;l
+	      IP-c&iacute;menk&eacute;nt 5 haszn&aacute;lhat&oacute;:
 	      <literal>nowait/100/0/5</literal>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>user</term>
+	  <term>felhaszn&aacute;l&oacute;</term>
 
 	  <listitem>
-	    <para>This is the username that the particular daemon
-	      should run as.  Most commonly, daemons run as the
-	      <username>root</username> user.  For security purposes, it is
-	      common to find some servers running as the
-	      <username>daemon</username> user, or the least privileged
-	      <username>nobody</username> user.</para>
+	    <para>Ezzel azt a felhaszn&aacute;l&oacute;t adjuk meg,
+	      akinek a nev&eacute;ben az adott d&eacute;mon futni fog.  Az
+	      esetek t&uacute;lnyom&oacute; r&eacute;sz&eacute;ben a
+	      d&eacute;monokat a <username>root</username>
+	      felhaszn&aacute;l&oacute; futtatja.  L&aacute;thatjuk
+	      azonban, hogy biztons&aacute;gi okokb&oacute;l bizonyos
+	      d&eacute;monok a <username>daemon</username> vagy a
+	      legkevesebb joggal rendelkez&#245;
+	      <username>nobody</username> felhaszn&aacute;l&oacute;val
+	      futnak.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>server-program</term>
+	  <term>szerver-program</term>
 
 	  <listitem>
-	    <para>The full path of the daemon to be executed when a
-	      connection is received.  If the daemon is a service
-	      provided by <application>inetd</application> internally,
-	      then <option>internal</option> should be
-	      used.</para>
+	    <para>A kapcsolat fel&eacute;p&uuml;l&eacute;sekor az itt
+	      teljes el&eacute;r&eacute;si &uacute;ttal megadott
+	      d&eacute;mon indul el.  Ha ezt a
+	      szolg&aacute;ltat&aacute;st maga az
+	      <application>inetd</application> bels&#245;leg
+	      val&oacute;s&iacute;tja meg, akkor ebben a mez&#245;ben az
+	      <option>internal</option> &eacute;rt&eacute;ket adjuk
+	      meg.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
-	  <term>server-program-arguments</term>
+	  <term>szerver-program-param&eacute;terei</term>
 
 	  <listitem>
-	    <para>This works in conjunction with
-	      <option>server-program</option> by specifying the
-	      arguments, starting with <literal>argv[0]</literal>,
-	      passed to the daemon on invocation.  If
-	      <command>mydaemon -d</command> is the command line,
-	      <literal>mydaemon -d</literal> would be the value of
-	      <option>server-program-arguments</option>.  Again, if
-	      the daemon is an internal service, use
-	      <option>internal</option> here.</para>
+	    <para>Ez a <option>szerver-program</option>
+	      be&aacute;ll&iacute;t&aacute;ssal egy&uuml;tt
+	      m&#251;k&ouml;dik, &eacute;s ebben a mez&#245;ben a
+	      d&eacute;mon megh&iacute;v&aacute;sakor
+	      alkalmazand&oacute; param&eacute;tereket tudjuk
+	      r&ouml;gz&iacute;teni, amit a d&eacute;mon nev&eacute;vel
+	      kezd&uuml;nk.  Ha a d&eacute;mont a parancssorb&oacute;l a
+	      <command>sajatdemon -d</command> paranccsal
+	      h&iacute;vn&aacute;nk meg, akkor a <literal>sajatdemon
+	      -d</literal> lesz
+	      <option>szerver-program-param&eacute;terei</option>
+	      be&aacute;ll&iacute;t&aacute;s helyes &eacute;rt&eacute;ke
+	      is.  Term&eacute;szetesen, ha a d&eacute;mon egy
+	      bels&#245;leg k&eacute;pviselt szolg&aacute;ltat&aacute;s,
+	      akkor ebben a mez&#245;ben is az <option>internal</option>
+	      fog megjelenni.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 id="network-inetd-security">
-      <title>Security</title>
+      <title>V&eacute;delem</title>
+
+      <para>Att&oacute;l f&uuml;gg&#245;en, hogy a
+	telep&iacute;t&eacute;s sor&aacute;n mit v&aacute;lasztottunk, az
+	<application>inetd</application> &aacute;ltal t&aacute;mogatott
+	szolg&aacute;ltat&aacute;sok egyes r&eacute;sze tal&aacute;n
+	alapb&oacute;l enged&eacute;lyezett is.  Amennyiben egy adott
+	d&eacute;mont konkr&eacute;tan nem haszn&aacute;lunk, akkor
+	&eacute;rdemes megfontolni a letilt&aacute;s&aacute;t.  A
+	k&eacute;rd&eacute;ses d&eacute;mon sor&aacute;ba tegy&uuml;nk
+	egy <quote>#</quote> jelet az
+	<filename>/etc/inetd.conf</filename> &aacute;llom&aacute;nyba,
+	majd <link linkend="network-inetd-reread">olvastassuk
+	&uacute;jra az inetd be&aacute;ll&iacute;t&aacute;sait</link>.
+	Egyes d&eacute;monok, mint mondjuk az
+	<application>fingerd</application> haszn&aacute;lata
+	egy&aacute;ltal&aacute;n nem aj&aacute;nlott, mivel a
+	t&aacute;mad&oacute;k sz&aacute;m&aacute;ra hasznos
+	inform&aacute;ci&oacute;kat tudnak
+	kisziv&aacute;rogtatni.</para>
 
-      <para>Depending on the choices made at install time, many
-	of <application>inetd</application>'s services may be enabled
-	by default.  If there is no apparent need for a particular
-	daemon, consider disabling it.  Place a <quote>#</quote> in front of the
-	daemon in question in <filename>/etc/inetd.conf</filename>,
-	and then <link linkend="network-inetd-reread">reload the
-	inetd configuration</link>.  Some daemons, such as
-	<application>fingerd</application>, may not be desired at all
-	because they provide
-	information that may be useful to an attacker.</para>
+      <para>M&aacute;s d&eacute;monok nem &uuml;gyelnek a
+	v&eacute;delemre, &eacute;s a kapcsolatokhoz rendelt
+	lej&aacute;rati idej&uuml;k t&uacute;ls&aacute;gosan
+	hossz&uacute; vagy &eacute;ppen nincs is.  Ezzel a
+	t&aacute;mad&oacute;nak lehet&#245;s&eacute;ge van lass&uacute;
+	kapcsolatokkal leterhelni az adott d&eacute;mont, ez&aacute;tal
+	kimer&iacute;teni a rendszer er&#245;forr&aacute;sait.  Ha
+	&uacute;gy tal&aacute;ljuk, hogy t&uacute;ls&aacute;gosan sok az
+	ilyen kapcsolat, akkor j&oacute; &ouml;tletnek bizonyulhat a
+	d&eacute;monok sz&aacute;m&aacute;ra a
+	<option>max-connections-per-ip-per-minute</option>,
+	<option>max-child</option> vagy
+	<option>max-child-per-ip</option> korl&aacute;toz&aacute;sok
+	elrendel&eacute;se.</para>
 
-      <para>Some daemons are not security-conscious and have long, or
-	non-existent, timeouts for connection attempts.  This allows an
-	attacker to slowly send connections to a particular daemon,
-	thus saturating available resources.  It may be a good idea to
-	place <option>max-connections-per-ip-per-minute</option>,
-	<option>max-child</option> or <option>max-child-per-ip</option> limitations on certain
-	daemons if you find that you have too many connections.</para>
+      <para>Alap&eacute;rtelmez&eacute;s szerint a TCP kapcsolatok
+	burkol&aacute;sa enged&eacute;lyezett.  A &man.hosts.access.5; man
+	oldalon tal&aacute;lhatjuk meg az
+	<application>inetd</application> &aacute;ltal
+	megh&iacute;vhat&oacute; k&uuml;l&ouml;nf&eacute;le
+	d&eacute;monok TCP alap&uacute; korl&aacute;toz&aacute;sainak
+	lehet&#245;s&eacute;geit.</para>
 
-      <para>By default, TCP wrapping is turned on.  Consult the
-	&man.hosts.access.5; manual page for more information on placing
-	TCP restrictions on various <application>inetd</application>
-	invoked daemons.</para>
     </sect2>
 
     <sect2 id="network-inetd-misc">
-      <title>Miscellaneous</title>
+      <title>Egy&eacute;b lehet&#245;s&eacute;gek</title>
 
-      <para><application>daytime</application>,
+      <para>A <application>daytime</application>,
 	<application>time</application>,
 	<application>echo</application>,
 	<application>discard</application>,
-	<application>chargen</application>, and
-	<application>auth</application> are all internally provided
-	services of <application>inetd</application>.</para>
+	<application>chargen</application> &eacute;s
+	<application>auth</application> szolg&aacute;ltat&aacute;sok
+	feladatainak mindegyik&eacute;t maga az
+	<application>inetd</application> is k&eacute;pes
+	ell&aacute;tni.</para>
+
+      <para>Az <application>auth</application>
+	szolg&aacute;ltat&aacute;s a h&aacute;l&oacute;zati kereszt&uuml;l
+	azonos&iacute;t&aacute;st teszi lehet&#245;v&eacute; &eacute;s
+	bizonyos m&eacute;rt&eacute;kig
+	be&aacute;ll&iacute;that&oacute;.  A t&ouml;bbit egyszer&#251;en
+	csak kapcsoljuk ki vagy be.</para>
 
-      <para>The <application>auth</application> service provides
-	identity
-	network services, and is
-	configurable to a certain degree, whilst the others are simply on or off.</para>
+      <para>A t&eacute;m&aacute;ban az &man.inetd.8; man oldal&aacute;n
+	tudunk elmer&uuml;lni m&eacute;g jobban.</para>
 
-      <para>Consult the &man.inetd.8; manual page for more in-depth
-	information.</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-nfs">
     <sect1info>
       <authorgroup>
-        <author>
-          <firstname>Tom</firstname>
-          <surname>Rhodes</surname>
-          <contrib>Reorganized and enhanced by </contrib>
-        </author>
+	<author>
+	  <firstname>Tom</firstname>
+	  <surname>Rhodes</surname>
+	  <contrib>&Uacute;jraszervezte &eacute;s feljav&iacute;totta:
+	    </contrib>
+	</author>
       </authorgroup>
       <authorgroup>
-        <author>
-          <firstname>Bill</firstname>
-      	  <surname>Swingle</surname>
-	  <contrib>Written by </contrib>
-        </author>
+	<author>
+	  <firstname>Bill</firstname>
+	  <surname>Swingle</surname>
+	  <contrib>&Iacute;rta: </contrib>
+	</author>
       </authorgroup>
     </sect1info>
-    <title>Network File System (NFS)</title>
+
+    <title>A h&aacute;l&oacute;zati &aacute;llom&aacute;nyrendszer
+      (NFS)</title>
 
     <indexterm><primary>NFS</primary></indexterm>
-    <para>Among the many different file systems that FreeBSD supports
-      is the Network File System, also known as <acronym role="Network
-      File System">NFS</acronym>.  <acronym role="Network File
-      System">NFS</acronym> allows a system to share directories and
-      files with others over a network.  By using <acronym
-      role="Network File System">NFS</acronym>, users and programs can
-      access files on remote systems almost as if they were local
-      files.</para>
+
+    <para>A &os; t&ouml;bb &aacute;llom&aacute;nyrendszert ismer,
+      k&ouml;zt&uuml;k a h&aacute;l&oacute;zati
+      &aacute;llom&aacute;nyrendszert (Network File System, <acronym
+      role="Network File System">NFS</acronym>) is.  Az <acronym
+      role="Network File System">NFS</acronym> &aacute;llom&aacute;nyok
+      &eacute;s k&ouml;nyvt&aacute;rak megoszt&aacute;s&aacute;t teszi
+      lehet&#245;v&eacute; a h&aacute;l&oacute;zaton kereszt&uuml;l.  Az
+      <acronym role="Network File System">NFS</acronym>
+      haszn&aacute;lat&aacute;val a felhaszn&aacute;l&oacute;k &eacute;s
+      a programok k&eacute;pesek majdnem &uacute;gy el&eacute;rni a
+      t&aacute;voli rendszereken tal&aacute;lhat&oacute;
+      &aacute;llom&aacute;nyokat, mintha helyben
+      l&eacute;tezn&eacute;nek.</para>
 
-    <para>Some of the most notable benefits that
-      <acronym>NFS</acronym> can provide are:</para>
+    <para>&Iacute;me az <acronym>NFS</acronym> n&eacute;h&aacute;ny

>>> TRUNCATED FOR MAIL (1000 lines) <<<



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803150330.m2F3UURb070125>