Small reminder: Available sections in hfs.events ( hfs.exe build 232)
[start]
-->> Launched at every time hfs.exe is executed
-->> you can put in this section some macro as {.set ini|...... .}
[quit]
-->> before hfs.exe is closed
[server start]
-->> Lauched every time hfs is switched ON (key F4 or macro {set ini|active=yes.} )
[server stop]
-->> Lauched every time hfs is switched OFF (key F4 or macro {set ini|active=no.} )
[connected]
-->> similar to the 'connected event' in log
[disconnected]
-->> similar to the 'disconnected event' in log
[request]
-->> launched every time hfs becomme a request from a browser
[unauthorized]
-->> launched before the 'unauthorized' section of hfs.tpl
[on macro rename]
-->>
perform renaming via {.rename.} macro. ****************************************************************
[archive name]
%archive-name%
optional: %mode% ->> %mode% is 'selection' or 'folder'
-->> used to rename a tar file before sending it to the user
*******************************************************************************
[download]
-->> launched when anybody download a file or a TAR archive
[download name]
%item-name% (it is the default value to be used or nothing)
-->> can be used to rename a download file before sending to the user
[download completed]
-->> Lauched when the last byte of a download file is sended to the user
*******************************************************************************
[upload name]
%item-name% (it is the default value to be used or nothing)
-->> can be used to rename an uploaded file before saving it in the current folder
[upload completed]
-->> launched every time that an upload of one file is finish with success
[upload failed]
-->> launched every time that an upload of one file has failed
*******************************************************************************
[on macro rename]
%old-name% and %new-name%
-->> launched every time that a file is renamed by macro
| [on macro move] | not implemented yet |
| [on macro copy] | not implemented yet |
| [on macro delete] | not implemented yet |
*******************************************************************************
[every (time)] and [at (time)]
[every XXX] and [at HH:MM]
XXX is in seconds, but you can use minutes or hours. examples
[every 5] (that is 5 seconds)
[every 3 hours]
[every 4h]
[every 15 minutes]
[every 1.5m] (that is 90 seconds)
[every 1:15 min] (that is 75 minutes)
HH:MM is instead in standard 24 hours format, but you can do things like
[at 0:00=at 6:00=at 12:00=at 18:00]
this will trigger every six hours, but at specific times.
while [every 6 hours] would trigger at same intervals but differently placed in time.