aboutsummaryrefslogtreecommitdiffstats
path: root/net/rmsg/pkg-descr
diff options
context:
space:
mode:
authorasami <asami@FreeBSD.org>1995-10-12 15:43:01 +0800
committerasami <asami@FreeBSD.org>1995-10-12 15:43:01 +0800
commite2d9d265d053b622a69be3acc0b2f8855c9dd4f5 (patch)
treec53a07f1ede138f7418be57f1ad189e84e92a583 /net/rmsg/pkg-descr
parent7711334d1b6206e4846a1f44596cd4b00acd22b1 (diff)
downloadfreebsd-ports-graphics-e2d9d265d053b622a69be3acc0b2f8855c9dd4f5.tar.gz
freebsd-ports-graphics-e2d9d265d053b622a69be3acc0b2f8855c9dd4f5.tar.zst
freebsd-ports-graphics-e2d9d265d053b622a69be3acc0b2f8855c9dd4f5.zip
This program allows you to send messages (like "write") to remote users.
Submitted by: torstenb
Diffstat (limited to 'net/rmsg/pkg-descr')
-rw-r--r--net/rmsg/pkg-descr49
1 files changed, 49 insertions, 0 deletions
diff --git a/net/rmsg/pkg-descr b/net/rmsg/pkg-descr
new file mode 100644
index 00000000000..0e3960d97c7
--- /dev/null
+++ b/net/rmsg/pkg-descr
@@ -0,0 +1,49 @@
+rmsg contains a messaging system which can be used to send
+write-like messages to logged-on users. The system can cross machine
+boundaries, so if another machine has the rmsgd program running, you can
+send messages to users on it.
+
+The system also allows bitnet virtual machine-like 'virtual users'
+to whom any user can send messages and they can answer the messages.
+The rmsgd server makes this possible by allowing a command 'exec' in a users
+.msgconf file, and whenever the user receives a message this command is
+executed and the message is piped to it.
+
+It is also possible to log incoming and outgoing messages and resend previous
+sent message. You can specify a file to which the last (or every) incoming
+message will be stored.
+
+Using the programs:
+-------------------
+
+Rmsgd:
+
+Rmsgd is the server program for the system. It should be started by root,
+but for now it works even if started by ordinary users, even though
+some capabilities are disabled for security reasons (that is, exec and
+logging of incoming messages, since that would be done by the user-id
+who started rmsgd and not the receiver).
+
+At any time, there should be only one rmsgd running. It doesn't do any harm
+to have several rmsgds other than the newly-started servers unmap the
+previous and thus the previous servers are unusable.
+
+The server should be named 'rmsgd' to have it start as a daemon.
+
+
+Rmsg:
+
+Rmsg is the client end of the system. Rmsg is used by ordinary users
+to send messages. For example, rmsg foo@bar hello there ! ^D would
+send a message 'hello there !' to user foo at machine bar. By
+default, rmsg stores the last outgoing message in the user's home
+directory in the file .msgout. Then msg -r user@machine can be used
+to resend the message. Message is normally read from standard input
+until EOF.
+
+Configuration:
+--------------
+
+The messages system has many options which the user can set by making
+a file '.msgconf' in her home directory and placing various command in it.
+Read the manual page for rmsg for more information.