Skip to content
Snippets Groups Projects
Commit d32a21d5 authored by cvs2git's avatar cvs2git
Browse files

This commit was manufactured by cvs2svn to create tag 'sbbs315b'.

parent 1d851511
No related branches found
Tags sbbs315b
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 0 additions and 614 deletions
CVSROOT/checkoutlist deleted 100755 → 0
+ 0
− 13
View file @ 1d851511
# The "checkoutlist" file is used to support additional version controlled
# administrative files in $CVSROOT/CVSROOT, such as template files.
#
# The first entry on a line is a filename which will be checked out from
# the corresponding RCS file in the $CVSROOT/CVSROOT directory.
# The remainder of the line is an error message to use if the file cannot
# be checked out.
#
# File format:
#
# [<whitespace>]<filename><whitespace><error message><end-of-line>
#
# comment lines begin with '#'
CVSROOT/commitinfo deleted 100755 → 0
+ 0
− 15
View file @ 1d851511
# The "commitinfo" file is used to control pre-commit checks.
# The filter on the right is invoked with the repository and a list
# of files to check. A non-zero exit of the filter program will
# cause the commit to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/config deleted 100755 → 0
+ 0
− 14
View file @ 1d851511
# Set this to "no" if pserver shouldn't check system users/passwords
#SystemAuth=no
# Set `PreservePermissions' to `yes' to save file status information
# in the repository.
#PreservePermissions=no
# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
# level of the new working directory when using the `cvs checkout'
# command.
#TopLevelAdmin=no
# Requires CVS v1.12+
UseNewInfoFmtStrings=yes
\ No newline at end of file
CVSROOT/cvswrappers deleted 100755 → 0
+ 0
− 23
View file @ 1d851511
# This file affects handling of files based on their names.
#
# The -t/-f options allow one to treat directories of files
# as a single file, or to transform a file in other ways on
# its way in and out of CVS.
#
# The -m option specifies whether CVS attempts to merge files.
#
# The -k option specifies keyword expansion (e.g. -kb for binary).
#
# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
#
# wildcard [option value][option value]...
#
# where option is one of
# -f from cvs filter value: path to filter
# -t to cvs filter value: path to filter
# -m update methodology value: MERGE or COPY
# -k expansion mode value: b, o, kkv, &c
#
# and value is a single-quote delimited value.
# For example:
#*.gif -k 'b'
CVSROOT/editinfo deleted 100755 → 0
+ 0
− 21
View file @ 1d851511
# The "editinfo" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
CVSROOT/loginfo deleted 100755 → 0
+ 0
− 29
View file @ 1d851511
# The "loginfo" file controls where "cvs commit" log information
# is sent. The first entry on a line is a regular expression which must match
# the directory that the change is being made to, relative to the
# $CVSROOT. If a match is found, then the remainder of the line is a filter
# program that should expect log information on its standard input.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name ALL appears as a regular expression it is always used
# in addition to the first matching regex or DEFAULT.
#
# You may specify a format string as part of the
# filter. The string is composed of a `%' followed
# by a single format character, or followed by a set of format
# characters surrounded by `{' and `}' as separators. The format
# characters are:
#
# s = file name
# V = old version number (pre-checkin)
# v = new version number (post-checkin)
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
ALL (echo %p %{sVv}; cat) | /sbbs/exec/smbutil -o -i "-tCVS commit" "-s%p/%s" -f$USER i /sbbs/data/subs/syncprog;sync
ALL /sbbs/exec/jsexec -c /sbbs/ctrl ircmsg -s bbs.synchro.net -p 5050 -c \#synchronet -n cvs_$USER -x "^In directory cvs" -x "^Modified Files:\$" -x "^Log Message:\$"
#ALL jsexec -c /sbbs/ctrl gnats_cvs $USER cvs justme
CVSROOT/modules deleted 100755 → 0
+ 0
− 57
View file @ 1d851511
# Three different line formats are valid:
# key -a aliases...
# key [options] directory
# key [options] directory files...
#
# Where "options" are composed of:
# -i prog Run "prog" on "cvs commit" from top-level of module.
# -o prog Run "prog" on "cvs checkout" of module.
# -e prog Run "prog" on "cvs export" of module.
# -t prog Run "prog" on "cvs rtag" of module.
# -u prog Run "prog" on "cvs update" of module.
# -d dir Place module in directory "dir" instead of module name.
# -l Top-level directory only -- do not recurse.
#
# NOTE: If you change any of the "Run" options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And "directory" is a path to a directory relative to $CVSROOT.
#
# The "-a" option specifies an alias. An alias is interpreted as if
# everything on the right of the "-a" had been typed on the command line.
#
# You can encode a module within a module by using the special '&'
# character to interpose another module into the current module. This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
lib-win32 -a lib/mozilla/js/win32.release lib/mozilla/nspr/win32.release lib/microsoft lib/cryptlib
lib-win32.release -a lib/mozilla/js/win32.release lib/mozilla/nspr/win32.release lib/microsoft lib/cryptlib
lib-win32.debug -a lib/mozilla/js/win32.debug lib/mozilla/nspr/win32.release lib/microsoft lib/cryptlib
lib-linux -a lib/mozilla/js/linux.release lib/mozilla/nspr/linux.release lib/cryptlib/linux.release
lib-linux.release -a lib/mozilla/js/linux.release lib/mozilla/nspr/linux.release lib/cryptlib/linux.release
lib-linux.debug -a lib/mozilla/js/linux.debug lib/mozilla/nspr/linux.debug lib/cryptlib/linux.release
lib-linux-x64 -a lib/cryptlib/linux.x64.release
lib-linux-x64.release -a lib/cryptlib/linux.x64.release
lib-linux-x64.debug -a lib/cryptlib/linux.x64.release
lib-freebsd -a lib/mozilla/js/freebsd.release lib/mozilla/nspr/freebsd.release lib/cryptlib/freebsd.release
lib-freebsd.release -a lib/mozilla/js/freebsd.release lib/mozilla/nspr/freebsd.release lib/cryptlib/freebsd.release
lib-freebsd.debug -a lib/mozilla/js/freebsd.debug lib/mozilla/nspr/freebsd.debug lib/cryptlib/freebsd.release
lib-openbsd -a lib/mozilla/js/openbsd.release lib/mozilla/nspr/openbsd.release lib/cryptlib/openbsd.release
lib-openbsd.release -a lib/mozilla/js/openbsd.release lib/mozilla/nspr/openbsd.release lib/cryptlib/openbsd.release
lib-openbsd.debug -a lib/mozilla/js/openbsd.debug lib/mozilla/nspr/openbsd.debug lib/cryptlib/openbsd.release
lib-netbsd -a lib/mozilla/js/netbsd.release lib/mozilla/nspr/netbsd.release lib/cryptlib/netbsd.release
lib-netbsd.release -a lib/mozilla/js/netbsd.release lib/mozilla/nspr/netbsd.release lib/cryptlib/netbsd.release
lib-netbsd.debug -a lib/mozilla/js/netbsd.debug lib/mozilla/nspr/netbsd.debug lib/cryptlib/netbsd.release
src-sbbs3 -a src/build src/sbbs3 src/xpdev src/smblib src/uifc include src/conio src/sexpots src/comio
run-sbbs3 -a ctrl text exec xtrn node1 node2 node3 node4 docs web
syncterm -a src/syncterm src/build src/conio src/uifc src/xpdev src/comio src/sbbs3/telnet.c src/sbbs3/telnet.h src/sbbs3/xmodem.c src/sbbs3/xmodem.h src/sbbs3/zmodem.c src/sbbs3/zmodem.h src/sbbs3/sexyz.h src/smblib/crc16.c src/smblib/crc16.h src/smblib/crc32.c src/smblib/crc32.h
install install
include include
lib lib
src src
docs docs
ctrl ctrl
text text
exec exec
xtrn xtrn
web web
CVSROOT/notify deleted 100755 → 0
+ 0
− 12
View file @ 1d851511
# The "notify" file controls where notifications from watches set by
# "cvs watch add" or "cvs edit" are sent. The first entry on a line is
# a regular expression which is tested against the directory that the
# change is being made to, relative to the $CVSROOT. If it matches,
# then the remainder of the line is a filter program that should contain
# one occurrence of %s for the user to notify, and information on its
# standard input.
#
# "ALL" or "DEFAULT" can be used in place of the regular expression.
#
# For example:
#ALL mail %s -s "CVS notification"
CVSROOT/postadmin deleted 100755 → 0
+ 0
− 15
View file @ 1d851511
# The "postadmin" file is called after the "admin" command finishes# processing a directory.#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/postproxy deleted 100755 → 0
+ 0
− 19
View file @ 1d851511
# The "postproxy" file is called from a secondary server as soon as
# the secondary server closes its connection to the primary server.
# This script might, for example, be used to shut down a dial up
# or VPN connection to the primary server's network.
#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository (currently always ".")
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/posttag deleted 100755 → 0
+ 0
− 31
View file @ 1d851511
# The "posttag" file is called after the "tag" command finishes# processing a directory.#
# If any format strings are present in the filter, they will be replaced as follows:
# %b = branch mode = "?" (delete ops - unknown) | "T" (branch) | "N" (not branch)
# %o = operation = "add" | "mov" | "del"
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %t = tagname
# %{sVv} = attribute list = file name, old version tag will be deleted
# from, new version tag will be added to (or deleted from, but
# this feature is deprecated. When either old or new revision is
# unknown, doesn't exist, or isn't applicable, the string "NONE"
# will be placed on the command line.
#
# Note that %{sVv} is a list operator and not all elements are necessary.
# Thus %{sV} is a legal format string, but will only be replaced with file
# name and old revision. it also generates multiple arguments for each file
# being operated upon. i.e. if two files, file1 & file2, are having a tag
# moved from version 1.1 to version 1.1.2.9, %{sVv} will generate the
# following six arguments in this order: file1, 1.1, 1.1.2.9, file2, 1.1,
# 1.1.2.9.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/postwatch deleted 100755 → 0
+ 0
− 17
View file @ 1d851511
# The "postwatch" file is called after any command finishes writing new
# file attibute (watch/edit) information in a directory.
#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/preproxy deleted 100755 → 0
+ 0
− 21
View file @ 1d851511
# The "preproxy" file is called form the secondary server as soon as
# the secondary server determines that it will be proxying a write
# command to a primary server and immediately before it opens a
# connection to the primary server. This script might, for example, be
# used to launch a dial up or VPN connection to the primary server's
# network.
#
# If any format strings are present in the filter, they will be replaced# as follows:
# %p = path relative to repository (currently always ".")
# %r = repository (path portion of $CVSROOT)
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/rcsinfo deleted 100755 → 0
+ 0
− 13
View file @ 1d851511
# The "rcsinfo" file is used to control templates with which the editor
# is invoked on commit and import.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being made to, relative to the
# $CVSROOT. For the first match that is found, then the remainder of the
# line is the name of the file that contains the template.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/taginfo deleted 100755 → 0
+ 0
− 20
View file @ 1d851511
# The "taginfo" file is used to control pre-tag checks.
# The filter on the right is invoked with the following arguments:
#
# $1 -- tagname
# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
# $3 -- repository
# $4-> file revision [file revision ...]
#
# A non-zero exit of the filter program will cause the tag to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/verifymsg deleted 100755 → 0
+ 0
− 21
View file @ 1d851511
# The "verifymsg" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
docs/64bit.txt deleted 100644 → 0
+ 0
− 65
View file @ 1d851511
Notes on building Synchronet on 64-bit *nix systems
===================================================
The 64-bit port is a relatively new effort on the part of the Synchronet
developers. Since none of the active developers are currently running 64-bit
OSs, progress on this port is relatively slow. However, the BBS itself and
the scfg utility have been ported to 64-bit and appear to be working correctly.
A few extra steps must be used to get a working build of Synchronet for 64-bit
platforms:
1) /usr/include/inttypes.h MUST exist.
This is a C99 file which includes stdint.h which defines size-based
integer types. Without this file, Synchronet will not know the sizes
of the integer types and will therefore assume 32-bit hardware.
If this include file does not exist, you will need to obtain it from
somewhere or not attempt a 64-bit Synchronet build.
2) The included libraries are not for 64-bit platforms and so must be installed
using other methods. The libraries in question are:
cryptlib - Used for the SSH support
Available from http://www.cs.auckland.ac.nz/~pgut001/cryptlib/
spidermonkey (THREADED) - Used for JavaScript support
The easiest way to get a threaded spidermonkey is to install
a native Mozilla browser such as Firefox
nspr4 - Used by spidermonkey
Installing a Mozilla browser will also install an nspr4 library
however, you will also need 64-bit capable nspr4 headers.
Your platform should have an nspr4 development package
available which should be installed
SDL - *OPTIONAL* - Used by scfg and other console based utilities.
Available from http://www.libsdl.org/
This package is not required for building or running anything
but does allow extra capabilities that other methods do not.
3) Specifying library and include file locations
Library and header locations can be passed on the make command-line if they
are not in standard locations (/usr/local/include, /usr/local/lib,
/usr/local/lib64, /usr/include, /usr/lib, and /usr/lib64)
cryptlib:
Specify the path the the header files using the CRYPTLIBINCLUDE
macro.
ex: ``make CRYPTLIBINCLUDE=/usr/local/include/cl''
Specify the path to the library file using the CRYPTLIBDIR
macro.
spidermonkey:
Specify the NAME of the library (without the lib prefix or any
file suffixes) using the JSLIB macro. For Mozilla browsers,
the library name would be ``moxjs''
ex: ``make JSLIB=mozjs''
Specify the path the the library file using the JSLIBDIR macro.
The include files that come with Synchronet SHOULD work.
However, if they don't, you can specify the path using the
JSINCLUDE macro.
nspr4:
Specify the path to the library using the NSPRDIR macro and
the path to the include files using the NSPRINCLUDE macro.
SDL:
Specify the complete path to the sdl-config program using the
SDL_CONFIG macro.
ex: ``make SDL_CONFIG=/usr/local/bin/sdl-config''
4) When reporting bugs, be SURE to mention that you are running a 64-bit build
and be prepared to follow instructions which may involve debugging and the
use of core files. Be absolutely sure to configure your system to save core
files in the event of a crash of Synchronet.
docs/_borders/bottom.htm deleted 100644 → 0
+ 0
− 42
View file @ 1d851511
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>Shared Bottom Border</title>
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta name="Microsoft Border" content="none">
</head>
<body>
<hr>
<p><b><a href="http://www.synchro.net/copyright.html">Copyright</a> 2006 by </b> <a href="http://www.synchro.net/author.htm"><b>Rob Swindell</b><br>
</a>
<a href="http://www.synchro.net"><font size="2"><br>
Synchronet BBS Software</font></a> <font size="2"> (Synchronet)
Version 3 is comprised of several documentation,<br>
library, executable, and <a href="http://www.synchro.net/source.html">source code</a>
files, all of which are covered by the<a href="http://www.fsf.org/copyleft/gpl.html">
<br>
GNU General Public License</a> with the exception of the following portions
covered by<br>
the <a href="http://www.fsf.org/copyleft/lesser.html">GNU Lesser General Public License</a>:
SMBLIB and XSDK.<br>
<br>
Synchronet Version 2 (for DOS and OS/2) and its source code was released to the<a href="http://www.fsf.org/philosophy/categories.html#PublicDomainSoftware">
<br>
Public Domain</a> by <a href="ftp://vert.synchro.net/main/sbbs/manifest.txt">Digital Dynamics</a>
in 1997 and remains Public Domain software today.<br>
Synchronet Version 3 is not Public Domain software.</font></p>
<p align="left"><font size="2"><a href="http://www.synchro.net">http://www.synchro.net</a>
</font></p>
<p align="left"><font size="2">For the complete Copyright Information please
read the <a href="http://www.synchro.net/copyright.html">Copyright Document</a>
.</font></p>
</body>
</html>
\ No newline at end of file
docs/_borders/top.htm deleted 100644 → 0
+ 0
− 17
View file @ 1d851511
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=IBM437">
<title>Shared Top Border</title>
<meta name="Microsoft Border" content="none">
</head>
<body>
<a href="http://www.synchro.net"><img border="0" src="../images/synclogo_fancyred.png" alt="Synchronet BBS - Multinode Bulletin Board Software" width="626" height="86"></a>
<hr>
</body>
</html>
docs/adding_nodes.html deleted 100644 → 0
+ 0
− 149
View file @ 1d851511
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=IBM437">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Adding Nodes</title>
</head>
<body>
<!--webbot bot="Include" U-Include="_borders/top.htm" TAG="BODY" startspan --><p>
<a href="http://www.synchro.net">
<img border="0" src="images/synclogo_fancyred.png" alt="Synchronet BBS - Multinode Bulletin Board Software" width="626" height="86"></a>
</p>
<hr>
<!--webbot bot="Include" endspan i-checksum="56836" -->
<p><b><a name="top"></a></b><a href="sysop.html#TOC">Back to Table of Contents</a></p>
<h2><a name="AddingNodes">[3.0] - Adding Nodes</a></h2>
<pre>Run SCFG. Select Nodes from the main menu. Hit INS (insert key) to create
additional nodes. Each added node will have the configuration options copied
from the last node. No configuration changes should be necessary.
</pre>
<pre><b>SBBSCTRL-Windows:</b>
If you'd like all nodes to be available for telnet logins, set the
<b> Last Node</b> in the telnet configuration dialog to your highest
configured node number.</pre>
<pre> <img border="0" src="images/sbbsctrl_telnet_cfg_gen.png" width="358" height="318"></pre>
<pre> All nodes controlled by the same instance of SBBSCTRL will use the
configuration information for the node specified as the <b>First Node
</b> in the telnet configuration dialog.</pre>
<pre>Alternatively, you can edit the <i>LastNode</i> value in the <i>[BBS]</i> section of your
Synchronet initialization file (e.g. <i>ctrl/sbbs.ini</i>).</pre>
<h2><a name="ConfiguringNodes">[3.1] - Configuring Nodes</a></h2>
<pre>To configure a node, select &quot;<i>Nodes</i>&quot; from the SCFG &quot;<i>Configure</i>&quot; menu. You will
then see a list of all the nodes installed on your system. You will also see
the bottom line of the screen now has two additional key commands added, <i>INS
</i>(Insert) and <i>DEL</i> (Delete). INS and DEL are used to add and delete nodes from
the system. If you select one of the nodes listed, you will receive another
menu as follows:</pre>
<pre><img border="0" src="images/scfg_node1.png" width="652" height="331"></pre>
<pre>
<b>Logon Requirements:
</b> Use this option to set specific requirements to logon this node.</pre>
<h2><a name="NodeToggleOptions">[3.2] - Node Toggle Options</a></h2>
<pre><img border="0" src="images/scfg_node1_toggles.png" width="652" height="331">
<b>Allow Logon by Number:
</b> Setting this option to 'Yes' will allow users to logon by typing their
user number at the login logon prompt.
<b>Allow Logon by Real Name:
</b> When set to 'Yes' this option allows users to enter their real name
(or company name) at the login prompt to logon to the BBS.
<b>Always Prompt for Password:
</b> When set to 'Yes' this option will cause the user to ALWAYS be prompted
for a password at logon, even if they have entered an incorrect (non-
existent) user name at the login prompt.
<b>Allow 8-bit Remote Logons:
</b> To allow E-7-1 terminals to use this node, set this option to 'No'.
This will also eliminate the ability of 8-bit remote users to send
IBM extended ASCII characters during the logon sequence.</pre>
<pre><b>Spinning Pause Prompt:</b>
To disable the spinning cursor on screen-pause prompts, set this option
to 'No'.</pre>
<pre><b>Keep Node File Open:</b>
It can benefit performance to leave the node file (ctrl/node.dab) open.
If you have problems with the node file being read correctly across network
drives (on a LAN), try setting this option to 'No'.</pre>
<h2><a name="NodeAdvancedOptions">[3.3] - Node Advanced Options</a></h2>
<pre>When selecting this option, you will be brought to a sub-menu of options as
follows:</pre>
<pre><img border="0" src="images/scfg_node1_advanced.png" width="652" height="331">
<b>Validation User:
</b> This is the number of the user to whom validation feedback is sent.
This value will usually be set to 1 (the sysop). If this value is set
to 0, then <b>new users will not be required to enter validation feedback</b>.
<b>Semaphore Frequency:
</b> This option specifies how often (in seconds) this node should perform
semaphore checks (e.g. checks to see if an event should be run, the
node should be downed, etc.).
<b>Statistics Frequency:
</b> This options specifies how often (in seconds) this node should check
system statistics (calls per day, logons today, etc.).
<b>Inactivity Warning:
</b> This is the number of seconds of user inactivity before a warning
(typically: &quot;Username, are you still there?&quot;) is displayed to the
user.
<b>Inactivity Disconnection:
</b> This is the number of seconds of user inactivity before the user
is automatically disconnected.
<b>Daily Event:
</b> This is the command line to execute when the first caller after
midnight logs off. If the program is located in the EXEC directory,
this command line should start with the %! specifier.
<b>Text Directory:
</b> This is the path to the text directory. This is where all menus,
macros, SIF files, QWK files, system information, and other text
files are stored.</pre>
<p><a href="#top"><b>Back to Top</b></a></p>
<!--webbot bot="Include" U-Include="_borders/bottom.htm" TAG="BODY" startspan -->
<hr>
<p><b><a href="http://www.synchro.net/copyright.html">Copyright</a> © 2006 by </b> <a href="http://www.synchro.net/author.htm"><b>Rob Swindell</b><br>
</a>
<a href="http://www.synchro.net"><font size="2"><br>
Synchronet BBS Software</font></a> <font size="2"> (Synchronet)
Version 3 is comprised of several documentation,<br>
library, executable, and <a href="http://www.synchro.net/source.html">source code</a>
files, all of which are covered by the<a href="http://www.fsf.org/copyleft/gpl.html">
<br>
GNU General Public License</a> with the exception of the following portions
covered by<br>
the <a href="http://www.fsf.org/copyleft/lesser.html">GNU Lesser General Public License</a>:
SMBLIB and XSDK.<br>
<br>
Synchronet Version 2 (for DOS and OS/2) and its source code was released to the<a href="http://www.fsf.org/philosophy/categories.html#PublicDomainSoftware">
<br>
Public Domain</a> by <a href="ftp://vert.synchro.net/main/sbbs/manifest.txt">Digital Dynamics</a>
in 1997 and remains Public Domain software today.<br>
Synchronet Version 3 is not Public Domain software.</font></p>
<p align="left"><font size="2"><a href="http://www.synchro.net">http://www.synchro.net</a>
</font></p>
<p align="left"><font size="2">For the complete Copyright Information please
read the <a href="http://www.synchro.net/copyright.html">Copyright Document</a>
.</font></p>
<!--webbot bot="Include" endspan i-checksum="15291" -->
</body>
</html>
\ No newline at end of file
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment