if your software supports it, set up a spare node just for testing new setti and menus. callers stay on the main nodes while you experiment safely. once ange works, move it over to the live setup. this habit prevents most self-in ted outages
if your software supports it, set up a spare node just for testing new and menus. callers stay on the main nodes while you experiment safely. ange works, move it over to the live setup. this habit prevents most se ted outages
How? You'd have to re-path your whole system and have a duplicate... Ever door would have to be totally redone... I don't see how this could possibly work if you don't use relative paths. I don't.
How? You'd have to re-path your whole system and have a duplicate... Ever door would have to be totally redone... I don't see how this could possibly work if you don't use relative paths. I don't.
if your software supports it, set up a spare node just for testing n and menus. callers stay on the main nodes while you experiment safel ange works, move it over to the live setup. this habit prevents most ted outages
How? You'd have to re-path your whole system and have a duplicate... Ever door would have to be totally redone... I don't see how this coul possibly work if you don't use relative paths. I don't.
i have a separate directory, mystic-tmp, i can use to test things out. of co you nwould probably only need it if you are testing a bunch the other
option would be to see if you bbs software can assign a "sysop only
ode? anyone know if thats possible with mystic? there's a Nx access control ng: "This command is used to check if a user is online a certain
node number. For ample: N1 will require that the user is currently
logged in on Node 1 in orde o pass. "
How? You'd have to re-path your whole system and have a duplicate... Ever door would have to be totally redone... I don't see how this coul possibly work if you don't use relative paths. I don't.
i did find an answer, at least on mystic bbs: ./mystic -l N11 so if
you had 10 nodes available, this would log you into node 11, invisible
users as there isn't a node 11 available
i did find an answer, at least on mystic bbs: ./mystic -l N11 so if
you had 10 nodes available, this would log you into node 11, invisible users as there isn't a node 11 available
How would that be any better than testing on an existing node? I really don't understand...
if your software supports it, set up a spare node just for testing new
setti
and menus. callers stay on the main nodes while you experiment safely.
once
ange works, move it over to the live setup. this habit prevents most
self-in
ted outages
How? You'd have to re-path your whole system and have a duplicate... Ever
door would have to be totally redone... I don't see how this could possibly
work if you don't use relative paths. I don't.
--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3,ftps,nntps ,wss, ssh utf-8) (default ports, 2222 for utf-8 and 999 for wss)
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (23:1/104)
How? You'd have to re-path your whole system and have a duplicate... Ever door would have to be totally redone... I don't see how this could
possibly work if you don't use relative paths. I don't.
i did find an answer, at least on mystic bbs:
./mystic -l N11
so if you had 10 nodes available, this would log you into node 11, invisible to
users as there isn't a node 11 available
pweck
sysopnet 23:1/1
bbs.pwecksretreat.com:2332
... The shortest distance between two points is under construction
--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Pweck's Retreat (23:1/1)
It feels like these tips are not based on real life sysops and ai
garbage. Lets try to have real good content
ifi did find an answer, at least on mystic bbs: ./mystic -l N11 so
invisibleyou had 10 nodes available, this would log you into node 11,
users as there isn't a node 11 available
How would that be any better than testing on an existing node? Ireally
don't understand...
well depending on how many nodes, you might want to save them all for callers
well depending on how many nodes, you might want to save them all for callers
I have 20... Usually only 1 is used.
forwell depending on how many nodes, you might want to save them all
callers
I have 20... Usually only 1 is used.
time for us to band together and build a new, younger group of callers. we need someone to build a good app for mobile phones that provides a good alternative to doom scrolling! there are a few out there but not imo easy
to navigate
time for us to band together and build a new, younger group of callers. need someone to build a good app for mobile phones that provides a good alternative to doom scrolling! there are a few out there but not imo ea to navigate
terminator is easy enough... You just need to add systems manually.
callers.time for us to band together and build a new, younger group of
goodneed someone to build a good app for mobile phones that provides a
imo eaalternative to doom scrolling! there are a few out there but not
to navigate
terminator is easy enough... You just need to add systems manually.
i wasnt aware of that one, it does look pretty good!
It's really the only one if you're using 80x25. Connectbot's latest version no longer supports ansi very well and termius sucks.
time for us to band together and build a new, younger group of calle need someone to build a good app for mobile phones that provides a g alternative to doom scrolling! there are a few out there but not imo to navigate
terminator is easy enough... You just need to add systems manually.
i wasnt aware of that one, it does look pretty good!
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 1,057 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 497650:44:46 |
| Calls: | 16,429 |
| Files: | 5,703 |
| Messages: | 694,221 |