Re: Why daemons are called "in.*" ?

From: Giovanni <lsodgf0@xxxxxxxxxxx>
Date: Wed, 31 May 2006 14:46:21 +0200

yaba@xxxxxxxx wrote:

Does anyone know why some daemons are called in.daemon ?
(in.named, in.tftpd, etc.)

I assume because they are not really standalone daemons but they are built to be started by inetd.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 < http://giovanni.homelinux.net/ >
.

References:
- Why daemons are called "in.*" ?
  - From: yaba

Prev by Date: Re: Suse 10.1
Next by Date: question about piping and standard output
Previous by thread: Re: Why daemons are called "in.*" ?
Next by thread: swap issue
Index(es):
- Date
- Thread

Relevant Pages

Re: filtering access via hosts.allow
... >>>AFAIK they are standalone daemons and do not get wakened via inetd. ... >> started from inetd or not, though many distro default sshd ... > ServerType inetd ...
(comp.os.linux.networking)
Re: Changes to hosts.allow do no affect to inetd daemons some times
... Since the service is marked 'nowait', inetd will handle all incoming ... Most things in /etc/inetd.conf are marked 'nowait', ... built into inetd -- or they are for RPC based services, ... the TCP wrappers support built into portmapon ...
(freebsd-questions)