Date: Fri, 15 Oct 2004 13:44:05 +0400 From: Denis Peplin <den@FreeBSD.org> To: Denis Peplin <den@FreeBSD.org> Cc: "Simon L. Nielsen" <simon@FreeBSD.org> Subject: Re: TCP Wrappers section (handbook/security): services is not daemons Message-ID: <416F9BE5.5020403@FreeBSD.org> In-Reply-To: <416E8CD3.9070700@FreeBSD.org> References: <416E4DFD.3040203@FreeBSD.org> <20041014102459.GD799@zaphod.nitro.dk> <20041014092213.22d6914d@localhost> <416E8491.8080500@FreeBSD.org> <20041014101233.399d4b40@localhost> <416E8CD3.9070700@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Hello!
I have patch for this issue (attached), and keramida help
me to fix it English form.
log:
Obtain some information from inetd(8) to fix "inetd"
description in network-servers chapter.
Add note about "daemon" term to "tcpwrappers" section
of security chapter.
Denis Peplin wrote:
> Hello!
>
> Tom Rhodes wrote:
>
>> On Thu, 14 Oct 2004 17:52:17 +0400
>> Denis Peplin <den@FreeBSD.org> wrote:
>>
>>
>>> Hello!
>>>
>>> Yes, i see now that using word "daemon" for services is
>>> tradition here :)
>>>
>>> It will not be a big problem, if we will add short
>>> description for this "term" (explain tradition) in
>>> beginning of the section.
>>
>>
>>
>> We can do that, but I do see one slight problem: Should you
>> write a patch or should I? I'm kind of in the middle of a
>> move and a new job so my FreeBSD time is pretty short. :)
>>
> I can write it, but i'm not native English speaker, so you preferred :)
[-- Attachment #2 --]
Index: network-servers/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v
retrieving revision 1.31
diff -u -r1.31 chapter.sgml
--- network-servers/chapter.sgml 8 Oct 2004 15:22:40 -0000 1.31
+++ network-servers/chapter.sgml 15 Oct 2004 09:36:06 -0000
@@ -111,12 +111,12 @@
<para>&man.inetd.8; is referred to as the <quote>Internet
Super-Server</quote> because it manages connections for
- several daemons. Programs that provide network service are
- commonly known as daemons. <application>inetd</application>
- serves as a managing server for other daemons. When a
+ several services. When a
connection is received by <application>inetd</application>, it
- determines which daemon the connection is destined for, spawns
- the particular daemon and delegates the socket to it. Running
+ 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
one instance of <application>inetd</application> reduces the
overall system load as compared to running each daemon
individually in stand-alone mode.</para>
Index: security/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v
retrieving revision 1.228
diff -u -r1.228 chapter.sgml
--- security/chapter.sgml 3 Oct 2004 23:35:59 -0000 1.228
+++ security/chapter.sgml 15 Oct 2004 09:36:08 -0000
@@ -1501,6 +1501,12 @@
read the <link linkend="network-inetd">inetd configuration</link>
section.</para>
+ <note>
+ <para>While programs run by &man.inetd.8; are not exactly
+ <quote>daemons</quote>, they have traditionally been called
+ daemons. This is the term we will use in this section too.</para>
+ </note>
+
<sect2>
<title>Initial Configuration</title>
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?416F9BE5.5020403>