Sysop

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 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 ;
• <> required parameter
• [] optional parameter
• () required exemption

For any commands where a path is requested, the current working directory is ctrl/

Command	Name	Description
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.
FOSSIL [command]	Execute FOSSIL driver command
NEXEC [command]	Execute native binary with I/O redirected
DIR [path]	List files	Displays a directory listing of the specified path.
GET [path/file]	Download file	Download a file from any directory on the BBS host system. The file does not have to be in the file database.
PUT [path/file]	Upload file	Upload a file to any directory on the BBS host system without having to add it to the file database.
TYPE [path/file]	View text/msg file	View any ASCII text or MSG format file on the system. Aliases CAT or LIST also invoke this command.
EDIT [path/file]	File editor	Edit any ASCII text or MSG format file on the system using your message editor. If the specified filename does not already exist it will be created.
DOS	DOS command shell	Go to the Windows/DOS command line (command.com) with I/O redirected.
SHELL	Unix command shell	Starts a native Unix shell (COMSPEC or SHELL env variable).

• Access Control