22 lines
3.3 KiB
HTML
22 lines
3.3 KiB
HTML
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>daemon</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../D.html" title="D"/><link rel="previous" href="../D.html" title="D"/><link rel="next" href="daemon-book.html" title="daemon book"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">daemon</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="../D.html">Prev</a> </td><th width="60%" align="center">D</th><td width="20%" align="right"> <a accesskey="n" href="daemon-book.html">Next</a></td></tr></table><hr/></div><dt><a id="daemon"/><dt xmlns="" id="daemon"><b>daemon</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="pronunciation">/day´mn/</span>, <span xmlns="http://www.w3.org/1999/xhtml" class="pronunciation">/dee´mn/</span>, <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> [from Maxwell's Demon, later incorrectly retronymed as ‘Disk
|
||
And Execution MONitor’] A program that is not invoked explicitly, but
|
||
lies dormant waiting for some condition(s) to occur. The idea is that the
|
||
perpetrator of the condition need not be aware that a daemon is lurking
|
||
(though often a program will commit an action only because it knows that it
|
||
will implicitly invoke a daemon). For example, under
|
||
<a href="../I/ITS.html"><i class="glossterm">ITS</i></a>, writing a file on the LPT spooler's directory
|
||
would invoke the spooling daemon, which would then print the file. The
|
||
advantage is that programs wanting (in this example) files printed need
|
||
neither compete for access to nor understand any idiosyncrasies of the LPT.
|
||
They simply enter their implicit requests and let the daemon decide what to
|
||
do with them. Daemons are usually spawned automatically by the system, and
|
||
may either live forever or be regenerated at intervals.</p></dd><dd><p>Daemon and <a href="demon.html"><i class="glossterm">demon</i></a> are often used
|
||
interchangeably, but seem to have distinct connotations. The term
|
||
<span class="firstterm">daemon</span> was introduced to computing by
|
||
<a href="../C/CTSS.html"><i class="glossterm">CTSS</i></a> people (who pronounced it <span class="pronunciation">/dee´mon/</span>) and used it to refer to
|
||
what ITS called a <a href="dragon.html"><i class="glossterm">dragon</i></a>; the prototype was a
|
||
program called DAEMON that automatically made tape backups of the file
|
||
system. Although the meaning and the pronunciation have drifted, we think
|
||
this glossary reflects current (2003) usage.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="../D.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../D.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="daemon-book.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> daemon book</td></tr></table></div></body></html>
|