Sponsored Content
Full Discussion: Send messages using finger
Top Forums UNIX for Dummies Questions & Answers Send messages using finger Post 302101846 by adhirgarg on Thursday 4th of January 2007 11:30:11 PM
Old 01-05-2007
You can use "talk" too

talk is another feature provided by UNIX.

look for "man talk" in UNIX prompt

Regards
Adhir
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

finger and newsgroups

Hi, I've been using unix at college for a few weeks now and I have come up against a few stumbling blocks: - Most unix commands seem to work w/ regexps - the computers I and my group are allowed to logon to are all itsunXX where XX is a number. if I can {finger @itsun88} to find out that I and... (1 Reply)
Discussion started by: the_man_who
1 Replies

2. UNIX for Dummies Questions & Answers

finger

is there a way to show information on all the users on your system? when i use 'finger' is only shows users names and info who are currently on the system. is there a way to show all accounts? thanx! (5 Replies)
Discussion started by: djatwork
5 Replies

3. Shell Programming and Scripting

help in finger command.

Hi, iam using sunsolaris. when you type finger command -- it dispalys information about local and remote users. but here it shows as can't stat /dev/gold:8664 can anybody help what is the solution for this error. previously the output came. thanks, shan (1 Reply)
Discussion started by: shanshine
1 Replies

4. UNIX for Dummies Questions & Answers

finger

Is there any possible way to get rid of the header when I do finger ? I want to get rid of Login Name Tty Idle Login Time Office Office Phone as the header. Please let me know how to do it. (2 Replies)
Discussion started by: felixwhoals
2 Replies

5. Solaris

Not send messages in my zone:

I have spark t1000 server in my corp, in global (ip 172.17.0.44) have zone(name www2) ip 172.17.0.15: In moment when i tried to send {code}#uuencode stats.zip stats.zip | mailx sotnav@domain.ru{code}a message whith sendmail on my www2 I have syslog: {code} What's problem please help? (2 Replies)
Discussion started by: sotich82
2 Replies

6. UNIX for Dummies Questions & Answers

Why can't I send messages to a remote domain

Hi there, I rent two servers hosted by the same provider: OVH. On server1, I use the mail command to send alert emails to my personal address and it works fine. On server2, which is newly instaled, I tried the following command and got this answer: Is there any other package that I need to... (2 Replies)
Discussion started by: chebarbudo
2 Replies

7. UNIX for Advanced & Expert Users

finger command

I want to know the correct version of how i should use the finger command in this example below.(os is debian lenny) (nymserver.pl is located in /home/nymserv directory.) the two versions are : (in/etc/inetd.conf) finger stream tcp nowait nymuser /usr/nym/nymserv nymserv... (3 Replies)
Discussion started by: xstation
3 Replies

8. Homework & Coursework Questions

program to send messages to parent using pipes and select system call

Write a program using select, which will create some number of child processes that continuously send text messages to the parent process using pipes. Each child has its own pipe that it uses to communicate with the parent. The parent uses select () to decide what pipes should be processed to... (1 Reply)
Discussion started by: ripssingh
1 Replies

9. Solaris

RWSocket::send: Broken pipe Error in /var/adm/messages

Hi Guys, I am getting some strange error in /var/adm/messages in my Solaris 10 box with Veritas Cluster and EMC storage. bash-3.00$ cat /var/adm/messages | egrep -v "lw8|snmp|sshd|xntpd|kern.info|LOGIN|link|service|started|finished|repeated|SS7 Log-daemon|success" Dec 18 09:58:35 GAMMa2... (1 Reply)
Discussion started by: vivek.goel.piet
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 10:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy