Sponsored Content
Top Forums UNIX for Dummies Questions & Answers sending messages through terminal Post 12163 by PxT on Thursday 20th of December 2001 01:02:52 PM
Old 12-20-2001
You might try 'write', 'talk', or 'mail' depending on your needs and the type of message.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sending Finder Messages/Alerts in UNIX

I recall a UNIX command and remember actually using it where you could send finder alerts/messages to the Finder on the machine you were on or use ssh so as to send the alerts/messages to another machine on the network. You could also send Finder Alerts/Messages that had a reply field in the sense... (0 Replies)
Discussion started by: Peaves
0 Replies

2. Programming

Sending INtr key for remote terminal

Hi folks, Just wondering if anyone knows how to send intr/break key to remote tty (shell), a simple example would be great! thx (2 Replies)
Discussion started by: andryk
2 Replies

3. UNIX for Advanced & Expert Users

sending a null character to a terminal

I'm testing out some ESMTP AUTH stuff, and it requires that the username and password be on the same line separated by a null character. Does anyone know how to echo the ASCII null character? Thanks, Alex (3 Replies)
Discussion started by: vertigo23
3 Replies

4. Shell Programming and Scripting

sending message to terminal

hi all i have script #!/bin/bash cd /usr3/prod grep ERROR /usr3/prod/ind.log > /usr3/prod/ind_err.log if test -s /usr3/prod/ind_err.log then echo "error during process" else echo "process succeed" fi i want that this message(echo) will be display one time at the top of the screen... (5 Replies)
Discussion started by: naamas03
5 Replies

5. UNIX for Advanced & Expert Users

Sending messages to Phone

Hi experts, I am using Linux 2.6.9. My requirement is I want to send a message to the phone once my scheduled backup is complete. I don't know whether it's possible or not but I heard it can be done but don't know how. Can comebody help me on this? Thanks in advance. Gary (1 Reply)
Discussion started by: abcabc1103
1 Replies

6. Solaris

Sending Messages to Users

How can I send messages to users who are logged in unto the server with Solaris 9 OS without going into the application? (3 Replies)
Discussion started by: rahmantanko
3 Replies

7. Homework & Coursework Questions

Sending encrypted messages (ssh or scp)

1. we are a group a students and we need a help for sending encrypted messages with unix (ssh or scp) 2. we tried to use ssh and scp protocol but we didn't manage to send the message because we don't know the correct syntax of the command and we are asked a password and we don't know which is... (1 Reply)
Discussion started by: supervavul
1 Replies

8. UNIX for Dummies Questions & Answers

Sending command from one terminal to another.

Hello, I am running a program in a terminal. this program is just printing random words. I can change the color of each word by entering the first character of the color(for example G for Green). I want to write a bash code that runs in a different terminal and sends different characters to... (3 Replies)
Discussion started by: alireza6485
3 Replies

9. UNIX for Dummies Questions & Answers

Sending Mail in OS X Terminal

Hi All! I would like your assistance with an issue that I have been having with OS X (Snow Leopard 10.6.8) and sending mail through the Terminal. I had been trying to send mail from Terminal to my GMail account from my home, where I have a Verizon DSL Internet connection routed through a... (0 Replies)
Discussion started by: danielsutton
0 Replies

10. HP-UX

Debug3 messages throw in my terminal

OS: HP-UX B.11.31 U ia64 shell : /sbin/sh Messages like "debug3: Wrote 48 bytes for a total of 15837" are thrown in my terminal after each key stroke. If I try to type a command such message appears after each character I type. If I simply press enter messages like below appear. ... (1 Reply)
Discussion started by: black_fender
1 Replies
TALK(1) 						    BSD General Commands Manual 						   TALK(1)

NAME
talk -- talk to another user SYNOPSIS
talk person [ttyname] DESCRIPTION
The talk utility is a visual communication program which copies lines from your terminal to that of another user. Options available: person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another host, then person is of the form 'user@host' or 'host!user' or 'host:user'. ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name, where ttyname is of the form 'ttyXX'. When first called, talk sends the message Message from TalkDaemon@his_machine... talk: connection requested by your_name@your_machine. talk: respond with: talk your_name@your_machine to the user you wish to talk to. At this point, the recipient of the message should reply by typing talk your_name@your_machine It does not matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the two parties may type simultaneously, with their output appearing in separate windows. Typing control-L '^L' will cause the screen to be reprinted. Typing control-D '^D' will clear both parts of your screen to be cleared, while the control-D character will be sent to the remote side (and just displayed by this talk client). Your erase, kill, and word kill characters will behave normally. To exit, just type your interrupt character; talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state. Permission to talk may be denied or granted by use of the mesg(1) command. At the outset talking is allowed. CONFIGURATION
The talk utility relies on the talkd system daemon. See talkd(8) for information about enabling talkd. FILES
/etc/hosts to find the recipient's machine /var/run/utmpx to find the recipient's tty SEE ALSO
mail(1), mesg(1), wall(1), who(1), write(1), talkd(8) HISTORY
The talk command appeared in 4.2BSD. In FreeBSD 5.3, the default behaviour of talk was changed to treat local-to-local talk requests as originating and terminating at localhost. Before this change, it was required that the hostname (as per gethostname(3)) resolved to a valid IPv4 address (via gethostbyname(3)), making talk unsuitable for use in configurations where talkd(8) was bound to the loopback interface (normally for security reasons). BUGS
The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD. Multibyte characters are not recognized. BSD
August 21, 2008 BSD
All times are GMT -4. The time now is 05:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy