-----BEGIN PGP SIGNED MESSAGE-----
> From: Robert Fendt [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 05, 2000 10:52 AM
> Subject: ftpd, telnetd
...
> my problem:
> ftp works only from host1 to host2, not from host2 to host1
> telnet works in neither way :(
check out if you can establish connections from host1 to host1 and
from host2 to host2. If these fail also, your daemon is not running.
If these succeed, you should check your /etc/hosts.allow or
/etc/hosts.deny files.
...
> my question(s):
> - how can i check for a running daemon?
servers for linux accept connections. The two main ways are these,
but chances are *really high* for ftp and telnet you can skip item 1.
and go forth to item 2.
1.
There's a server running that listens to the socket (port) on which
the client will connect. e.g. standard ftp=21, standard telnet=20,
standard http=80. These servers are called daemons since they remain
"slumbering" until a connection is attempted on the socket (port)
being listened to. You can detect these daemons in two ways:
a. You know what's the name of the server. Then you can detect
whether it is running by executing a `ps` command.
$ ps aux|grep daemonname
Where daemonname is replaced by the name of the
server/daemon-executable.
e.g.
$ ps aux|grep httpd
b. You know the socket (port) on which the server/daemon should be
listening. You can check whether a process is listening on that port
by executing following command:
$ netstat -a |grep LISTEN
your servers port number should be mentioned in the 4th field behind
the ':'
Since most webservers are apache webservers and most apache
configurations run the webserver as a daemon (see
/etc/httpd/conf/httpd.conf - item ServerType)
These servers/daemons have to be launched at boot-time of the
computer and run (sleep) permanently so can always be found within
`ps`.
They are being activated by boot-scripts. These system
initialisation-scripts can be found in OR
/etc/rc.d/
OR
/sbin/init.d/
to be certain, check out the output of
$ grep '^si' /etc/inittab
So now you know where to cause extra daemons to be launched
2.
There's a "super-socket" process (a daemon) that listens to a
collection of sockets (ports) for entering requests and when such a
request is encountered, that super-socket process launches the
specific server-executable and passes the initiated connection to
that server.
This super-socket process is (almost always) called inetd (stands for
Internet Daemon). in the combination of /etc/services and
/etc/inetd.conf it's configured what sockets inetd should be
listening to and what the corresponding server (that should be
launched when an incomming connection is attempted on a certain
socket) for a certain socket is).
So check out /etc/inetd.conf to see if the socket corresponding to
your redoupted service (ftp or telnet) is activated (not commented
out). Furthermore check out /etc/services to make certain you have
the correct socket-number (port) defined and last of all, you'd
better be certain your server (6th field in /etc/inetd.conf) is
working properly.
> - how can i start a daemon (tried "start-stop-daemon...", no
> success)
> manually?
> - how can i start a daemon via "rc..." script @ boottime?
I'd say you read the
> - how can i find out if a daemon is installed
******* Groetjes vanwege ***** Greetings From *******
Dieter Demerre - http://www.angelfire.com/de/ddemerre
[EMAIL PROTECTED] - [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
iQEVAwUBORLWy+H7QfvhLrpDAQFj7gf/Xgnt1vWmHOZAdcrrHYdUgajFMFHpVAtt
+FUbwE5wuPweDbvgZ6bxX12AjieD4QsebJX2f2e7nd/F+E5heRfgqJFrSd/0sJ4X
DEbN0IHBv+Ui2utmTPctu1dTtruSmoPHTXo9imBdPTVc9oDPj00D+KassYPdyI5G
0btZ1mPdzjizv1RB91M64DFj6m3YP/DxS/YS32P5u4Jgc+BfP+Bg25gGaYJXdqFP
6O8PoKo1mnnimHaJg5VudU+2v4YQJ+uk1UWD/tKZkVQwJwD8GesFux9fuNs3nk6A
vkKmY1UOl2Q/m24TPduFvF6oavIOrH4wfjLmWsNUhPBrCZ6000Nj7Q==
=Olph
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
