@Thenomain Well. My mechanipus branch of tinymux will auto-reconnect sql as needed... see
this commit if you want to try it in isolation...

Otherwise, set up a ~/.my.cnf file with something like:

[client] user=gamename password=... database=gamename

and then a ~/wait-for-sql.sh like:

#! /bin/bash while ! echo 'select distinct "sql is up";' |mysql; do sleep 1; done

and then be sure to set it executable

$ chmod 755 wait-for-sql.sh

and then edit your crontab (cron -e) to have something like:

@reboot wait-for-sql.sh && cd /home/mush/gamename/game && ./Startmux

or if you're on my fork something like

@reboot wait-for-sql.sh && cd /home/mush/gamename/game && bin/mux-start

menacing helpfulness intensifies

Hey, I was getting my ass kicked at Ora et Labora. Priorities.

@Thenomain

When are you gonna do that MLP/WOD crossover game, T?

When?!

@Thenomain said:

I would like to make a "Darkwater nWoD" bare-bones game database, complete with your quiet room that's ready to run.

Hell yes I'm interested.

That sounds like a pretty reasonable goal. Problem I'm running into currently? The main mechanipus branch builds fine, but has a very different (and much more modern) autoconf tool suite. This means: installing into the ../game tree? No. It doesn't do that.

I probably need to sit down and write up a more complete automake setup to install all the things in all the right places, so that a fairly modest example config line will work for most people.

Right now, though, even building MUX has been too big a barrier for most people. I come from the OpenSource and C/C++ communities, so I like to say, "Go download ___ from git and build it," but most of the mushers aren't quite sure what a shell is. ...this creates large headaches, but I suppose we'll get there eventually.

That said, oddly enough Brazil is still working on MUX.