This is an old revision of the document!
Table of Contents
The sysop (System Operator) is the administrator that runs the BBS, and they have unlimited access and control over their instance of Synchronet and its users. When networked with other systems (e.g., DOVE-Net, FidoNet, inter-BBS chat), they are often considered responsible for any traffic originating from their system, including misconfigurations and any of their users' poor behavior.
There is usually one sysop per BBS, though Synchronet can be configured for multiple sysops (sometimes called co-sysops). In Synchronet, any user with a security level at or above 90 is considered a sysop.
Depending on the “Require Sys Pass During Login” in SCFG System Configuration under Toggle Options, the sysop will either be required to enter the system password at login or when performing a sysop-level function. Synchronet will prompt with
SY: when asking for the system password.
Multiple Sysops / Co-Sysops
Multiple levels of sysop access (90-99) can be used to restrict some areas (i.e., message groups, sub-boards, file libraries, etc.) by setting the minimum required level of that area higher than the sysop's security level.
Any user with a security level at or above 90 can perform sysop functions, including
;SHELL access with the same OS permissions as the OS user that the BBS runs as.
Using the in-BBS
;UEDIT user editor, a sysop with security level at or above 90 cannot edit a sysop with a higher security level.
;SHELL can potentially give access to the useredit application that allows full user editing privileges, however.
Users with sysop access can cause damage to the BBS, as well as compromise the underlying operating system. Give out sysop-level access with caution.
A menu of the available commands can be viewed with the '!' command from the main or transfer sections with the Synchronet Classic command shell. Additional sysop commands are available in many other sections of the BBS and are displayed after the normal menu with the '?' command. All sysop commands from the main or transfer sections of the Synchronet Classic command shell begin with a semicolon (';') character, end with CR (ENTER), and some have optional parameters (shown in square brackets). Users with certain exemptions can use some of these commands and have access to the menus via the '!' command using the Synchronet Classic command shell.
Note: The Baja source code file for these commands is: exec/str_cmds.src
- All commands are preceded by a
|NODE [parameters]||Node utility||Executes the node utility with the passed parameters.|
|DOWN [#]||Down node||A sysop can toggle the down status of a node with this command. When a node has the down status (noted by the [D] flag on the node status line) it will be shut down immediately after the user logs off. If a user is not online, it will shut down immediately. If a node [#] is not specified, the current node will be shut down.|
|LOCK [#]||Lock node||The sysop can use this command to prevent users logging onto a node until the lock is removed. If [#] is specified, that node's lock status will be toggled. validate –> Sysops and users with the 'L' exemption can use this command and log onto locked nodes. A locked node will have an (L) in the node listings.|
|INTR [#]||Interrupt node|| This command allows a sysop (or user with the
|ANON||Toggle anonymous mode|| Makes the current node anonymous, where the node is listed as online but the user is not. Sysops and users with the
|QUIET||Quiet mode|| Using this command, a sysop (or user with the
To a sysop, a node in this state appears normal, with the addition of a [Q] in the node information line.
|UEDIT [user number or name]||User editor|| This command initiates the User Edit function. If user is specified, it will be the current user when User Edit starts.
See the chapter on User Edit for more information.
|EDIT [filename]||File editor||Edit any ASCII text or MSG format files on the system using your message editor. If [filename] is given it will be opened, or it will be created if it doesn't exist. If [filename] is not specified, the filename will be prompted for.|
|TYPE [filename]||View text/msg file|| View any ASCII text or MSG format file on the system, starting from the
|LOG||Today's log||View today's detailed log file.|
|YLOG||Yesterday's log||View yesterday's detailed log file.|
|NS [#]||Node statistics||Today's statistics for node [#] if specified, or will prompt for the desired node.|
|SS||System statistics||Today's statistics for all nodes combined.|
|NLOG [#]||Node statistics log||View the history of statistics information for a single node on the system. If [#] is specified, that will be the node who's statistics are viewed, otherwise the current node will be used.|
|SLOG||System statistics log||View the history of statistics information for the system.|
|ERR||Critical error log||View the error log and optionally delete it, as well as optionally clearing all nodes' error counters.|
|GURU||Guru log||Display and optionally clear the GURU.LOG file that contains user discussions with the system guru (GURU.DAT).|
|Read all mail||Read all the email on in the mail base.|
|SPY [#]||Spy on a node||Allows the sysop to remotely monitor or control another node.|
|ECHO [string]||Print a text message||Prints a string, including Message Variables (@-codes).|
|CHUSER||Change to another user||Allows the sysop to temporarily change to another user account. If changing to an account with a higher level, the password of that user must be given. Changing to a user of non-sysop status automatically enables Temp Sysop mode so that the sysop can change back to their own account before logging off (a suggested action).|
|BULKMAIL||Send mass mail||Sends an email to all users that match a specified ARS. ←– what does ARS mean?|
|SHELL||OS command shell||Executes the native shell (COMSPEC or SHELL env variable.|
|CALL <Hub-ID>||Force QWKnet callout|| Forces a QWKnet callout to the <Hub-ID>. Example:
|EXEC [command]||Execute a command with I/O redirected||Execute internal DOS commands (DIR, TYPE, etc.) by prepending “command /c” to your command line. Execute Baja modules by prepending “*” to the command line. Baja modules must be located in your EXEC directory. Command line specifiers (see appendix A) may be used.|
|NEXEC [command]||Execute native binary with I/O redirected|
|FOSSIL [command]||Execute FOSSIL driver command|
|AVAIL||Toggle sysop chat availability|
|EVENT [EventID]||Execute event||Forces a timed event to execute via semfile.|
|LOAD [filespec]||Load filespec||Loads the text.dat from the specified filespec.|
|POFF||Pager off||Toggles if other users can page you for this session.|
|PLAN||Edit .plan file||Edits or deletes your .plan file (displayed when somebody fingers you.|
|FIND [word]||Find a message area or file area|
|MSGS||Redisplay messages||Redisplay instant messages (notifications and telegrams).|
Other Commands from Old Docs
|RERUN [#]||Rerun node||Rerun any node on the system. ←- What is rerun? If there is a user on the node, it will not rerun until that user logs off. A node that is going to be rerun is noted with an [R] in the node listing.|
|DOS||DOS command shell||Go to the DOS command line with I/O redirected.|
|CHAT||Page sysop|| Users with the
|DIR [path]||List files||Displays a directory listing of the path specified. If no path is specified, a list of the current file transfer area is displayed.|
|GET [path]||Download file||Download a file from any directory on the system. The file does not have to be in the file database.|
|PUT [path]||Upload file||Upload a file to the system without having to add it to the file database.|