On 01-24-20 11:48, g00r00 wrote to Vk3jed <=-
I use a cron job to both monitor and start mis if it's not already running. The backup problem is easy for me to handle. Any script that manages MIS can tell it not to restart by dropping a file called /tmp/upgrade". The file doesn't have to contain anything. If this file exists, the script that attempts to restart MIS will abort. That way,
I had something like this on my Linux laptop BBS install. I was able
to do all of my upgrading via Mystic-DOS from a remote system via
telnet, SSH or whatever.
Making a way to make this a little easier for people would be nice
though and I am trying to move in the direction of automatic upgrades
and stuff too.
Yeah, I got used to the traditional upgrade process and have a script
that does the donkey work of replacing the binaries, etc, then issues a reminder to read the documentation to see what other things had to be done. :)
On 01-25-20 11:23, g00r00 wrote to Vk3jed <=-
Yeah, I got used to the traditional upgrade process and have a script
that does the donkey work of replacing the binaries, etc, then issues a reminder to read the documentation to see what other things had to be done. :)
Yep its that last part we are getting rid of (hopefully). A big part
of that would be covered by the new theme system.
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 16 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 22:20:28 |
| Calls: | 133 |
| Files: | 50,534 |
| D/L today: |
137 files (63,614K bytes) |
| Messages: | 323,396 |