I have seen words like "agents" for daemon like processes that continualy
run with a sleep.
I can think of INET type services when a request comes via a socket (an UDP
or TCP port) and the INET/XINET sends the request to the appropriate script
(or daemon or agent) to execute.
There is also child processes, spawned processes, threads, which are more
rigorous on their definitions and they come mostly from the programming
side of the family (vs marketing).
I don't think there is an ISO or standard (e.g. OSI) forcing anybody to
conform to a naming convention.
Regards,
[EMAIL PROTECTED]
NCCI
Boca Raton, Florida
561.893.2415
greetings / avec mes meilleures salutations / Cordialmente
mit freundlichen Grüßen / Med vänlig hälsning
"McKown, John"
<[EMAIL PROTECTED] To:
[email protected]
insctr.com> cc:
Sent by: Linux on Subject: Terminology question.
390 Port
<[EMAIL PROTECTED]
IST.EDU>
07/20/2005 11:31
AM
Please respond to
Linux on 390 Port
I know that something that is "always running" and not connected to a
terminal is generally called a daemon. I'm thinking of stuff like
SYSLOGD. What is the correct terminology for something which is started
by a daemon in response to a user request? For example, you do an ssh to
a Linux system. This connects to the sshd daemon. The sshd daemon then
fork()s and eventually, a shell is opened. What is the proper
terminology for the processes which are forked from the original daemon.
Are they also called daemons?
I am trying to use "proper" terminology for something that I am looking
at writing. Basically, it will work similar to telnet (xinetd listens on
the port, then forks the telnet program). It isn't telnet, but I want to
set it up so that each user who comes in gets their own process, as
opposed to something like a database where everybody connects to a
single, perhaps multithreaded, process.
Thanks.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology
This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message
is not the intended recipient or an agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
