X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-7.html;h=af763d048ddda64cf923278fc9c8d190162ca0dd;hb=699e2b8f9d924df78f55f69dfeded213f158b121;hp=5a60b9dec1e6b1ec2fc43e966ff08d292dce8085;hpb=4fa8a0251b64361c908d056393b46abece6d38be;p=spider.git diff --git a/html/adminmanual-7.html b/html/adminmanual-7.html index 5a60b9de..af763d04 100644 --- a/html/adminmanual-7.html +++ b/html/adminmanual-7.html @@ -182,7 +182,7 @@ and Homenode. PC41s are only sent for the information that is available.

7.12 init (5)

-

init <node call> Re-initialise a link to an AK1A compatible node +

init <node call> Re-initialise a link to an AK1A compatible node

This command attempts to re-initialise a link to a (usually) AK1A node that has got confused, usually by a protocol loop of some kind. It may @@ -343,7 +343,7 @@ permission to send this command at all.

7.26 set/debug (9)

-

set/debug <name>Add a debug level to the debug set +

set/debug <name> Add a debug level to the debug set

You can remove this level with unset/debug <name>

@@ -362,7 +362,7 @@ out from it nor goes back into from the rest of the nodes connected to you.

7.28 set/sys_location (9)

-

set/sys_location <lat & long>Set your cluster latitude and longitude +

set/sys_location <lat & long> Set your cluster latitude and longitude

In order to get accurate headings and such like you must tell the system what your latitude and longitude is. If you have not yet done a SET/QRA @@ -372,7 +372,7 @@ then this command will set your QRA locator for you. For example:-

7.29 set/lockout (9)

-

set/lockout <call>Stop a callsign connecting to the cluster +

set/lockout <call> Stop a callsign connecting to the cluster

You can show who is locked out with the show/lockout (9) command.

To allow the user to connect again, use the command unset/lockout @@ -380,7 +380,7 @@ then this command will set your QRA locator for you. For example:-

7.30 set/node (9)

-

set/node <call> [<call> ...]Make the callsign an AK1A cluster +

set/node <call> [<call> ...] Make the callsign an AK1A cluster

Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands. @@ -475,12 +475,22 @@ is useful for checking where you think you have loaded a .pm file from.

7.37 shutdown (5)

-

shutdownShutdown the cluster +

shutdown Shutdown the cluster

Shutdown the cluster and disconnect all the users. If you have Spider set to respawn in /etc/inittab it will of course restart.

-

7.38 stat/db (5) +

7.38 spoof (9) +

+ +

spoof <callsign> <command> Run commands as another user +

+

This is a very simple yet powerful command for the sysop. It allows you to +issue commands as if you were a different user. This is very useful for the +kind of things that users seem to always get wrong.. like home_node for +example. +

+

7.39 stat/db (5)

stat/db <dbname> Show the status of a database @@ -489,7 +499,7 @@ set to respawn in /etc/inittab it will of course restart.

Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

-

7.39 stat/channel (5) +

7.40 stat/channel (5)

stat/channel <callsign> Show the status of a channel on the cluster @@ -498,7 +508,7 @@ This command is unlikely to be of much use to anyone other than a sysop. you are on or else for the callsign that you asked for.

Only the fields that are defined (in perl term) will be displayed.

-

7.40 stat/msg (5) +

7.41 stat/msg (5)

stat/msg <msgno> Show the status of a message @@ -506,7 +516,7 @@ you are on or else for the callsign that you asked for.

This command shows the internal status of a message and includes information such as to whom it has been forwarded, its size, origin etc etc.

-

7.41 stat/user (5) +

7.42 stat/user (5)

stat/user <callsign> Show the full status of a user