CODASERVER
Section: Maintenance Commands (8)
Updated: LOCAL
Index
Return to Main Contents
NAME
codaserver - Code distribution aid daemon
SYNOPSIS
codaserver
[
-c
] [
-lfile
] [
-rfile
] [
-t
]
DESCRIPTION
Codaserver
is the server for the code distribution system.
It should be installed on any system where you want clients to be able
to pick up files.
Codaserver
is normally started as necessary by the inet daemon.
To run it in an interactive test mode, use the ``-t'' flag; this will
read commands from standard input and echo results to standard output.
To test the syntax of a codafile, use the ``-r'' flag; this will read
and parse the file, and report any errors to standard output.
Codaserver
reports all transactions to a log file, normally
/usr/spool/log/codalog.
To specify a different log file, use the ``-l'' flag; the name ``-'' is
taken to mean standard output.
For each in decoding the logs, every message is stamped with the process-id
and a sequence number.
See the
coda
manual page for a description of the
Codafile
language.
The ``-c'' flag prints out copyright and version information.
PROTOCOL
The coda server uses a simple protocol running over a TCP stream.
Commands and their responses are exchanged in ASCII, and lines are
terminated by a carriage-return/news line pair.
It is easy to debug the system by connecting to the server with a
telnet(1)
to the right port.
Message Types
Upon first connecting, the server will send an acknowledgement; after
this the server will only reply to messages sent from the client.
Every non-blank line sent to the server will result in one or more
lines of reply that ultimately end with an
ACK
or
NAK
message.
All messages from the server are preceded by a three-character code.
If the fourth character is a space, the server has more data to
send (as in the
help
command); if the fourth character is a dash, this line has the
server's final reply to the client's request.
The following message types are sent by the server:
- ACK
-
The last command successfully completed;
the rest of the line may contain some information.
- NAK
-
the rest of the line should give an explanation for the failure.
- INF
-
Information line intended for the user (e.g., help output).
- DAT
-
Data lines intended for client programs (e.g., file lists).
The rest of the line is interpreted by the client program.
There is currently one type of data line, it describes a file or
directory to be loaded by the client.
After the four-character identifier are the four letters
ITEM
and a space.
The remainder of the line is a set of space-separated key-value
pairs, where the key is a single letter followed by an equal
sign.
The values are all interpreted in a Unix context; numbers are sent
in decimal.
The current keys are:
-
W Type; d for directory, f for file
N Name of the file as text
U The numeric id of the item's owner
G The numeric id of the item's group
M The decimal value of the item's permission bits
S The size of the item in bytes
T The modification date of the file
Server Commands
Commands consist of a word, possibly followed by an argument.
The command word may be in either case.
The coda server understands the following commands:
- GOTO dir
-
The argument is a directory for the server to
chdir(2)
to.
This command is not as useful as it used to be.
- HELP
-
Describe the available commands.
- HOST name
-
Set the name of the apparent destination host.
This command is only available in test mode.
The host name is converted to uppercase.
- LIST [block]
-
After a
read
command, this will list walk through the directories listed in the
Codafile and send a set of data line listing all the files and
directories that are applicable for the client system.
If no block name is given, all applicable blocks in the file are walked.
- MESG [text]
-
The text is written to the server's log file.
- QUIT
-
The server exits.
- READ [file]
-
Read the indicated Codafile; the default is
Codafile.
This resets any root value that might have been previously set,
and clears the item list.
- ROOT [path]
-
Set the root directory for relative pathnames.
This can be used to override the root after a
read
command has been given.
The default path is
/.
- SEND filename
-
After a
list
command, this sends back an
ACK
message, the uninterpreted bytes in the file, and a second
ACK
message.
The client must remember (from the
list
command)
how big the file is so it knows how much data to expect.
Only items mentioned in the most recent
list
command can be sent.
- USER name pass
-
Log in with the given name and password; only the
help
and
mesg
commands can be used without logging in.
AUTHOR
This program was written by Rich $alz <rsalz@bbn.com>.
It has the following copyright:
-
Copyright 1989 BBN Systems and Technologies Corporation.
All Rights Reserved.
This is free software, and may be distributed under the terms of the
GNU Public License; see the file COPYING for more details.
$Header: codaserver.8,v 2.0 90/03/23 15:02:01 rsalz Exp $
SEE ALSO
coda(1).
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- PROTOCOL
-
- Message Types
-
- Server Commands
-
- AUTHOR
-
- SEE ALSO
-
This document was created by
man2html,
using the manual pages.
Time: 10:51:37 GMT, December 12, 2024