Talk:List of Unix daemons

Comment
This partial list is rather pointless, given that it makes no effort to explain *which* Unix uses these daemons. It should be relegated to a list in the daemon article. --Joy &#91;shallot&#93;   22:11, 12 Jun 2005 (UTC)

It is in deed pointless. In modern Unix variants there is a multitude of daemons for all kinds of stuff (think dbus etc.). The most daemon like programms are not even listed in the posix standard documents. It might however be helpful to create a List of "classic" unix daemons. i.e. services that where (or are) offered in a wide variety of unix like systems. init cron and the nfs stuff seems fitting. httpd not so much. 84.179.165.176 (talk) 18:41, 17 May 2010 (UTC)


 * I agree that while this article as it exists is pointless, it could be narrowed to "top / critical / core" services. Also, I propose that the article ("Unix_daemons") be a redirect to Unix-like_daemons or even Unix-like_Services as UNIX is a copyrighted term. I would love to see "popular (>1% usage globally) examples of daemons that provide these services".  bad boy jamie    talk 06:57, 8 June 2013 (UTC)

I did add some additional information, and modified my text to say Unix-like, although I do agree with most of you, this list is a little weird. I will work on it a little more, maybe I can try to incorporate some better information and help it a little more. This information is useful, just need to find the right balance. User:Jessicab8110 16:56 1 Feb 2024 (US EST)

Article has been included in Wikipedia
The article was deemed worthy for inclusion in Wikipedia: the result of the AfD was to keep it, because it's functional and appropriate as a Wikipedia article per Wikipedia notability guidelines, and its inclusion is congruent with building Wikipedia. Northamerica1000 (talk) 08:42, 20 September 2011 (UTC)

TALK questions
bad boy jamie   talk 07:10, 8 June 2013 (UTC)
 * 1) Should this article be rewritten from ground up?
 * 2) Should examples of services (e.g. daemons > 1% global usage) be listed?
 * 3) Should the exclusionary "Unix" be substituted for Unix-like?
 * 4) Should only services recognized in /etc/services (SYSV, POSIX) be listed?   Should all listed, be included?
 * 5) Should this be a static list, or are professionally-based statements of relevance allowed?

RFC comment by User:Staszek Lem

 * (1). Huh? It is a list which is a list is a list, right? If you have any ideas to make the structure of the list more useful, please explain. If you want to improve item summaries, this is hardly "from ground up". Please be more specific what you have in mind.
 * (2) What is service you are talking about? This list is list of unix daemons, not all kinds of services. As for usage examples, I say "no". They belong to main article. (Lists of) examples tend to mushroom/spam/have NPOV+REF issues, better be confined to specific pages.
 * (3) No. This is the list of Unix daemons, which also may happen to have the same name/function in "unix-like" systems. One may well have List of additional Linux daemons (or a better title) for non-unix linux daemons (if such exist). Staszek Lem (talk) 18:18, 10 June 2013 (UTC)
 * (4) Per wikipedia rules the things to be listed : (4a) - standard unix daemons (i.e., installed as part of OS), per WP:RELEVANCE (4b) daemons notable enough to have wikipedia articles, per WP:LIST
 * (5) There are no static lists in wikipedia. What do you understand under "statement of relevance"?

