[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: xinetd.d listening twice on port 69

Andy Green wrote:

Hash: SHA1

Mark Sargent wrote:
| Andy Green wrote:

|> I would find it a nice explanation if it is a bug, because my
|> understanding of how the sockets work will not allow this scenario of a
|> single process binding two sockets to the same port and listen()-ing to
|> both. Of course my understanding can easily be broken and often is ;-)

| below is the results. I have no idea what I'm looking at/for.

| xinetd    5105           root    8u     IPv4       9913
| UDP *:tf tp
| xinetd    5105           root    9u     IPv4       9914
| UDP *:tf tp

lsof shows you all the "file" type assets a process has open, sockets
being "files" for this purpose.  The lines above show that the xinetd
process 5105 does indeed hold two IPv4 UDP sockets listening on the tftp
port and so it's presumably not a netstat bug.

Maybe it's worth copying your version of

[root server html]# cat /etc/xinetd.d/tftp
# default: off
# description: The tftp server serves files using the trivial file
transfer \
#       protocol.  The tftp protocol is often used to boot diskless \
#       workstations, download configuration files to network-aware
printers, \
#       and to start the installation process for some operating systems.
service tftp
~        socket_type             = dgram
~        protocol                = udp
~        wait                    = yes
~        user                    = root
~        server                  = /usr/sbin/in.tftpd
~        server_args             = -s /tftpboot
~        disable                 = no
~        per_source              = 11
~        cps                     = 100 2
~        flags                   = IPv4

... just in case. And really just in case

cd /etc/xinetd.d
grep tftp *

- -Andy
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


Hi All,
ok, I copied the tftp file from xinetd.d to another location and rebooted. Guess what, xinetd is still listening on port 69 udp. This is weird. I can't get my head around it, eh. Cheers.

Mark Sargent.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]