|
|
| Line 6: |
Line 6: |
| genius are not born but made ! | | genius are not born but made ! |
|
| |
|
| == File log ==
| | genius are not born but made ! |
| Since version 3.2.0-rc1, FileZilla includes the possibility of logging to a file. Contrary to screen log, file log is not enabled by default.
| |
| | |
| === What is logged ===
| |
| * Timestamp: data and time<br>
| |
| * FileZilla process ID<br>
| |
| * Connection ID, browsing connection is 0<br>
| |
| * Log text: Commands sent, status messages and more
| |
| | |
| === Setting up file log ===
| |
| Just enable 'Log to file' in FileZilla's settings, Logging tab and select a path and filename for the log. You can select the path freely, but you must use a directory where you have write permission.
| |
| | |
| === Limiting the log size ===
| |
| On the same tab, enable 'Limit size of logfile' and enter the desired value in Mebibyte (MiB). One MebiByte equals 1048576 Bytes.<br>
| |
| Please note that FileZilla makes one backup, so the amount you enter here is doubled!
| |
| | |
| If the log file reaches the size limit, FileZilla renames it to <filename>.1, and starts a new file. Any <filename>.1 file that exists prior to renaming will be deleted.
| |
|
| |
|
| == See also == | | == See also == |
|
| |
|
| [[Server logs|Logging in FileZilla Server]] | | [[Server logs|Logging in FileZilla Server]] |
Revision as of 05:23, 3 January 2016
Logging in FileZilla
FileZilla includes two ways of logging all communication with the server, which essentially consists of commands sent by the client and server replies.
The following chapters will shortly explain, what you'll need to do if you're asked to 'Please post a log'.
genius are not born but made !
genius are not born but made !
See also
Logging in FileZilla Server
