3 .\" Copyright 1987,1988 by the Massachusetts Institute of Technology
4 .\" All rights reserved. The file /usr/include/zephyr/mit-copyright.h
5 .\" specifies the terms and conditions for redistribution.
8 .TH ZWRITE 1 "October 26, 1989" "MIT Project Athena"
9 .ds ]W MIT Project Athena
11 zwrite \- write to another user via Zephyr
54 sends a message from you to another user through the
56 notification service. The user must have subscribed to messages of
57 the appropriate class and instance using the
62 understands the following options.
67 to send the message authenticated, using
69 to perform the authentication. This is the default.
74 to send the message unauthenticated.
79 to print what type of message it is sending, and whether or not it was
85 to suppress information about whether or not the message was sent.
90 from expanding tabs in the message into appropriate spaces. Normally
92 will expand any tabs it finds into the appropriate number of spaces to
93 maintain separation based on 8-character tab stops.
98 to ignore `.' on a line by itself in the input and only end a typed
99 message when the user types the end-of-file character (usually
100 control-D). When the input is not a terminal, this is the default action.
103 Sends an urgent message. This changes the
105 instance of the message to ``URGENT''.
110 to ignore the Zephyr variables
115 when picking a default class, instance, and opcode.
120 from sending a PING message to verify the recipient is subscribing to
121 messages. By default,
123 will send a notice to the destination class, instance, and recipient,
124 with opcode ``PING'' before sending the message. If the PING is sent,
125 and the server response indicates there are no recipients subscribed to
128 exits without sending a message.
131 option is used, no PING is sent.
134 prepends a "CC:" line to the body of the message indicating the
135 recipients of the message. This is strictly a convenience: the
136 presence of a "CC:" line at the top of a zephyr body does not
137 necessarily indicate that this option was used, or that the message
138 really was sent to the listed users, and its lack doesn't indicate
139 that the message was not sent to multiple users.
141 .B \-s \fIsignature\fR
142 sets the signature to be included in the message. This overrides both
143 the user's name (as found in the password file) and any
144 setting of the Zephyr variable
145 .IR zwrite-signature .
148 be a single argument, hence when using a shell it should be quoted with
151 argument of "" leaves the signature in
155 Allows a user to specify a different class for the message. This allows
156 a message to be sent to a large group of people with some degree of
161 for a description of how to restrict access to classes. When this option
162 is specified, the message is sent to recipient "*" unless an additional
163 list of recipients is specified.
165 This argument may not be used in conjunction with the -f option.
167 .B \-i \fIinstance\fR
168 Allows a user to specify a different instance than the default.
169 When this option is used, the message is sent to recipient "*" unless an
170 additional list of recipients is specified. This allows a message to be
171 sent to a large group of people (e.g. a development group) just by having
172 the members subscribe to messages of class "MESSAGE", the specified instance,
175 This argument may not be used in conjunction with the -f option.
178 Allows a user to specify a different realm for the message, if the
179 server supports interrealm Zephyr.
182 Allows a user to specify a different default format for the message.
185 Allows a user to specify a different opcode for the message.
186 Some Zephyr notice display programs may use the opcode to decide how
190 Allows a user to specify an argument to be interpreted as a filesystem
191 specification. The class is set to
199 contains no colons (`:'), it is assumed to
200 be a host name, and it is converted into an official host name via
204 contains a colon, the portion preceding the colon is
205 treated as a host name, and the colon and any trailing characters are
206 appended to the offical host name returned by
208 If the name fails to resolve into an official host name, the instance is
213 This option may not be used in conjunction with the -c or -i option.
217 sends the remaining arguments on the command line as the message.
221 option is not specified, the user is prompted for the message to be
222 sent. The message may be terminated by typing ^D or ``.'' on a line
225 The default class for messages is ``MESSAGE'', the default instance
226 is ``PERSONAL'', andthe default opcode is ``'' (an empty string).
227 These defaults can be overridden by setting the Zephyr
234 Command-line options can override the defaults.
236 If the class is ``MESSAGE'' and the instance is either ``PERSONAL'' or
237 ``URGENT'', a recipient must be specified. These comparisons are
242 option is used, the contents of the Zephyr variable
244 are used to augment the user's username in the
249 option is not specified, the user's full name (as specified in the
250 password file) is used instead.
252 Tab expansion should really be done by the receiver of the message.
254 The \-u option is provided for compatibility with old versions of
256 and is not necessarily useful for sending messages to users who do not
257 have old subscription files.
259 kerberosintro(1), zctl(1), zephyr(1), zwgc(1), zhm(8), zephyrd(8),
262 Project Athena Technical Plan Section E.4.1, `Zephyr Notification
267 $ZEPHYR_VARS or $HOME/.zephyr.vars
271 Robert S. French (MIT-Project Athena)
273 Copyright (c) 1987,1988 by the Massachusetts Institute of Technology.
277 specifies the terms and conditions for redistribution.