xinetd.d listening twice on port 69

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Sargent wrote:


| [root at localhost tftp]# cat /etc/xinetd.conf
...
| service tftp
| {
|        socket_type     = dgram
|        protocol        = udp
|        wait            = yes
|        user            = root
|        server          = /usr/bin/tftp
|        server_args     = -c -s /tftpboot
|        disable         = no
|        per_source      = 11
|        cps             = 100 2
| }
| Ok, now, how does that get there..? I certainly didn't put it there. Is
| it put there by default by another process..? Cheers.

Shouldn't be.  This idea of a directory of config files was invented to
allow optionally present stuff to easily add and remove its personal
config from the main program without having to parse a single master
config file and append / rip bits out of it.  It's clear that the tftp
package does generate its /etc/xinetd.d/ tftp file for its config.  So
it's hard to understand it would also append its config to the master file.

Anyway, rip out the appended stuff from /etc/xinetd.conf and restart the
xinetd service and I guess you'll be okay.

But I am still bemused by the two listening sockets on the same port
being possible.  Maybe it is some kind of cool load balancing feature I
never heard of.  Can anyone else here explain how it can be?

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

iD8DBQFCU5xDjKeDCxMJCTIRAm4FAJ4msaizDJzo3+RWAnCmoy9KwsyjigCdHTJw
EFHYw6pYB5TJOxbQoWj+S6w=
=J8k0
-----END PGP SIGNATURE-----