I would like to exclude web external called doors from being listed in logon.lst. When calling external doors individually the logon.lst reflects each door as a new call, and while it technically is a new and separate call it just doesn't look good. I've looked through the scripts but couldn't find a way to avoid this behavior.
Re: web externals in logon.lst
By: Rastus to DOVE-Net.Synchronet_Discussion on Sun Feb 22 2015 05:50 pm
I would like to exclude web external called doors from being listed in logon.lst. When calling external doors individually the logon.lst reflects each door as a new call, and while it technically is a new and separate call
it just doesn't look good. I've looked through the scripts but
couldn't find a way to avoid this behavior.
The only way to defeat the logon.lst (for non-sysop users) is to have the node be placed into "quiet mode" upon these special logins.
You can do this by editing your logon.js. First, copy exec/logon.js to
your mods directory. Then edit your mods/logon.js as follows:
Find this section:
// Set rlogin_xtrn_menu=true in [logon] section of ctrl/modopts.ini
// if you want your RLogin server to act as a door game server only if(options
&& options.rlogin_xtrn_menu
&& bbs.sys_status&SS_RLOGIN) {
bbs.xtrn_sec();
bbs.hangup();
}
And modify it so (inserting one line):
// Set rlogin_xtrn_menu=true in [logon] section of ctrl/modopts.ini
// if you want your RLogin server to act as a door game server only if(options
&& options.rlogin_xtrn_menu
&& bbs.sys_status&SS_RLOGIN) {
system.node_list[bbs.node_num-1].status=NODE_QUIET;
bbs.xtrn_sec();
bbs.hangup();
}
Try that. The downside is that the node will appear to other users to be inactive and waiting for a caller, when it fact, it will be in use by a
user running the door.
digital man
Synchronet "Real Fact" #57:
The last version of Synchronet to run on MS-DOS and OS/2 was v2.30c
(1999). Norco, CA WX: 58.6�F, 61.0% humidity, 9 mph NNE wind, 0.51 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net
Thank you, this will work out very well. I can still see who's online using the node utility and that is all that I really care about. I didn't want the doors called from the web to be displayed and this takes care of that.
The active node numbers aren't important.. But it would be nice to choose a higher node to log on to.. When I ran Renegade it would allow the sysop to log in on a higher node. It would be nice to choose the node number. Is that possible with SBBS?
The only way to do that would be to run 2 instances of sbbs and have the terminal server (for Telnet, RLogin, and SSH connections) service different node ranges. I'm not sure what advantage that would provide.
Re: Re: web externals in logon.lst
By: Digital Man to Rastus on Tue Feb 24 2015 15:24:29
The only way to do that would be to run 2 instances of sbbs and have the terminal server (for Telnet, RLogin, and SSH connections) service different node ranges. I'm not sure what advantage that would provide.
Speaking of issues in this vein... How is it that you have Synchronet configured @ Vertrauen (unless it's a trade secret ;) to have allegedly a bunch of nodes served by a Linux instance and a bunch on a Windows
instance? I've been wondering abou that for awhile now...
No secret. I use a Samba share on my Linux system so that my Windows
nodes (I run some in Win8 and some in a Win7 VM) can share the same data and configuration files as the Linux nodes. I've always run a multiple-computer BBS and usually multiple OSes (since I support
multiple OSes).
Re: Re: web externals in logon.lst
By: Digital Man to Khelair on Tue Feb 24 2015 23:46:42
No secret. I use a Samba share on my Linux system so that my Windows nodes (I run some in Win8 and some in a Win7 VM) can share the same data and configuration files as the Linux nodes. I've always run a multiple-computer BBS and usually multiple OSes (since I support multiple OSes).
I've got to say, I'm pretty impressed that that works. :)
The only way to do that would be to run 2 instances of sbbs and have the terminal server (for Telnet, RLogin, and SSH connections) service
different node ranges. I'm not sure what advantage that would provide.
digital man
Digital Man wrote:
The only way to do that would be to run 2 instances of sbbs and have the terminal server (for Telnet, RLogin, and SSH connections) service different node ranges. I'm not sure what advantage that would provide.
It was just a thought. Renegade had/has a switch to allow the op to choose a node.
Synchronet is a great package. With a little bit of JavaScript programming knowledge most anything is possible. Thing I like best is the excellent documentation and access to the awesome support that you and the community provide.. It puts SBBS over the top when compared to the other bbs
packages!
Have a great day!
That was kind of the foundation of Synchronet from the beginning: to support multiple nodes spread across multiple LAN-connected computers. I would be very concerned if it didn't work. :-)
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 10:29:09 |
| Calls: | 510 |
| Messages: | 220575 |