Server IP : 103.53.40.154 / Your IP : 3.15.211.71 Web Server : Apache System : Linux md-in-35.webhostbox.net 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64 User : ppcad7no ( 715) PHP Version : 8.2.25 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON Directory (0755) : /../sys/../usr/share/doc/lftp-4.4.8/ |
[ Home ] | [ C0mmand ] | [ Upload File ] |
---|
lftp 2.0 and later support loading modules (shared objects) at runtime. Use command `module' to load a module. It also supports loading certain modules (some of protocols and commands) automatically on demand. To compile modular lftp use: configure --with-modules You will need GCC and ELF platform (linux, freebsd-3.x, solaris, irix etc). Below are the technical details. Module is a shared object, after loading it with dlopen(3) lftp does dlsym("module_init") and calls this function with parameters argc, argv: extern "C" void module_init(int argc, const char * const *argv); The argv vector contains the arguments passed to `module' command after module name. In case of loading module on demand it is empty. Note: function _init of a module is called automatically by dlopen. It can execute constructors if the module is properly compiled with `gcc -shared'. To load modules on demand lftp uses protocol or command name to find module file. For protocols it looks for proto-<PROTOCOL>.so and for commands -- cmd-<COMMAND>.so. The modules register the protocols and commands they provide with functions FileAccess::Register and CmdExec::RegisterCommand. lftp searches module for any protocol specified in URL in open command, and only for certain compile time defined set of commands -- the commands that have NULL instead of function pointer in command table in commands.cc.