Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
Notice: | Welcome to the Digital UNIX Conference |
Moderator: | SMURF::DENHAM |
Created: | Thu Mar 16 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 10068 |
Total number of notes: | 35879 |
I am just now learning to use Digital Unix V4.0, after having used V3.2 for a while. I'm having trouble setting up as a tftp remote host. My instructions, which were written for V3.2, say to de-comment the line in /etc/inetd.conf that references tftpd and reboot. This works. However, my notes also say that any file I write to via tftp must be in the directory denoted in the last two columns of the inetd.conf table. The table says "/usr/sbin/tftpd" and "tftpd/ tmp". The directory says that tftpd under /usr/sbin is a file, not a directory. I don't know how to proceed from here. Is there anyone here who is an expert on this? This is beyond the expertise of my group.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
9970.1 | Did you read the man pages? | NNTPD::"[email protected]" | Brian Haley | Wed May 28 1997 17:18 | 16 |
Hi, Did you read any of the man pages to see if they changed - I don't think they did. You might look at tftpd and inetd for starters. Basically, configure it exactly as your 3.2 machine (you did keep the config files, right?). Are you trying to do RIS or just tftp? Running with debug turned on (-d) or using tcpdump to get traces would be a good start if you're trying to debug a problem. For future reference, you didn't have to reboot for inetd.conf changes to take effect. Just edit the file and 'kill -HUP' the inetd pid, causing it to re-read the file. -Brian [Posted by WWW Notes gateway] | |||||
9970.2 | CECMOW::RAIKO | Thu May 29 1997 03:49 | 5 | ||
The string should contain "tftpd /tmp" instead of "tftpd/ tmp" in order to allow access to /tmp. Regards, Gleb. | |||||
9970.3 | NETCAD::MORRISON | Bob M. LKG2-A/R5 226-7570 | Thu May 29 1997 12:53 | 14 | |
Thanks for your help so far. Re .2, the filename is as you said; I entered it wrong here. Thanks for the pointer re not needing to reboot. > config files, right?). Are you trying to do RIS or just tftp? Just tftp. > Running > with debug turned on (-d) or using tcpdump to get traces would be a > good start if you're trying to debug a problem. For now, I'm only trying to open a tftp-writeable file. That is, I need to know that the file is tftp-writeable so I can rule that out as the cause of the problem in case the next attempt to tftp fails. |