Is there a way to add a command line shutdown for mystic ? . something like
c:\mystic\mis -shutdown /q , or c:\mystic\mis -restart /q. This would allow me to perform batch file daily restarts of my mystic servers .
I use Cmdow:
cmdow "Mystic Internet Server (The Positronium Repository)" /CLS
Download it from: http://cmech.dynip.com/filebase.bbs/bfds/CMDOW148.ZIP
So I tried this program and it works , a little to well, its like a off now switch , its a cool program but I think we need a program that
closes the MIS server clean . Shutting it off dirty causes issues with locked busy nodes and Im worried this may bork the Hub . Thanks for the suggestion .
So I tried this program and it works , a little to well, its like a o now switch , its a cool program but I think we need a program that closes the MIS server clean . Shutting it off dirty causes issues wit locked busy nodes and Im worried this may bork the Hub . Thanks for t suggestion .
You can write a bash script which closes mis server and after succeeding it, shuts down the computer. From inside a mystic menu you can add an external command to execute that script at +5 min after the current
time, so you can exit it normal. the script will run automatically and
the xomputer will close normal.
On 14 May 2019 at 12:18p, xqtr pondered and said...
So I tried this program and it works , a little to well, its lik now switch , its a cool program but I think we need a program th closes the MIS server clean . Shutting it off dirty causes issue locked busy nodes and Im worried this may bork the Hub . Thanks suggestion .
You can write a bash script which closes mis server and after succeed it, shuts down the computer. From inside a mystic menu you can add an external command to execute that script at +5 min after the current time, so you can exit it normal. the script will run automatically an the xomputer will close normal.
Certainly fair to say it would be a welcome switch for g00r00 to add
upon his return.
Not sure a killswitch to shutdown cleanly is the answer... I only saw
this message and don't know the past thread, but would be better to just make sure that upon startup it checks for old semaphores and bsy files
and cleans them out... rather than a complete shutdown script... right? Seems a little overkill to accomplish something not huge?
Hi :)
I think the issue is about being able to issue scheduled graceful
shutdown of MIS so things close cleanly and then other stuff like
backups etc can run then MIS is restarted.
I don't agree with the idea that on startup a script just clearing old semaphores and bsy files... they are usually still there to prevent something from running that closed badly at the time a problem occurred. So better IMHO to remove those manually and force the sysop to go
looking as to what happened.
**waves hello :) **
Certainly fair to say it would be a welcome switch for g00r00 to add
upon his return.
This reminds me - what are people doing for backups? I'd love to have
This reminds me - what are people doing for backups? I'd love to have
So I run mystic in docker - and I use "restic".
My backup is:
* Docker pause mystic
* Restic backup
* Docker unpause mystic
Restic is incremental, can de-dupes, compresses and can store stuff on another disk, another server running or in S3 (which is what I have) -
it is configured to keep the last 14 backups in S3. I also have a backup on a USB stick, which I keep the last 2 backups.
So I run mystic in docker - and I use "restic".
* Docker pause mystic
I also use my bareos backup server to back up the tqwNet UK and CA hubs, so everything gets backed up nicely over the ZeroTier private network.
Interesting. But what happens if you try to
* Docker pause mysticwhen someone is online? And a step further, what happens when you try to resume mystic and someone was online? How does it handle that?
Slick. I'll give this a look. FWIW I have been using resync, but I am
also the only current user, so can't attest to what other solutions look/feel like in comparison :) Thanks for sharing this.
To each their own, I never shut mystic down to perform backups or anything, no need to as far as I can tell... runs perfectly well and hasn't been shut off more than a couple of times during power cuts lol. The sem files that get created are just empty files anyway so it's not like it has something to go on to "continue" after it does come back to life, so no point keeping them after a dirty shutdown imho.
I need a clean command line shutdown command because (mostly*) a file
gets tossed from a node ( not the hub ) that should not have tossed , typically is the file is huge and borks the hub. so I Need to write a batch to do a daily shutdown and restart of mystic clean to reset the
HUB. just shutting mystic off , then performing a cleanup on restart
often wont fix the issue.
Sysop SolaRis
Error 1202 BBS !
I make Bill Gates do my Tech Support
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 15:12:12 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,312 |