Better yet, setup ipf to only allow connections to the tftpd port from
whichever router needs a load image, then makes the changes below.  This
way you can keep tftpd enabled at all times in inetd.conf and just control
access to it via ipf.

diana

On Sun, 9 Apr 2000, David Brownlee wrote:

> 	I just enable it in inetd.conf, hup it, use it, comment it back
> 	out, and hup again.
> 
> 	Thinking about it it would be nice to be able to run it
> 	standalone. Someone would just need to copy the code from another
> 	daemon. If you want to submit a PR with the code that would be
> 	great, otherwise if you want to submit a PR noting it so it
> 	doesn't get forgotten...
> 
> 		David/absolute
> 
> On Sat, 8 Apr 2000, Paul Hoffman wrote:
> 
> > At 03:29 PM 4/8/00 -0400, mcmahill@mtl.mit.edu wrote:
> > >usually you'd start tftpd from inetd by turning it on in /etc/inetd.conf
> > 
> > Boy, I would hope that the current tftpd does not *require* that. I needed 
> > it for a single application (updating my router) and did not want to run it 
> > forever. I just switched to a different box not running NetBSD to do what I 
> > needed.
> > 
> > 
> 
>