NAME | SYNOPSIS | API RESTRICTIONS | DESCRIPTION | RETURN VALUES | ERROR MESSAGES | NOTES | ATTRIBUTES
#include <arpa/ftpd/systemFilesys.h>int systemReceiveAscii(FtpConn * conn, FILE * instr, char * name, off_t offset);
The function or functions documented here may not be used safely in all application contexts with all APIs provided in the ChorusOS 5.0 product.
See API(5FEA) for details.
These functions read data from FILE instr , up to the EOF . They store the data in a file specified by name , starting at an offset value ( offset ). conn->byte_count is incremented by the number of bytes received.
If the file specified by name does not exist, it is created.
If the file specified by name already contains lines or byte streams outside of the region defined by offset and offset + <number-of-bytes-received> ), these lines or byte streams are not changed.
The effect of storing data in a file is implementation-dependent.
systemReceiveAscii takes lines of text (in the format defined by FTP) from the input stream and converts them to the file representation of text lines. In a traditional UNIX implementation, when systemReceiveAscii has successfully completed, the same arguments are used in a call to systemSendAscii (3FTPD) . This function sends a sequence of lines, beginning with the set of lines that were just received.
systemReceiveBin stores the data exactly as it receives it from the input stream. In a traditional UNIX implementation, when systemReceiveBin has successfully completed, the same arguments are used in a call to systemSendAscii (3FTPD) . This function sends a stream of bytes, beginning with the stream of bytes that were just received.
These routines periodically call ftpdOob (3FTPD) to check for urgent conditions on the control line. conn->byte_count is updated when ftpdOob (3FTPD) is called.
Returns 0 if successful, -1 otherwise.
Problem with instr .
Resource allocation problem.
File write problem.
File seek problem.
File name problem.
The ftpdOob (3FTPD) routine may longjmp (3STDC) to an older stack frame, instead of returning. For information on the necessary precautions, refer to the ftpdOob (3STDC) manual page.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Interface Stability | Evolving |
NAME | SYNOPSIS | API RESTRICTIONS | DESCRIPTION | RETURN VALUES | ERROR MESSAGES | NOTES | ATTRIBUTES