This script checks userinfo on login. It is suitable to identify known spammers, warn users or just announce pingers or other important hub users. Search values ​​are regular expressions and consensus for all fields in one profile is necessary (analogy to userinfo check in OP clients).


Installation and usage

Download the script and move it to any location on your filesystem. Then create config XML file and save it in the same directory as globster-usercheck.xml, you can use the example configuration at the bottom of this document.

To start the script:

cd /path/to/script
./ [<config>]

Always use full path to the configuration file. If no config file is given, the script searches for globster-usercheck.xml in the script path or /etc/globster. We changed the directory to the script path and we have the config in the same directory so we can leave this argument empty.

To run in background:

./ &

XML configuration

The table below shows tags which can be used in the XML configuration file. Most of them are mandatory for the script to work.

TagDescriptionContainer tag
configStart tag of the configuration, can be replaced by any tag except other tags described here.-
hubNew hub object.config
userinfoUserinfo profile group tag.hub
inffieldValue to be searched for (regular expression).userinfo
actiontosendIDs of actions separated by comma to be sent when all patterns in userinfo are matched.userinfo
actionAction sent when match is found. Command or message have to be constructed in way it can be sent to global chat or private message. Raw commands should not be used. Variable %[userNI] states for user's nickname.config

The table below shows attributes which can be used in the XML configuration file. Most of them are mandatory for the script to work.

dbusaddrDBUS_SESSION_BUS_ADDRESS of the Globster bus session. Script uses this address to identify the session of Globster in case of script restart. This attribute is optional.config
hubidGlobster hub ID.hub
fieldSpecifies the field name to be checked. Values: nick, description, client, mail, slots, sharedfiles, sharesize, conn, ip4, ip6, as. CID, open hubs and flags are not fully supported, yet.inffield
actionidAction ID, used in actiontosend.action
destinationSpecifies destination of the action. Values: chat, user.action
meSends action message as if it was a system message. Values: 0 off, 1 onaction

Example configuration

Sample configuration can be found here.