<H2><A NAME="ss7.12">7.12 init (5)</A>
</H2>
-<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
+<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
<P>
<P>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
<H2><A NAME="ss7.26">7.26 set/debug (9)</A>
</H2>
-<P><CODE><B>set/debug <name></B>Add a debug level to the debug set</CODE>
+<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
<P>
<P>You can remove this level with unset/debug <name>
<P>
<H2><A NAME="ss7.28">7.28 set/sys_location (9)</A>
</H2>
-<P><CODE><B>set/sys_location <lat & long></B>Set your cluster latitude and longitude</CODE>
+<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
<P>
<P>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
<H2><A NAME="ss7.29">7.29 set/lockout (9)</A>
</H2>
-<P><CODE><B>set/lockout <call></B>Stop a callsign connecting to the cluster</CODE>
+<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
<P>
<P>You can show who is locked out with the show/lockout (9) command.
<P>To allow the user to connect again, use the command unset/lockout
<H2><A NAME="ss7.30">7.30 set/node (9)</A>
</H2>
-<P><CODE><B>set/node <call> [<call> ...]</B>Make the callsign an AK1A cluster</CODE>
+<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
<P>
<P>Tell the system that the call(s) are to be treated as AK1A cluster and
fed PC Protocol rather normal user commands.
<H2><A NAME="ss7.37">7.37 shutdown (5)</A>
</H2>
-<P><CODE><B>shutdown</B>Shutdown the cluster</CODE>
+<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
<P>
<P>Shutdown the cluster and disconnect all the users. If you have Spider
set to respawn in /etc/inittab it will of course restart.
<P>
-<H2><A NAME="ss7.38">7.38 stat/db (5)</A>
+<H2><A NAME="ss7.38">7.38 spoof (9)</A>
+</H2>
+
+<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
+<P>
+<P>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.
+<P>
+<H2><A NAME="ss7.39">7.39 stat/db (5)</A>
</H2>
<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
<P>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.
<P>
-<H2><A NAME="ss7.39">7.39 stat/channel (5)</A>
+<H2><A NAME="ss7.40">7.40 stat/channel (5)</A>
</H2>
<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
you are on or else for the callsign that you asked for.
<P>Only the fields that are defined (in perl term) will be displayed.
<P>
-<H2><A NAME="ss7.40">7.40 stat/msg (5)</A>
+<H2><A NAME="ss7.41">7.41 stat/msg (5)</A>
</H2>
<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
<P>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.
<P>
-<H2><A NAME="ss7.41">7.41 stat/user (5)</A>
+<H2><A NAME="ss7.42">7.42 stat/user (5)</A>
</H2>
<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>