Staszek Lem (talk) 18:18, 10 June 2013 (UTC)


 * I think we should start by defining a clearer criteria. First of all, the world "Unix" is an ill-defined term:
 * Does it refer to the "classical" Unix (e.g. System V)? (I think this would make the article rather obsolete and pointless.)
 * Does it refer to the proprietary and/or open source derivatives? The BSDs have tons of derivatives -- do we include daemons shipped with those? If not, where do you draw the line?
 * And Mac OS X, which is a derivative of Unix?
 * Does it include "Unix-like" systems like Linux? I see you suggest above that should be "no", although the article says "yes"
 * What "daemons" are included? You said "standard unix daemons (i.e., installed as part of OS)", "daemons notable enough to have wikipedia articles", although that's your interpretation and not written anywhere in the article. -- intgr [talk] 20:20, 10 June 2013 (UTC)
 * I said what I said because these are wikipedia practice IMO. While there are tons of derivatives, I don't think there are tons of OS daemons. Even if there are, if they are mentioned in wikipedia somewhere, they must have either articles or redirects. Staszek Lem (talk) 20:17, 17 June 2013 (UTC)


 * This article also lists ancient daemons like biod, swapper, syncd, vhand, which don't have Wikipedia articles and aren't included in any modern system. -- intgr [talk] 20:20, 10 June 2013 (UTC)
 * Wikipedia is encyclopedia, not the most recent version of a user guide, right? "Digital obsolescence" should have no power. If some daemon did something useful in the past, it deserves an article (or a section): what it did, who does its job now (or whether its job no longer exists), etc. Staszek Lem (talk) 20:17, 17 June 2013 (UTC)


 * FreeBSD has some specific daemons like newsyslog, hastd, devd. Solaris has Service Management Facility. OpenBSD has OpenBGPD, OpenNTPD.
 * OS X includes Apache web server (which sometimes calls itself "httpd", but there's also the CERN httpd), PostgreSQL, BIND, ntpd, samba, CUPS. MySQL (mysqld) used to be included. Are these Unix daemons? Because most work equally well on every modern OS.
 * How about OS X specific daemons? launchd, Apple Remote Desktop, Apple Push Notification Service, Apple Filing Protocol server, Software Update service, their VPN server?
 * Why exclude popular daemons like nginx, lighttpd, thttpd, PowerDNS, Postfix etc, on the basis that they weren't chosen to be included in the default install? If anything, these are more Unix-ish than Apple's stuff.
 * And I'm just a Linux user, I don't know half the things about proper "Unices". I simply find this criteria unworkable. If you ask me, it's more like "totally arbitrary collection of software". Which is probably why nobody has dared to touch this article for years (last time an item was added was in 2009 October).
 * Apologies for being bitter. Can you help with coming up with a better criteria? -- intgr [talk] 20:20, 10 June 2013 (UTC)


 * Comment: Whatever the intention or intended function, the article or list in its current form is not foreseeably likely to be useful. How is it likely to be useful and stay useful? It lacks context. A list article referring to any dynamic set is less than half as good as its standard of maintenance, and I see no sign of maintenance in this one. Suppose some monastic masochist undertook to maintain it till he got a life/wife? What would the future of the article be? Unless some company or group of companies in that segment of the market undertook to maintain a set of such articles, I don't see it going anywhere. I certainly am in no position to help, but though I have no objection to list articles -- I actually approve of them in principle -- I don't think that this one deserves its bit space unless the situation changes. JonRichfield (talk) 06:50, 11 June 2013 (UTC)
 * Well, what you wrote is an ubiquitous problem of wikipedia. And there is the only solution: a volunteer to do this job. Staszek Lem (talk) 20:17, 17 June 2013 (UTC)


 * Comment I do think the list has some use, I'm quite surprised that we don't have a Category Unix daemons which is a well defined group of programs. There is a case for a list as well as some of the deamons like crond don't have separate articles so would not be findable through the category system. If we look at List of Unix utilities we see it has a "First appeared" column which lists the system it was first used on. A similar column for system distinguishing BDS/System V/linux and possibly Mac would be useful. Not sure about Mac specific ones, maybe better in an OSX specific article. Distinguishing between general system and application specific ones is also a good thing to do, but I would not want to go over the top on the applications. I'd be happy with general classes, the httpd entry could mention the varients, but the detail can be found on the httpd page. I don't think we need to go into the command line arguments.--Salix (talk): 15:45, 15 June 2013 (UTC)

I would not suggest to exclude any daemons from this list unless the list becomes longer than 1-2 hundred items. When this happens, one may look at the list and come with ideas how to split it. For starters, one may look at List of Unix utilities (criteria, format, etc.). Staszek Lem (talk) 20:17, 17 June 2013 (UTC)


 * Comment I feel there is a need for a list of Unix[-like] daemons, but I'm not sure of the best format. A stand-alone article, as noted above, has its problems. Having the same list as part of the Daemon (computing) article, with a redirect from here, could be a better solution. Or, I like Salix's suggestion to add a Category Unix daemons. Given the choice I'd probably put all our eggs in one basket (Daemon (computing)) and then guard that basket (i.e. maintain the article). Then add the category. -- Dan Griscom (talk) 13:35, 22 June 2013 (UTC)

put all our eggs in one basket (Daemon (computing)) and then guard that basket (i.e. maintain the article). Then add the category [ i.e. Category Unix daemons - ''Ed. (yoyo)'' ].
 * Comment I concur with most of the responses given by user Staszek Lem. However, I also think the suggestions by Salix and Dan Griscom have merit, and would go along with Dan Griscom's preferred solution:
 * I do think that this article: List of Unix daemons is best as a linked article amplifying the content of the more general Daemon (computing) article. It might be only one of several such lists, depending on relevance and interest: why not also link to such as List of Linux daemons and List of OS/X daemons, supported by Category Linux daemons and Category OS/X daemons as required?  yoyo (talk) 06:47, 25 June 2013 (UTC)


 * It seems like a kind of pointless article to me, especially given its current state, but I can see how it might be turned into a somewhat useful resource. In particular, I like Salix's suggestions.  I would prefer we didn't start listing minutiae like oddball daemons used only by one Linux distribution.  That OCD level of attention to detail just makes for an unreadable article.  To be listed, daemons would have to be notable and used across multiple UNIX-like operating systems, not just existent.  Restricting this list to notable services sounds good, too.  ntp, smtp, nntp, httpd, etc.  If people want to list common implementations (Apache, Sendmail/Postfix, CUPS, etc), I guess that would be OK, as long as it doesn't take over the entire article. NinjaRobotPirate (talk) 13:19, 30 June 2013 (UTC)


 * 8 years later, I arrive here with the same question. As far as I'm concerned, an article must serve a clear purpose: readers reading an article must clearly understand its scope and quickly be able to determine whether their particular question(s) are within scope. That purpose isn't clear to me in this case. The reader will need to refer to Unix daemon, which unfortunately redirects to a Daemon (computing) article that lacks a clear scope, and fails to explain some crucial points, such as the purpose of daemons. Without a good understanding of what is meant by Unix or by daemon, the present article lacks a clear scope as well. How to fix this:
 * Have a general article about Unix daemons that discusses the daemons on Unix and Unix-like operating systems: their purpose, how they work, and typical examples, ranging from 1970s Unix to today's Unix-like systems.
 * Only if the examples section in that article grows too big or too detailed, retain it as a separate article. It should never be just a list, but a table, listing, for each example, the daemon's name, the year and Unix version in which it was introduced, some more examples of versions of Unix(-likes) that used or use it (with references), and its purpose. Both application-specific daemons and generic daemons such as inetd and dbus-daemon should be in here.
 * It would be nice, but not strictly necessary, to also have a more general article on "daemon"/"service" processes in computing, and their relationship with services. This is hard to write, because the concepts and terminology tend to be quite OS-specific. Rp (talk) 15:06, 8 April 2021 (UTC)