Appendix М. Custom Extensions

Top  Previous  Next

The extensions, implemented as a lua-scripts, are meant for automation of the administrator work enabling quicker performance of certain tasks of the Enterprise Server. These scripts are located in the folder:

◆for Windows OS: var\extensions

◆for FreeBSD OS and Solaris OS: /var/drwcs/extensions

◆for Linux OS: /var/opt/drwcs/extensions

of Server installation folder. After the Server installation, preinstalled extension procedure are located in this folder. To permit the Server to perform user extension scripts, the Server must be launched with the -hooks switch.

All scripts are disabled by default. To enable scripts, you must remove the word disabled or remove entire comment (keep empty line).

The extensions folder contains following scripts:

◆access_check.ds – called before check access against appropriate ACL (Access Control List);

◆access_denied.ds – called when access denied according ACL settings or result  of access_check procedure;

◆admin_logged.ds – called when administrator successfully authenticate in the Dr.Web Control Center;

◆admin_noauth.ds – called when administrator failed to authenticate in the Dr.Web Control Center;

◆agent_status.ds – called when Agent report its local policy;

◆backup.ds – called when backup completed but before deleting previous backup files;

◆bad_connection.ds – called when new client connection cannot be established;

◆connection_denied.ds – called when connection denied according license limitation;

◆database_load.ds – called when database driver load process completed;

◆database_verify.ds – called when database verification completed;

◆deinstallation.ds – called when deinstallation of Agent completed;

◆disconnected.ds – called when client disconnected;

◆group_changed.ds – called when group properties changed;

◆group_created.ds – called when new group created;

◆group_deleted.ds – called when group deleted;

◆install.ds – called when installation event occurred;

◆installed_components.ds – called when Agent reported installed components;

◆jobexecuted.ds – called when job executed event received from Agent;

◆license_error.ds – called when new client connection cannot be established due license limitation;

◆load_plugin.ds – called when plugin module loaded;

◆load_protocol.ds – called when protocol module loaded;

◆neighbor_connected.ds – called when server connected;

◆neighbor_install.ds – called when installation event received from neighbor Server;

◆neighbor_noauth.ds – called just after server connection rejected due (authorization) error;

◆neighbor_run_begin.ds – called when component started event received from neighbor Server;

◆neighbor_run_end.ds – called when component completed event received from neighbor Server;

◆neighbor_scan_error.ds – called when scan error event received from neighbor Server;

◆neighbor_scan_statistics.ds – called when scan statistics event received from neighbor Server;

◆neighbor_station_status.ds – called when station local policies/settings received from neighbor Server;

◆neighbor_virus.ds – called when virus detected event received from neighbor Server;

◆newbie_accepted.ds – called when newbie access granted, authorization is successful and station created in database;

◆newbie_came.ds – called when newbie connected;

◆newbie_registered.ds – called when newbie access granted but before information stored in database;

◆pong.ds – called when PONG received from client;

◆run_begin.ds – called when component started event received from Agent;

◆run_end.ds – called when component completed event received from Agent;

◆scan_error.ds – called when scan error event received from Agent;

◆scan_statistics.ds – called when scan statistics event received from Agent;

◆server_jobexecuted.ds – called when job executed on the server;

◆server_load.ds – called when Server binary file loaded for execute some service function (the Server will not serve clients);

◆server_start.ds – called when Server started and going to serve clients;

◆server_terminate.ds – called when Server completed serve clients;

◆server_unload.ds – called when Server completed execute some service function (the Server did not serve clients);

◆station_connected.ds – called when Agent connected successfully;

◆station_create.ds – called when station create completed;

◆station_date.ds – called when invalid station time/date detected;

◆station_deleted.ds – called when station deleted;

◆station_noauth.ds – called just after Agent connection rejected due authorization error;

◆station_update_failed.ds - called after receiving a message from the Agent on update error at the station;

◆station_update_reboot.ds - called after receiving a message from the Agent on requirement to restart the station after update;

◆unload_plugin.ds – called when plugin module unloaded;

◆unload_protocol.ds – called when protocol module unloaded;

◆virus.ds – called when virus detected event received from Agent;

◆virusbases.ds – called when Agent sent virus bases information.