Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
February 17, 2024 16:29
May 5, 2022 19:40
April 15, 2020 15:25
August 10, 2015 21:40
February 21, 2022 11:36
February 21, 2022 11:36
February 21, 2022 11:36
February 17, 2024 16:17
April 15, 2020 15:25
February 21, 2022 11:36
February 17, 2024 16:29

MXQ - mariux64 job scheduling system


Main git repository clone


Install using GNU make

make install

or to specify a prefix:

make PREFIX=... [DESTDIR=...] install

Install using bee

bee init $(bee download git:// --execute
bee update mxq

or to specify a prefix

bee init $(bee download git:// --prefix=... --execute
bee update mxq

Initial setup

Definitions of the tables for the MySQL database can be found in mysql/create_tables.sql and mysql/create_trigger.sql Be sure to create those once and check the same directory for alter_tables*.sql` files when upgrading.

mysql [options] [database] <mysql/create_tables.sql
mysql [options] [database] <mysql/create_trigger.sql

Development builds

The devel target in the Makefile will enable all devolopment features by defining MXQ_DEVELOPMENT when compiling C sources.

make clean
make devel PREFIX=/path/to/test
make install PREFIX=/path/to/test

Differences to production builds

Some new features and improvements are enabled in development builds. Those features may not be tested for every situation yet and may result in database corruption and/or failing jobs.

changed mxqd default options

In devolopment builds --no-log is default (enable logging with --log)

Development database access

Devolopment builds default to use [mxqdevel] groups from mysql config files for servers and clients (instead of the default [mxqclient] and [mxqd] groups)