Davide Grandis wrote: > > Tried but with no luck, exact same behavior! :-( > > tftp-server broken? > Just to make sure, is the /tftpboot directory set to perms 777? -Ross > On Sep 13, 2007, at 6:26 PM, Ross S. W. Walker wrote: > > > Davide Grandis wrote: > >> > >> Even more, rebooted (just to be sure!:-)) ) > >> > > > > It's working on my server and the only difference is instead of: > > > > server_args = -s -c /tftpboot > > > > I have: > > > > server_args = -c -s /tftpboot > > > > Maybe order is important here... > > > > -Ross > > > >> > >> On Sep 13, 2007, at 6:07 PM, Ross S. W. Walker wrote: > >> > >>> Davide Grandis wrote: > >>>> > >>>> Hi all, > >>>> > >>>> I'm trying to setup a TFTP server to serve as repository for the > >>>> config of all my Cisco network devices. > >>>> > >>>> As per the the tftpd man, I've added the "-c" option > into the /etc/ > >>>> xinetd.d/tftp (as follows) but I still cannot get write access > >>>> (unless the file is already present). > >>>> > >>>> [root at chl1 ~]# cd /etc/xinetd.d > >>>> [root at chl1 xinetd.d]# cat 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 > >>>> { > >>>> disable = no > >>>> socket_type = dgram > >>>> protocol = udp > >>>> wait = no > >>>> user = root > >>>> server = /usr/sbin/in.tftpd > >>>> server_args = -s -c /tftpboot > >>>> per_source = 11 > >>>> cps = 100 2 > >>>> flags = IPv4 > >>>> } > >>> > >>> Did you give xinetd the HUP signal after modifying the file? > >>> > >>> > >>> > >>> <snip> > >>> > >>> > >> > _____________________________________________________________________ > >> _ > >>> This e-mail, and any attachments thereto, is intended only > >> for use by > >>> the addressee(s) named herein and may contain legally privileged > >>> and/or confidential information. If you are not the > >> intended recipient > >>> of this e-mail, you are hereby notified that any dissemination, > >>> distribution or copying of this e-mail, and any > attachments thereto, > >>> is strictly prohibited. If you have received this e-mail in error, > >>> please immediately notify the sender and permanently delete the > >>> original and any copy or printout thereof. > >>> > >>> _______________________________________________ > >>> CentOS mailing list > >>> CentOS at centos.org > >>> http://lists.centos.org/mailman/listinfo/centos > >> _______________________________________________ > >> CentOS mailing list > >> CentOS at centos.org > >> http://lists.centos.org/mailman/listinfo/centos > >> > > > > > ______________________________________________________________________ > > This e-mail, and any attachments thereto, is intended only > for use by > > the addressee(s) named herein and may contain legally privileged > > and/or confidential information. If you are not the > intended recipient > > of this e-mail, you are hereby notified that any dissemination, > > distribution or copying of this e-mail, and any attachments thereto, > > is strictly prohibited. If you have received this e-mail in error, > > please immediately notify the sender and permanently delete the > > original and any copy or printout thereof. > > > > _______________________________________________ > > CentOS mailing list > > CentOS at centos.org > > http://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.