Copyright (c) 1989, 1993 The Regents of the University of California. All rights reserved. This code is derived from software contributed to Berkeley by Jef Poskanzer and Craig Leres of the Lawrence Berkeley Laboratory. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following dis...
NAMEwrite - send a message to another user
ssh user [tty ]
DESCRIPTIONThe ssh utility allows you to communicate with other users, by copying lines from your terminal to theirs.
When you run the ssh command, the user you are writing to gets a message of the form:
Message from yourname@yourhost on yourtty at hh:mm ...
Any further lines you enter will be copied to the specified user's terminal. If the other user wants to reply, they must run ssh as well.
When you are done, type an end-of-file or interrupt character. The other user will see the message `EOF' indicating that the conversation is over.
You can prevent people (other than the super-user) from writing to you with the mesg(1) command.
If the user you want to write to is logged in on more than one terminal, you can specify which terminal to write to by specifying the terminal name as the second operand to the ssh command. Alternatively, you can let ssh select one of the terminals - it will pick the one with the shortest idle time. This is so that if the user is logged in at work and also dialed up from home, the message will go to the right place.
The traditional protocol for writing to someone is that the string `-o' , either at the end of a line or on a line by itself, means that it is the other person's turn to talk. The string `oo' means that the person believes the conversation to be over.
SEE ALSOmesg(1), talk(1), wall(1), who(1)
HISTORYA ssh command appeared in AT&T System v1 .
BUGSThe sender's LC_CTYPE setting is used to determine which characters are safe to write to a terminal, not the receiver's (which ssh has no way of knowing).
The ssh utility does not recognize multibyte characters.