3.1.3 Using environment variables to define a JP1/FTP environment
You can use the OS's environment variables to define some of the JP1/FTP environment settings. The specified settings take effect when you start the JP1/FTP daemon (jftsd) from the environment for which you have set the environment variables. If you want to start JP1/FTP automatically using /etc/opt/jp1_fts/startup, define the environment variables in /etc/opt/jp1_fts/startup.
- Organization of this subsection
(1) Environment variables that can be set
The following table lists and describes the environment variables that can be set.
Environment variable name |
Value |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- #1
-
Not supported in AIX.
- #2
-
When ON is specified, an auto-start program (process) can become a superuser even if it is started as an ordinary user.
- #3
-
Note the following about specifying ON:
-
An attempt to transmit a file whose size exceeds 4 gigabytes will result in an error.
-
If a file whose size is less than 4 gigabytes is transmitted to a Windows system in the ASCII mode, the size of the resulting file might exceed 4 gigabytes in the Windows system. Therefore, when JP1/FTP is used as an FTP program in a Windows system, the maximum file size set in the Windows version of JP1/FTP might be exceeded during transmission.
-
- #4
-
In the following circumstances, a timeout might occur at the FTP client and could result in abnormal termination of the transmission:
-
JP1/FTP-to-JP1/FTP transmission
-
File transmission from an FTP server to an FTP client
-
Transmission of large files
-
ASCII mode
-
Size checking function is used
A timeout might occur because it takes time for the FTP server to calculate the file size, resulting in a delay in transmitting the response message. If this becomes a problem, either increase the timeout value for waiting to receive data or execute transmission without using the size checking function.
-
- #5
-
Although JP1/FTP does not limit the size, transmission might fail due to OS limitations.
- #6
-
Note the following when the transmission size is 4 gigabytes or greater:
-
If the size of the transmission file is to be referenced by a user program using the API library (other than in Linux (IPF version)), you must modify the API library. For details, see 7. API Library.
-
In the transmission log list displayed by ftshist and the list displayed by the ftshistory command, the columns might be shifted in the case of transmission of a large file.
-
Operations-Manager Agent versions earlier than 10-00 do not support a transmission size of 4 gigabytes or greater. Consequently, if the Operations-Manager Console is connected to an Operations-Manager Agent earlier than version 10-00, and if an attempt is made to reference a transmission log whose transmission size is 4 gigabytes or greater, the displayed value will be smaller than the actual transmission size.
-
- #7
-
When ON is specified and the user program using the API library functions (fts_ftp_syn_request_ex() and fts_ftp_asyn_request_ex()) is linked to a static library version earlier than 09-00, you must re-link the library. If you do not re-link the library, the API library functions will return an error.
The old-format API library functions (fts_ftp_syn_request() and fts_ftp_asyn_request()) cannot use a secondary group. If ON is specified, the old-format API library functions will return an error.
- #8
-
When ON is specified and the FTP server receives the corresponding command, it sends the message 500 'command-name': command not understood to the FTP client.
Help for the corresponding command is not disabled.
- #9
-
By default, the programs that start automatically when transmission ends are started with SIGHUP, SIGCHLD, and SIGTERM masked with sighold(). Consequently, the programs that start automatically when transmission ends hold these signals when they are received.
- #10
-
When ON is specified, you cannot receive a file that is being sent or send a file that is being received, but you can send the same file concurrently.
- #11
-
The timing for applying data to the disk is normally determined by the OS. However, this function forcibly applies data to the disk according to the JP1/FTP timing. Be extremely careful about using this function, since enabling it might cause one of the following performance-related problems:
-
The transmission speed might decline compared to when the function is disabled.
-
File access by other programs might be adversely impacted.
-
- #12
-
Even if the file to be transmitted is smaller than 2 gigabytes, if there are already 2 gigabytes or more in received files, an error will occur if this environment variable is not specified on the machine where these received files are located.
(2) Examples of environment variable definition
(a) JP1FTS_LS_OPTION setting example
This example specifies -lgA in the ls option:
- In csh:
>setenv JP1FTS_LS_OPTION -lgA >jftsd
- In sh:
>JP1FTS_LS_OPTION=-lgA >export JP1FTS_LS_OPTION >jftsd
(b) JP1FTS_LARGEFILE2 setting example
This example enables the transmission of a file exceeding 4 gigabytes.
- In csh:
>setenv JP1FTS_LARGEFILE2 ON >jftsd
- In sh:
>JP1FTS_LARGEFILE2=ON >export JP1FTS_LARGEFILE2 >jftsd