HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

Action:
Ensure that the full path name, which the client is requesting from the server, exists within the
tftp directory or in a path specified with the tftpd command.
For example, if the tftp directory is /home/tftpdir and the TFTP client is requesting the file
/usr/lib/X11/700X/C2300A, the file must exist as
/home/tftpdir/usr/lib/X11/700X/C2300A.
If no entry exists for the user tftp in the /etc/passwd file, you must specify at least one file
or directory with the tftpd command. Make sure that you specify the full path name when
attempting to get a file from a directory specified with the tftpd command.
Symptom:
File transfer fails with Access Violation, Permission Denied, or TFTP Error Code 2
message.
Cause:
tftpd does not have permission to read the file.
Action:
If the transfer is a get operation where the client is attempting to read the file from the server,
then the server does not have read permissions on the file that it is trying to send. Ensure that
the file the client is reading has read permissions for the user tftp. For example, if the client
attempts to read the file xterm, xterm must have the permission 0400 and must be owned by
the user tftp.
$ ll /home/tftpdir/xterm
-r-------- 1 tftp guest 438 May 10 1989 xterm
During a put operation (which is not something a BOOTP client does as part of the BOOTP
protocol), an error message Access Violation, Permission Denied is displayed when a
file does not have write permission on the server to write to the file. If the server receives a file,
it must exist and be writeable by the user tftp. For example, if a tftp client is sending the file
named fontlist, the file must have permission 0600 and must be owned by tftp:
$ ll /home/tftpdir/fonts
Error Logging
This section explains the error messages that bootpd logs through syslogd. The following
logging levels are discussed in this section:
• “Information Log Level” (page 114)
• “Notice Log Level” (page 115)
• “Error Log Level” (page 116)
You must set the bootpd debug level for logging these messages. You can set bootpd debugging
level using the -d option.
Information Log Level
The following describes the messages logged at the syslogd information log level:
• exiting after time minutes of inactivity
If bootpd does not receive a bootrequest within time minutes (the timeout set with the -t
option), it issues this message and exits.
• reading configuration_file
reading new configuration_file
114 Configuring the BOOTP and TFTP Servers