ChatCommandsDoc.tioga
Eric Nickell, October 24, 1986 11:12:16 am PDT
A CEDAR COMMAND TOOL SERVER
CEDAR 6.1 — FOR INTERNAL XEROX USE ONLY
ChatCommands
A Cedar Command Tool Server
Eric Nickell
© Copyright 1986 Xerox Corporation. All rights reserved.
Abstract: ChatCommands can be run on a Cedar machine to provide to Pup users a Cedar Command Tool. Its primary use is (1) to provide (appropriately restricted) remote access to server machines, (2) to provide Dorado computing power to DLion users for tasks which are not Summonable (yet), and (3) to provide some Cedar capabilities to user's who are on non-Cedar, but Pup-type, machines.
Created by: Eric Nickell
Maintained by: Eric Nickell <Nickell.pasa>
Keywords: CommandTool, Telnet, Pup, Chat
XEROX Xerox Corporation
Palo Alto Research Center
3333 Coyote Hill Road
Palo Alto, California 94304
For Internal Xerox Use Only
1. Use
Setting It Up
Bringover /Cedar/CedarChest6.1/Top/ChatCommands.df
Make sure that appropriate name are listed in "///STPServer.createAccess". (Actually, with profile option, it is possible to change the name of this file.)
Starting a Server
Syntax: ChatCommands on|off
Note that user's have extremely great capabilities. Consider carefully who should have access to this capability on your machine.
Use from a client
Chat to the machine you would like a CommandTool on. It must be running the ChatCommands stuff and be enabled. It is necessary to "Login" to the chat service first. Do this only once--once you have a CommandTool, the only "Login" command available will be the CommandTool, which will change the logged in user on the server machine.
2. Profile options
ChatCommands.AccessFile: ROPE ← "///STPServer.createAccess" --The filename which determines which users are allowed to use this facility on a particular machine. This profile entry is most appropriate for machineProfile entries.