A
: There are several built in event handlers now , you can use them with
RaidenFTPD built-in event triggers (you can find them in *.ftpd file ,
there is also documentation about events in
this page)
Supported
event trigger handlers
1.
http://
usage:
event=http://xxx.xxx.xxx.xxx/xxx.php
%u %g
when
the event occurs , the raidenftpd calls http url using
http GET method for you , with arguments translated |
2.
file://
usage:
event=file://c:\[path_with_no_space]\[executabe.exe]
%u %g
when
the event occurs , the raidenftpd calls local program
for you , with arguments translated , note that raidenftpd
does not wait for the end of external program if
using file:// |
3.
exec://
usage:
event=exec://c:\[path_with_no_space]\[executabe.exe]
%u %g
when
the event occurs , the raidenftpd calls local program
for you , with arguments translated , note that raidenftpd
wait for the end of external program if using exec://
|
4.
ask://
usage:
event=ask://c:\[path_with_no_space]\[executabe.exe]
%u %g
when
the event occurs , the raidenftpd calls local program
for you , with arguments translated , note that raidenftpd
can interact with extrnal program if using ask://
, see this
for more information |
5.
log://
usage:
event=log://c:\[path_with_no_space]\[text_file.txt]
%u %g
when
the event occurs , the raidenftpd writes custom log for
you to any filename specified , with arguments translated
, note that this operation is thread-safe |
6. queue://
usage:
event=queue://c:\[path_with_no_space]\[text_file.txt] %u %g
when the event occurs , the raidenftpd inserts this event to the odbc event_queue table, and ensures that only one event is executed at a time sequentially |
|
|