| Next revision | Previous revision |
| access:sysop [2022/02/28 13:28] – created Andre | access:sysop [2022/04/13 19:04] (current) – Moved string commands into their own page. Andre |
|---|
| ====== Sysop ====== | ====== Sysop ====== |
| There is usually one sysop (System Operator) per BBS - the owner and operator of the hardware which Synchronet is running on and accepting remote users. Quite often systems require more than one sysop and Synchronet is flexible in this respect. Within Synchronet, a sysop is defined as any user with a main level of 90 or above. Any user that qualifies as a sysop, is prompted with an "SY:" to enter the system password at logon. Any time a sysop attempts to perform a sysop function that may breach the system security, he is prompted with an "SY:" to enter the system password before he can proceed. Users with sysop access can cause serious damage to the system. Give out this ability with caution. | The sysop (//**Sys**//tem //**Op**//erator) 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 [[access:level|security level]] at or above 90 is considered a sysop. |
| |
| ===== Multiple Sysops ===== | Depending on the "Require Sys Pass During Login" in [[util:scfg:system|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. |
| As stated above, any user with a security level of 90 or greater can perform sysop functions, "So why have levels 91-99?" you might ask yourself. Well, you can still restrict a user with sysop access from accessing Message Groups or Sub-boards or File Libraries or Directories by setting the minimum required level above that user's level. For example: If you have a remote sysop with a security level of 90, you can still have a Message Group or Sub-board with a minimum required level of 91. Now this remote sysop will not be able to access that Group or Sub-board. While it is true that sysops can edit their own and subordinate user's accounts, they can not edit a sysop of higher level's account (when calling remotely). A remote sysop can't raise any user's level above his own, or add flags or exemptions that he himself doesn't have. | |
| | |
| | |
| ===== Sysop Commands ===== | |
| 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. | |
| | |
| ^ Command ^ Name ^ Description ^ | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| |
| | ===== 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 [[access:level|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. |
| |
| |
| | ===== Sysop Commands ===== |
| | 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. |
| |
| | A detailed listing of available commands and their purpose is available on the [[module:str_cmds|string commands]] page. |
| |
| ===== See Also ===== | ===== See Also ===== |
| * [[:access:index|Access Control]] | * [[:access:index|Access Control]] |
| |
| {{tag>}} | {{tag>access sysop}} |
| |
