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
;sysop menu has misspelling
|NODE [args]||Node Utility|
|DOWN [x]||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 shutdown immediately after the user logs off. If a user is not online, it will shutdown immediately.|
|LOCK [x]||Lock Node||The sysop can use this command to prevent users logging onto a node until the lock is removed. If 'x' is specified, that node's lock status will be toggled, otherwise a list of all nodes is given and the sysop is prompted for the node to lock or unlock. Sysops and users with the 'L' exemption can use this command and log onto locked nodes. A locked node will have an 'L' in parenthesis after the node information in the node listings.|
|INTR [x]||Interrupt Node||This command allows a sysop (or user with the 'I' exemption) to hang up on a user on another node. If the user is currently executing an external program (editors and transfer protocols included), he will not be disconnected until control returns to Synchronet. A message will be displayed telling the user that the node has been temporarily closed for maintenance before carrier is dropped. If 'x' is specified that node's interrupt status will be toggled, otherwise a list of all nodes is displayed and the sysop is prompted for the node who's interrupt state he wishes to toggle. The current interrupt status of a node is reflected by an 'I' in square brackets following the node information line in the node listings.|
|ANON||Anonymous||This command makes the current node anonymous. Sysops and users with the 'Q' exemption have access to this command. To a sysop, an anonymous node appears normal with the addition of an 'A' in square brackets following the node information line.|
|QUIET||Quiet Mode|| Using this command, a sysop (or user with the 'Q' exemption) can make his node appear to be “Waiting for call” to other users of the system. Users with this ability can also make this state their default state upon logon in the user defaults section. Local users can logon in this state with the WFC command SPACE, then 'Z' or user number 1 can logon fast and quiet with the WFC command SPACE, then 'Q'.
To a sysop, a node in this state appears normal with the addition of a 'Q' in square brackets following the node information line.
|UEDIT [x]||User Edit|| This command initiates the User Edit function. If 'x' is specified and is a valid user number, that user will be the current user when User Edit starts, otherwise the user online will be the current user. This command is also available from the transfer menu. Locally, Alt-U is the preferred method of initiating User Edit.
See the chapter on User Edit for more information.
|EDIT [s]||Edit Text/MSG File||A sysop can edit any ASCII text (and MSG format) files on the system with this command. If 's' is given, it will be used as the filename to be opened or created if it doesn't exist. If 's' is not specified, the filename will be prompted for.|
|LIST [s]||View Text/MSG File||A sysop can use this command to view any ASCII text (or MSG format) file on the system. If the filename 's' is not specified, it is prompted for.|
|LOG||Today's Detail Log||A sysop can view today's detailed log file with this command. This command views the same file as the 'L' wait for call screen command.|
|YLOG||Yesterday's Detail Log||A sysop can view yesterday's detailed log file with this command. This command views the same file as the 'Y' wait for call screen command.|
|NS [x]||Node Statistics||This command will give today's statistics for node 'x' if specified, or the current node.|
|SS||System Statistics||This command will give today's statistics for all nodes combined.|
|NLOG [x]||Node Statistics Log||A sysop can view the history of statistics information for any node on the system. If 'x' is specified, that will be the node who's statistics are viewed, otherwise the current node. Same as 'N' from the wait for call screen.|
|SLOG||System Statistics Log||Using this command, a sysop can view the history of statistics information for the system. Same as 'S' from the wait for call screen.|
|ERR||Critical Error Log|
|GURU||View Guru Log||A sysop can use this command to view the GURU.LOG file which contains discussions that users have had with the system guru (GURU.DAT). See GURU.DAT for more information.|
|Read All Mail||Using this command (or 'M' from the WFC screen) a sysop can read all the e-mail on the system.|
|SPY [n]||Spy on Another User||This command allows the sysop to remotely monitor or control another node running in the same instance as the node the sysop is logged into.|
|ECHO <str>||Print string (w/@-codes)|
|CHUSER||Change into Another User||This command 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 an account of non-sysop status automatically enables Temp Sysop mode so that the sysop can change back to his/her own account before logging off (a suggested action).|
|BULKMAIL||Send Mass Mailing||Use this command to send a single e-mail message to multiple users.|
|SHELL||OS Command Shell|
|CALL [Hub-ID]||Force QWKnet Call-out||Forces a QWKnet call-out to the hub “Hub-ID” the next time the call-out node is at the WFC screen. Example: CALL VERT|
|EXEC [Command]||Execute a DOS program or Baja module||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 <cmd>||Execute Native Program|
|FOSSIL <cmd>||Execute FOSSIL Program|
Other Commands from Old Docs
|RERUN [x]||Rerun Node||This command allows a sysop to rerun any node on the system by specifying the node number on the command line. If there is a user on the node that is to be rerun, the node will not rerun until that user logs off. A node that is going to be rerun is noted with an 'R' in square brackets following the node information in node listings.|
|DOS||Shell to DOS||Using this command, a sysop can go straight to the DOS command line locally or remotely. If the sysop is on locally, ALT-D is the preferred method of shelling to DOS. If a local sysop wishes to shell to DOS from the wait for call screen, he can use the 'D' command.|
|CHAT||Users with the 'C' exemption can use this command to page the sysop.|
|OLD||Search for Files not Downloaded Since New-Scan Date||A sysop can use this command to remove, edit, or move files that were uploaded before the new-scan date (set with the '&P' transfer section command) and have not been downloaded since.|
|OLDUL||Search for Files Uploaded Before New-Scan Date||A sysop can use this command to remove, edit, or move files that were uploaded before the new-scan date (set with the '&P' transfer section command).|
|CLOSE||Search for Files Currently Open||If there are no users online and all nodes are running, there should be no file records open. A sysop can check for open file records with this command. Any file records that are left open erroneously, can be closed with this command. This circumstance should not happen.|
|ALTUL [x]||Alternate File Path Uploads||If there are alternate file paths configured, a sysop can use this command to set the current upload path to one of the alternate file paths. All subsequent upload commands will use the alternate upload path as the storage directory regardless of the storage path specified for the directory being uploaded to. This is a useful command for those who wish to have one directory with files listed from multiple CD-ROMs.|
|UPLOAD||Bulk Local Upload||This command searches for files that are on disk, but not in the database of the directory. If any are found, a description is prompted for and the file is then added to the database.|
|RESORT||Re-Sort and/or Compress||A sysop can use this command to re-sort a directory if he has changed the sort order in the directory configuration or can use this command to remove deleted file records from the database to conserve memory and disk space. If there are many deleted files in the database of a directory, performance will also be affected. Deleted file records are used by new uploaded files, but if a substantial amount of files have been removed from a directory, a sysop may wish to use this command.|
|OFFLINE||Search for Offline Files||This command will search the disk for files that are in the database of a directory but not actually on the disk. The sysop can then remove, edit, or move these files to another directory. Offline directories are ignored in this search.|
|DIR [s]||Directory of Files||This command displays a DOS directory of the path specified. If no path is specified, a directory of the current file transfer directory is displayed.|
|GET [s]||Download File From Anywhere||A sysop can download a file from any drive or directory on the system by using this command. The file does not have to be in the file database.|
|PUT [s]||Upload File to Anywhere||A sysop can use this command to upload a file to a local disk without having to add it to the file database.|