Sponsored Content
Full Discussion: Whats Behind Your Name?
The Lounge What is on Your Mind? Whats Behind Your Name? Post 54084 by RTM on Monday 2nd of August 2004 08:27:16 AM
Old 08-02-2004
Used this one when my original account stopped working - and RTFM was already taken at that time.

A big Thanks to Neo for setting up and running this site.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Whats does this mean

Found this piece of code written in ksh. I have no ideas what do the stuff like ${SRF##*\.} do. SUFFIX=${SRF##*\.} if ; then SUFFIX="" fi I have encountered similar expressions in other programs also. Any pointers on where to learn more about these... (1 Reply)
Discussion started by: jyotipg
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Whats the go?

woofie, Your posts are being deleted because your use of profanity. I am close to changing your status to read only. In fact, if you argue with the mods again, I will ban you from these boards. Neo (1 Reply)
Discussion started by: Neo
1 Replies

3. Shell Programming and Scripting

whats the difference between $* and $@

Hi, whats the difference between $* and $@ in command line arguments to a shell scripts (3 Replies)
Discussion started by: pbsrinivas
3 Replies

4. Shell Programming and Scripting

tell me whats wrong in this?

#! /bin/bash head -5 $1 echo "remove $1 ?" read answer if then echo invalid answer elif rm $1 echo "$1 is deleted" elif then echo file is not deleted else echo "invalid answer" fi What i really want this to do is to ask to delete the file or not..it says something wrong... (1 Reply)
Discussion started by: nadman123
1 Replies

5. Shell Programming and Scripting

tell me whats wrong with this

#! /bin/bash USAGE=" | ] if then echo "$USAGE" exit 1 fi while getopts lb: OPTION do case $(OPTION)in a) echo Hi there! exit 2;; b) echo hello o) OARG=$OPTARG;; \?)echo "$USAGE" ;; exit 2;; esac done shift `expr... (1 Reply)
Discussion started by: nadman123
1 Replies

6. Shell Programming and Scripting

whats this NAME=${0##*/}

hi all, i found NAME=${0##*/} in a script. i given this coomand in my unix box(presently in ksh). echo ${0##*/} it returned ksh. the purpose of the above is to return the shell name or more than that. do you have any more information like this, please share with me. one more query... (7 Replies)
Discussion started by: Arunprasad
7 Replies

7. Shell Programming and Scripting

##*_ - whats this?

Hi all, could you please tell me whats this stands ##*_ 0##*/ i knew this alone if some more is there please tell me that also. (3 Replies)
Discussion started by: Arunprasad
3 Replies

8. UNIX for Dummies Questions & Answers

whats wrong with this?

can anyone tell me why this code doesn't work how its supposed to, its the hangman game but it doesn't play how its supposed to #!/bin/bash NoAttempts="0" livesgiven="5" LivesRemain=$livesgiven LettersAttempted="" wordfile=words numwords=0 function menu() { clear cat << menu... (1 Reply)
Discussion started by: ferrycorsten73
1 Replies

9. Homework & Coursework Questions

Whats wrong with the following

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: ls -ld htdocs drwxr-x--- 3 root root 8192 2006-11-19 10:41 htdocs How would a host administrator... (1 Reply)
Discussion started by: Larry_1
1 Replies
talk(1) 						      General Commands Manual							   talk(1)

Name
       talk, otalk - talk to another user

Syntax
       talk person [ttyname]

       otalk person [ttyname]

Description
       The command is a visual communication program which copies lines from your terminal to that of another user.

       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 :
       host!user
	or
       host.user
	or
       host:user
	or
       user@host
       The form user@host is perhaps preferred.

       If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.

       When first called, it 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 doesn't 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 Ctrl-L will cause the screen to be reprinted,
       while your erase, kill, and word kill characters will work in talk as normal.  To exit, just type your interrupt character; then moves  the
       cursor to the bottom of the screen and restores the terminal.

       Permission to talk may be denied or granted by use of the mesg command.	At the outset talking is allowed.  Certain commands, in particular
       and disallow messages in order to prevent messy output.

       In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session  with
       the  command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
       gram with the command. See the Restrictions section.

Examples
       The following example demonstrates how to use the command.  In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates  a
       session with user2, whose system (system2) is running ULTRIX V3.0.  User1 types the following:
       system1> talk user2@system2
       The following message appears on the screen of user2:
       Message from Talk_Daemon@system2 at 12:37 ...
       talk: connection requested by user1@system1.
       talk: respond with:  otalk user1@system1
       To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
       system2> otalk user1@system1

Restrictions
       The  version  of  released  with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
       ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3  BSD  or  versions	of
       UNIX based on 4.3 BSD.

       The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
       followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
       which has DECMCS characters in its alphabet.

Files
       to find the recipient's machine

       to find the recipient's tty

See Also
       mail(1), mesg(1), who(1), write(1), talkd(8c)

																	   talk(1)
All times are GMT -4. The time now is 04:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy