5 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
I've been having a problem connecting to the forum. I know it is just something with my computer but I have no idea what it is. It started last week.
Every time I connect I get this:
<?xml version="1.0" encoding="ISO-8859-1" ?>
- <rss version="2.0"... (2 Replies)
Discussion started by: Vi-Curious
2 Replies
2. Forum Support Area for Unregistered Users & Account Problems
Folks,
Hope this is not a newbie question, but it might end up being that.
I wanted to retrieve the source code for unix_linux_bench as directed on https://www.unix.com/linux-benchmarks/11175-instructions-linux-benchmarks.html
When one clicks on the links specified for download, the browser... (1 Reply)
Discussion started by: wagdalule
1 Replies
3. Answers to Frequently Asked Questions
Every now and then our users post complete programs to this site. It is especially important that these contributions don't get lost, so I will collect them here. Some of these programs are intended to demonstrate a programming technique and some are ready to run. As a guideline, the code... (0 Replies)
Discussion started by: Perderabo
0 Replies
4. Post Here to Contact Site Administrators and Moderators
Of late, when i start www.unix.com my system is
going to 100% CPU and takes lot of time to get
the information. I think this is happening after
adding the graphics on the page. Has anyone seen
this problem..Sorry to post this here.. (6 Replies)
Discussion started by: sssow
6 Replies
5. Post Here to Contact Site Administrators and Moderators
PUZZLED:
How can I search for posts on 'VI' if by the new rules (or maybe they are old) I get the messge:
"The search term you specified (vi) is under the minimum word length (3) and therefore will not be found. Please make this term longer.
If this term contains a wildcard, please make... (13 Replies)
Discussion started by: sierra_aar
13 Replies
XTELL(1) General Commands Manual XTELL(1)
NAME
xtell - sends a message to another computer running xtelld
SYNOPSIS
xtell [-v] [user[:tty][@host[:port]]] [message]
write user [tty]
DESCRIPTION
How to use it: suppose you want to send a message to user gubas on computer trener.fsport.uniba.sk Just type:
prompt:~% xtell gubas@trener.fsport.uniba.sk Hi
To send multiple lines long message to user 7tokarova at computer pascal.fmph.uniba.sk, type
prompt:~% xtell 7tokarova@pascal.fmph.uniba.sk
Hi
How are you today
Please answer
^D
in this case, finish sending messages with EOF (CTRL D)
If you want to send message to user holik on local computer, you can do it either by typing:
prompt:~% xtell holik@localhost Hi
or simply:
prompt:~% xtell holik Hi
To send message to certain tty, append the tty to username, separated by colon:
prompt:~% xtell stanys:ttyp2@reaktor.ip.fmph.uniba.sk 'Sveikas Tomai'
will send message 'Sveikas Tomai' to user stanys on ttyp2 at computer reaktor.ip.fmph.uniba.sk
To specify other port than the default 4224, append the port to computer name, separated by colon:
prompt:~% xtell bosa@radon.dnp.fmph.uniba.sk:4000 'Ahoj'
assumes the xtell daemon runs at computer radon on port 4000, and sends the message 'Ahoj' to user bosa.
Option -v turns verbose mode on. Xtell will then display some messgaes about connecting, which is usefull especially when the connection is
slow.
Example:
prompt:~% xtell -v rybar@dmpc.dbp.fmph.uniba.sk
xtell invoked without parameters will ask user for username and host to send the message to.
If the user has created in his/her/its home directory the file .xtell-log, and the file is writable by nobody, all messages will be written
to this file as well as to the screen (handy when the screen is overwritten and you could not see the message).
xtell checks the environmental variable XTELLPROMPT. If it exists, it is used as prompt for messages.
Last notice: if you do not think zsh is the best shell, (besides doing a mistake) replace prompt:~% in above text with prompt:~$ or what-
ever :-)
AUTHOR
Radovan Garabik (garabik@melkor.dnp.fmph.uniba.sk)
SEE ALSO
xtelld(8), write(1), talk(1), talkd(8), tty(1)
BUGS
What happens to .xtell-log when two messages arrive simultaneously? There is no locking implemented.
XTELL(1)