NAME | SYNOPSIS | DESCRIPTION | NOTES | ATTRIBUTES
#include <arpa/ftpd/ftpd.h>void reply(FtpConn * conn, int number, char * format, ... );
These three routines all issue a message to the client with an associated condition code. These routines are used by the FTPD library as well as by the application-side routines to report the result of an operation. The message and the following arguments follow the same rules as printf(3STDC) . The number argument is defined by the FTP protocol to reflect the reason for the message being issued. For each routine, only certain numbers are valid, as defined by RFC 959. Each application-side routine manual page lists a number of valid replies along with the type of reason to issue each of them. The lists are not exhaustive, the ones mentioned in the manual pages are those actually used by the BSD implementation. If you require other reply types, check in RFC 959. The reply and perror_reply functions are final, only one of either type should be called per invocation of any application-side routine. The difference between reply and perror_reply is that perror_reply automatically adds the standard string implied by the current value of errno. The lreply function should be used if a multiple-line reply is required. Multiple lreply() calls can be used, followed by one final reply() .
Not all routines are expected to issue an error reply. Only systemUser (3FTPD), and systemPass (3FTPD) can supply an OK reply, by using lreply . The final lreply is supplied by the FTPD library. Supply an error or OK reply only if the manual page mentions one.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Interface Stability | Evolving |
NAME | SYNOPSIS | DESCRIPTION | NOTES | ATTRIBUTES