icon Top 9 categories map      RocketAware >

write(1)

Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.


The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Home

Search all pages


Subjects

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

    

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD RedHat Solaris Others



WRITE(1)                   OpenBSD Reference Manual                   WRITE(1)

NAME
     write - send a message to another user



SYNOPSIS
     write user [ttyname]

DESCRIPTION
     write allows you to communicate with other users, by copying lines from
     your terminal to theirs.

     When you run the write command, the user you are writing to gets a mes-
     sage 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 termi-
     nal.  If the other user wants to reply, they must run write 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.  Some commands, for example nroff(1) and pr(1),
      disallow writing automatically, so that your output isn't overwritten.

     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 write command.  Alternatively, you can
     let write 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's the
     other person's turn to talk.  The string `oo' means that the person be-
     lieves the conversation to be over.

SEE ALSO
     mesg(1),  talk(1),  who(1)

BUGS
     The `EOF' message seen when the other write terminates is indistinguish-
     able from that party simply typing `EOF' to make you believe that any fu-
     ture messages did not come from them.  Especially messages such as:
           [1]    Done                   rm -rf *

HISTORY
     A write command appeared in Version 6 AT&T UNIX.

OpenBSD 2.6                      June 6, 1993                                1

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.



(Corrections, notes, and links courtesy of RocketAware.com)


[Detailed Topics]
FreeBSD Sources for write(1)
OpenBSD sources for write(1)


[Overview Topics]

Up to: Immediate Unidirectional Message Delivery - Methods of one-way transfer of (short) messages for immediate reception. Paging, ICQ, SMS, et al


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD RedHat Solaris Others






Rapid-Links: Search | About | Comments | Submit Path: RocketAware > write.1/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments