Hi John Paul, Glad that it finally worked out -- but remember to isolate access to a writable tftp server as it can lead to very ugly security issues.
I was a bit short on message concerning xinetd the other day -- I suppose that is somewhat synonymous to kernel modules, that is, that kernel modules are loaded and unloaded depending on whether they are needed. xinetd's approach to services is similar -- services are launched dynamically when they are requested. It is possible for your to configure tftpd, pop and other services to be loaded continuously in memory, ready to service eventual requests. from a resource standpoint, this may not be desirable, particularly if the service is used irregularly. so larger services (sendmail, apache, named, etc.) are loaded and forked into the background ready handle requests, and xinetd stands ready to start and stop "smaller" services that are used irregularly. further, xinetd services are typically compiled using tcp wrappers -- an additional method of securing services from unauthorized access. for instance, if your tftp server is going to be used uniquely to backup/restore cisco ios and router configs, than you can secure the service to allow only access from your router(s). For good explanation, see the Chapter 8 in the Red Hat 8.0 Reference Guide. Cheers Christopher CUSE RHCE/CCNA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John-Paul Delaney Sent: Tuesday, March 25, 2003 9:06 AM To: [EMAIL PROTECTED] Subject: RE: understanding tftp Bravo Christopher that did it! A big thanks... /j-p. "christopher cuse" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 24/03/2003 15:29 Please respond to redhat-list To: <[EMAIL PROTECTED]> cc: Subject: RE: understanding tftp Hi John Paul I see your error now -- you have placed a "-l" argument to the server: -l Run the server in standalone (listen) mode, rather than run from inetd. In listen mode, the -t option is ignored, and the -a option can be used to specify a specific local address or port to listen to. remove the -l argument and try again! Cheers Christopher CUSE RHCE/CCNA [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John-Paul Delaney Sent: Monday, March 24, 2003 11:56 AM To: [EMAIL PROTECTED] Subject: Re: understanding tftp Thanks Gene... I completely mis-interpreted that output :( . This is the contents of the /etc/xinetd.d/tftp file: disable = no socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s -c -l /tftpboot per_source = 11 cps = 100 2 How then, is the tftp server started? thanks /j-p. Gene Yoo <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 21/03/2003 23:24 Please respond to redhat-list To: [EMAIL PROTECTED] cc: Subject: Re: understanding tftp John-Paul Delaney wrote: > tftpd seems to be running ok: > root 20212 0.0 0.3 3544 632 tty1 S 07:50 0:00 grep tftpd if you did ps auxw | grep tftpd like above, that's all your going to see. your tftpd is not up and running. run chkconfig --list tftpd -- <<gyoo [at] attbi [dot] com>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iQCUAwUBPhxERRxoVYCzmrKXAQJK5gP3Y7CTsFyKpEz2p5W4GWI9+qSm+kWfdJ0R xNlma0Ma9rAL/OBJcZMo5IXyXas+3Edogbv4Al6dIf8lot1WS0Iaxxl/cg2f7gf+ otf7LfNpZDE/6OzR7A1qN6baPMLSjGzywwQWMfSVuWWb6kGQxMsA13Kn68G7Ozxs 5CODZqUPyg== =AolA -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
