Has there been any implementation to force Magicka to reload it's config files/language? Cuz I have to say it's a real pain in the ass having to shutdown and reload Magicka after every single little small change to
config files ..

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Internal Dimension [idbbs.dlinkddns.com:2023] (21:1/178)

Has there been any implementation to force Magicka to reload it's config files/language? Cuz I have to say it's a real pain in the ass having to shutdown and reload Magicka after every single little small change to config files ..

Not yet, I asked the same question not long ago. I'm sure it's on his
list of things to do though :)

toofargone .:[fusion]:. telnet.fusionbbs.online tel:23 ssh:2222

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Fusion BBS (21:4/132)

Has there been any implementation to force Magicka to reload it's files/language? Cuz I have to say it's a real pain in the ass havi shutdown and reload Magicka after every single little small change config files ..

Not yet, I asked the same question not long ago. I'm sure it's on his
list of things to do though :)

Yeah, it's a tricky one. Magicka loads it's config before it forks
servers, so I'm not really sure how to go about that. It seems like a lot
of work for very little gain.

Andrew

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)

Yeah, it's a tricky one. Magicka loads it's config before it forks
servers, so I'm not really sure how to go about that. It seems like a
lot of work for very little gain.

True, the reload process would have to involve the servers shutting down
and restarting anyway to reload the new config. No reason you couldn't
create a shell script to do the same thing.. something like;

#!/bin/sh
pkill magicka
/path/to/magicka config/bbs.ini

That would kill and restart magicka. You can do the same for watchmail,
binkd, chat server if you like.

You could even make it automated during nightly / weekly maintenance.

If there are no users online then doing a restart isn't going to put
anyone out anyway.

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Fusion BBS (21:4/132)

apam wrote to toofargone <=-

Yeah, it's a tricky one. Magicka loads it's config before it forks servers, so I'm not really sure how to go about that. It seems like a
lot of work for very little gain.

I don't have too much trouble with typing CTRL-C, arrow up, and ENTER myself.
<GRIN>



... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
--- MultiMail
+ Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (@3)
* Origin: FTN-MNET Gateway (21:1/50)

On 17 Feb 2019, Blue White said the following...

I don't have too much trouble with typing CTRL-C, arrow up, and ENTER myself. <GRIN>

That's all and well but what if you are calling remote and dont have access
to the local console .. I wish I could remember C++ lol I have a project I
want to do .. gonna do some reading and see if I can't re-learn

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: internal dimension + idbbs.dlinkddns.com:2019 (21:1/178)

That's all and well but what if you are calling remote and dont have access to the local console .. I wish I could remember C++ lol I have a project I want to do .. gonna do some reading and see if I can't re-learn

You could always run SSH on a seperate port from your bbs (if you have
ssh enabled on the bbs) and run something like ssh user@machine "command"

You would just need a shell script to run;

#!/bin/bash
pkill magicka
/path/to/magicka /path/to/bbs.ini

There are heaps of ssh apps for Android, i'm sure there is one for iPhone
too.

|15t|10o|02ofargone |15.:[|15f|10u|02sion|15]:.
|15t|10e|02lnet |15t|10e|02lnet|15.|02fusionbbs|15.|02online:23
|15s|10s|02h |15t|10e|02lnet|15.|02fusionbbs|15.|02online:2222

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Fusion BBS (21:4/132)

That's all and well but what if you are calling remote and dont have access to the local console .. I wish I could remember C++ lol I have a project I want to do .. gonna do some reading and see if I can't re-learn

Ok I knocked this up quickly. You'll need two files;

startmagicka.sh
#!/bin/sh
screen -X sessioname bbs
/path/to/magicka /path/to/bbs.ini

remoterestart.sh
#!/bin/sh
pkill magicka
screen -dm -S bbs /path/to/startmagicka.sh

What this will do is kill any magicka processes running, destroy the old
screen session, create a new screen session and name it bbs (i name my
screen sessions for ease of use), fire up magicka, then detatch from
the screen session leaving magicka happily running in a screen session.

Then all you'll need to do is ssh user@host /path/to/remoterestart.sh

Easy to do, saves hours of coding. I've got all of my services (bbs,
watchmail, binkd, magichat) running in named screen sessions.

Someone else might have a better way...

|15t|10o|02ofargone |15.:[|15f|10u|02sion|15]:.
|15t|10e|02lnet |15t|10e|02lnet|15.|02fusionbbs|15.|02online:23
|15s|10s|02h |15t|10e|02lnet|15.|02fusionbbs|15.|02online:2222

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Fusion BBS (21:4/132)

On 18 Feb 2019, toofargone said the following...

Someone else might have a better way...

Docker :P

(sorry, couldnt help myself...)

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (21:2/116.1)

Hello,

Ok I knocked this up quickly. You'll need two files;

startmagicka.sh
#!/bin/sh
screen -X sessioname bbs
/path/to/magicka /path/to/bbs.ini

remoterestart.sh
#!/bin/sh
pkill magicka
screen -dm -S bbs /path/to/startmagicka.sh

If you have a distro with systemd, you can create simple unit files to
help starting up magicka in the background. Currently I only start up
Magicka and binkd, since I don't have doors or other things running at
the moment.

My Magicka unit file (called magicka.service):

---start---
[Unit]
Description=Magicka BBS service After=network.target

[Service] User=bbs Group=bbs Type=simple WorkingDirectory=/home/bbs/bbs ExecStart=/home/bbs/bbs/magicka /home/bbs/bbs/config/bbs.ini ExecStop=/usr/bin/pkill -15 magicka Restart=on-failure

[Install]
WantedBy=multi-user.target
--end---

