midb — Message Index database daemon
midb [-c config]
midb is used by imap(8gx) and pop3(8gx) to generate and keep track of folder and message summaries. In particular, it enumerates messages to give them their IMAP UID and have at all times a suitable UIDNEXT value for folders ready. midb also caches the Message-Id, modification date, message flags, subject and sender to facilitate IMAP listings.
- -c config
Read configuration directives from the given file. If this option is not specified, /etc/gromox/midb.cfg will be read if it exists.
Output version information and exit.
Display option summary.
The usual config file location is /etc/gromox/midb.cfg.
- Colon-separated list of directories which will be scanned when locating further configuration files, especially those used by plugin instances.Default: /etc/gromox/midb:/etc/gromox
- Colon-separated list of directories which will be scanned when locating data files.Default: /usr/share/gromox/midb
- The time after the last use of a particular midb.sqlite3 that the sqlite gets unloaded.Default: 30minutes
- Log every incoming MIDB command and the return code of the operation in a minimal fashion to stderr. Level 1 emits commands with a failure return code, level 2 emits all commands.Default: 0
- A space-separated list of individual IPv6 or v4-mapped IPv6 host addresses that are allowed to converse with the midb service. No networks and no CIDR notations are permitted. This option deprecates the /etc/gromox/midb_acl.txt file used in earlier versions.Default: ::1
- An IPv6 address (or v4-mapped address) for exposing the event service on.Default: ::1
- The TCP port number for exposing the event service on.Default: 5555
- Target for log messages here. Special values: "-" (stderr/syslog depending on parent PID) or "syslog" are recognized.Default: - (auto)
- Maximum verbosity of logging. 1=crit, 2=error, 3=warn, 4=notice, 5=info, 6=debug.Default: 4 (notice)
- The time after a midb.sqlite3 was first loaded that it will be unloaded.Default: 60min
- This directive controls whether database schemas are automatically upgraded when a message index database (midb.sqlite) is loaded. During this time, that DB is unavailable and operations on it will be delayed. Connection aborts, if any, would be due to timeouts in components other than midb. (The file can temporarily grow to double its size, so ample disk space may be required.)Default: yes
- The minimum number of client processing threads to keep around.Default: 100
- Default: 10
- If set to 1, every query given to SQLite prepare/execute is logged. If set to 0, only failed queries are logged. (It cannot be made completely silent, since our queries ought to never fail.)Default: 0
- See SQLite documentation for details.Default: 0 (use SQLite default)
- Enables/disables synchronous mode for SQLite databases. See SQLite documentation for details.Default: off
- Selects the particular journal mode for SQLite databases; off selects DELETE mode, on selects WAL mode. See SQLite documentation for details.Default: on
- Directory for runtime variadic data.Default: /var/lib/gromox
config_file_path/exmdb_list.txt: exmdb multiserver selection map.
/usr/lib/gromox/libgxs_*.so: service plugins