Would the following script work to start the BBS on the second workspace? I already have the script setup in the autostart options, but added the wmctrl line because I want it to open the terminal window and start the BBS on the second workspace.
#!/bin/bash
(command &); wmctrl -r "Window Title" -t 1
cd /mystic/semaphore
rm *.bsy
cd /mystic
./mis -server
Why not create a systemd service instead?
Explain please. I'm not as fluent in Linux as I was in DOS or WinBlows.
Ok, my bash seems to be running, but I don't get the window so that I can monitor what the BBS is doing. :(
Other than that what I wrote seems to be working just fine.
Ok, my bash seems to be running, but I don't get the window so that I can monitor what the BBS is doing. :(
Other than that what I wrote seems to be working just fine.
Ok, my bash seems to be running, but I don't get the window so that I
monitor what the BBS is doing. :(
Other than that what I wrote seems to be working just fine.
Right, would nodespy be good enough?
... Electricity is really just organized lightning.
--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Clutch BBS * telnet://clutchbbs.com (21:1/199)
Right, would nodespy be good enough?
I used to run nodespy as well but it only shows info when a user is actually logged in. I don't run it full time any more.
I'm going to try tail -f /bbs/mystic/logs/*.log and see how I like it.
Right, would nodespy be good enough?
nodespy only shows you node status and user activity. tailing log files gives you all the mailer/mutil/mis info on top of that.
Ok, my bash seems to be running, but I don't get the window so that I monitor what the BBS is doing. :(
Other than that what I wrote seems to be working just fine.
Right, would nodespy be good enough?
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 121 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 06:15:13 |
| Calls: | 7,847 |
| Calls today: | 2 |
| Files: | 9,394 |
| D/L today: |
170 files (13,303K bytes) |
| Messages: | 399,040 |