BOPM (Bedienen)
Aus ZH Wiki
Hier erhältst du Informationen zur Bedienung des BOPM.
Übernommen aus der Dokumentation. Die Bedienung ist nur durch Oper möglich, über die Kommandozeile nur durch den Serverbesitzer.
Inhaltsverzeichnis |
Command Line Options
-c <name> Config name. By default BOPM reads bopm.conf, "-c foo" will cause BOPM to read foo.conf. The primary use for this is to run multiple BOPMs from one directory.
-d Debug mode. BOPM will not fork, and will write logs to stderr.
Multiple -d increase debug level.
Operator Channel Commands
Das sind die Befehle die eventuell für Oper interessant sind.
botnick check <host> [scanner] -- Manually scan host for insecure proxies and output all errors. If scanner is not given, bopm will scan on all scanners. NOTE: this will NOT add a kline (or whatever) if it finds a proxy. This is a change from 2.x.
botnick stats -- Output scan stats, uptime and client connection count.
botnick fdstat -- Output some into about file descriptors in use.
Also if several BOPMs are present in one channel they will all respond to !all, for example !all stats (fixed in BOPM 3.1.0).
Rehashing BOPM
A /kill to bopm will cause the process to restart, rehashing the configuration file and ending all queued scans.
Logging
Once started, BOPM logs all significant events to a file called "bopm.log" which by default can be found at $HOME/bopm/var/bopm.log. There is also a config option to log all proxy scans initiated, which can be quite useful if you receive an abuse report related to portscanning.
These log files, especially the scan log, can grow quite large. It is suggested that you arrange for these files to be rotated periodically. An example shell script is provided in the contrib/logrotate directory. If you prefer to use the log rotation facilities of your operating system then you should send a USR1 signal to BOPM after moving its logfiles - this will cause BOPM to reopen those files.
