Talk:Inetd

"Server"
I see that the phrase "inetd server" is straight from the man page, but that predates the advent of "client-server" terminology, so it might leave the reader confused. For instance when I glanced at the header, I thought is was going to be a very simple example of inetd itself, since technically inetd is a server. "inetd service" would be slightly better.--J Clear 23:43, 13 June 2006 (UTC)
 * I think that calling a service handler spawned by inetd a server is correct, as it is really just acting as a part of inetd (via a fork, to make a copy, and an exec to overlay the copy with the appropriate handler). However, I agree that it might be confusing--the whole client-server thing can be confusing, especially with protocols like X, where, for example, the server runs on my PC and the clients are various Unix systems spread across the country.  I went ahead and changed the all the appropriate occurrences of "server" to "service" that I saw.  scot 14:02, 14 June 2006 (UTC)
 * Thanks for the edits. Let me make my point another way though.  Read the heading "Creating an inetd server" out of context.  It's not that I don't think inetd is starting servers, just that the headline could refer to inetd itself.  I'm a hardware guy, so the X protocol server makes perfect sense to me. ;-)--J Clear 23:07, 14 June 2006 (UTC)
 * OK, so I did miss one. I will make the change.  I might also put in (if it's not already there) that inetd is often called a "super-server", since it is basicially a server server...  scot 14:39, 15 June 2006 (UTC)

de-stub
It seems like this is complete enough for your average computer user or sysadmin. So I removed the stub tag.--J Clear 01:04, 14 June 2006 (UTC)
 * Acutally, I think it's pretty much everything the average C/C++ programmer needs to know to implement a basic service. That's what I came here looking for, and when I didn't find it here, I decided to add it once I found it.  The documentation for actually implementing an inetd server using the methods outlined is pretty scarse on the web--or rather it was pretty scarse, now it ought to be all over the place in the hundreds of Wikipedia mirrors.  scot 14:06, 14 June 2006 (UTC)

RfC
Large quantities of text have been added to this article, and should be reviewed for accuracy and general applicability. The article also appears to require significant copyediting for style and tone, and formatting by someone familiar with the topic.  Acroterion  (talk)  12:32, 31 October 2007 (UTC)
 * Hi, me again from the RfCsci page. It looks like the major additions were confined to the "Function" section.  I came in here, not knowing anything about inetd, but after reading the new content I'm confused.  Just what does inetd do?  Before User:Wiki104's edits, the function section was one rather concise paragraph that suitably explains the topic.  I think the whole of Wiki104's additions can go. &mdash; EagleOne\Talk 19:04, 9 November 2007 (UTC)
 * I agree with EagleOne in that the best thing to do was to remove Wiki104's additions. The problem with the added text was that it attempted to introduce high-level concepts that should be explained in other articles. Also, parts of the text contained inforamtion that is handled in later sections in this article. However, it may be possible to use parts of the remvoed text in super-server or daemon. Labongo 17:47, 13 November 2007 (UTC)
 * Edits have been reviewed and removed, so I have removed to RfC tag.Labongo 13:09, 16 November 2007 (UTC)

Howto information
The how-to information provided seems slightly excessive. Perhaps I should trim it a little and add some more background information? Qbeep (talk) 19:43, 9 April 2009 (UTC)
 * Absolutely! The article is really out of hand to what is needed on Wikipedia.  If people want to learn how to setup inetd, there are thousands of sources for that (which can be linked to from here), but we don't need the steps themselves. Rurik (talk) 19:59, 9 April 2009 (UTC)

removed comments on files io since that is not the topic of this wiki. removed some other unnecessary bloat. 145.53.104.245 (talk) 19:46, 21 October 2009 (UTC)