And I start binkp in a similar fashion. Here is my binkd unit file
(called magickbink.service):

---start---

[Unit]
Description=Magicka BINKD service After=network.target

[Service] User=bbs Group=bbs Type=simple WorkingDirectory=/home/bbs/files ExecStart=/usr/local/sbin/binkd /home/bbs/files/ftn/binkd.conf ExecStop=/usr/bin/pkill -15 binkd Restart=on-failure

[Install]
WantedBy=multi-user.target
---end---

To enable them, copy the unit files to "/etc/systemd/system" and enable
them like this:

sudo systemctl enable magicka.system
sudo systemctl enable magickbink.system

Start/stop/inspect them like this:

sudo systemctl start magicka.system
sudo systemctl stop magicka.system
sudo systemctl status magicka.system

A status looks something like this:

---start---
# systemctl status magickbink.service
? magickbink.service - Magicka BINKD service
Loaded: loaded (/etc/systemd/system/magickbink.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2019-02-18 20:27:46 GMT; 12min ago
Main PID: 967 (binkd)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/magickbink.service
ÃÄ967 binkd: server manager (listen 24555)
ÀÄ968 binkd: client manager

Feb 18 20:27:46 magickabbs systemd[1]: Started Magicka BINKD service.
Feb 18 20:27:46 magickabbs binkd[967]: [102B blob data]
Feb 18 20:27:46 magickabbs binkd[967]: [60B blob data]
Feb 18 20:27:46 magickabbs binkd[967]: [70B blob data]
Feb 18 20:27:46 magickabbs binkd[967]: [62B blob data]
---end---

And just to see whether it is actually running as the right user:

---start---
# ps axuf | grep [b]inkd
bbs 967 0.0 0.3 10788 1968 ? Ss 20:27 0:00 binkd:
server manager (listen 24555) bbs 968 0.0 0.0 10788 232 ?
S 20:27 0:00 \_ binkd: client manager ---end---

And the same thing for Magicka itself:

---start---
# ps axuf | grep [m]agicka
bbs 434 0.0 1.4 102204 7460 ? Ssl 20:17 0:00 /home/bbs/bbs/magicka /home/bbs/bbs/config/bbs.ini bbs 530 0.0
0.6 94008 3356 ? S 20:17 0:00 \_ /home/bbs/bbs/magicka /home/bbs/bbs/config/bbs.ini ---end---

I must say that even though I am far from being a systemd fanboy, in this
case it proved to be rather useful.

Cheerio,
Jan Henkins

--- MagickaBBS v0.12alpha (Linux/x86_64)
+ Origin: UnderZaNet BBS, ssh://bbs.under.za.net:2024 (@8)
* Origin: FTN-MNET Gateway (21:1/50)

Docker :P

(sorry, couldnt help myself...)

Well i'm not an expert on everything or anything :)

Whatever works the easiest for you.

toofargone .:[fusion]:.
telnet: telnet.fusionbbs.online:23
ssh: telnet.fusionbbs.online:2222

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Fusion BBS (21:4/132)

That's all and well but what if you are calling remote and dont ha access to the local console .. I wish I could remember C++ lol I h project I want to do .. gonna do some reading and see if I can't r

Ok I knocked this up quickly. You'll need two files;

Easy to do, saves hours of coding. I've got all of my services (bbs, watchmail, binkd, magichat) running in named screen sessions.

Sweet.. I almost had words to say until I realized that if I use the
start script to start the BBS it wont detach the screen.. so I called the restart script with no magicka running and it detached the screen and the
BBS is running .. a GUI control panel would be kinda nice :)

I wish I could change over totally to Magicka, but I am the Canadian host
for DoRENet and Retronet and the Amiganet 902 host .. and Magicka isn't
that far with it's tic processor .. it does not forward to nodes nor can
you hatch or use fileboxes :( .. I looked at HTick but the Husky project
just makes me dizzy trying to configure it



--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Internal Dimension [idbbs.dlinkddns.com:2023] (21:1/178)

Hello,

If you have a distro with systemd, you can create simple unit files to help starting up magicka in the background. Currently I only start up Magicka and binkd, since I don't have doors or other things running at
the moment.

My Magicka unit file (called magicka.service):

Dood.. that's even better lol.. I was trying to figure out how to do it
with systemd and monitoring pid files to check for crashing/reloading if
so

Will try that method out later


--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Internal Dimension [idbbs.dlinkddns.com:2023] (21:1/178)

If you have a distro with systemd, you can create simple unit files

Yay, didn't know that could be done! I've got all my services now under systemd.. magicka, magichat, binkd, watchmail :")

Awesomesauce!

toofargone .:[fusion]:.
telnet: telnet.fusionbbs.online:23
ssh: telnet.fusionbbs.online:2222

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: Fusion BBS (21:4/132)

If you have a distro with systemd, you can create simple unit

Yay, didn't know that could be done! I've got all my services now
under systemd.. magicka, magichat, binkd, watchmail :")

I have a systemd unit that launches screen :)

You can run magicka as a daemon and have it fork off, but I like to be
able to ctrl-c git pull make and run again :)

Similar setups can be done with other init systems too.

Andrew

--- MagickaBBS v0.12alpha (Linux/x86_64)
* Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)

Dave Vandermeer wrote to Blue White <=-

That's all and well but what if you are calling remote and dont have access to the local console .. I wish I could remember C++ lol I have a project I want to do .. gonna do some reading and see if I can't
re-learn

You are able to change the config files from remote, too? I can do it, via
SSH from another machine, but not calling from remote. I have not learned
that trick yet.




... Gone crazy, be back later, please leave message.
--- MultiMail
+ Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (@3)
* Origin: FTN-MNET Gateway (21:1/50)