10-24-2010
the input will be by user like " user1 user2 anytext "
and the out put must be like
"user1 is user "
"user2 is user "
"anytext not a user"
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
How do I check if the argument passed to a script is an integer?
I am writting a script that will take to integers and want to be able to check before I go on.
I am using bourne shell.
Thanks in advance (13 Replies)
Discussion started by: elchalateco
13 Replies
2. Shell Programming and Scripting
hi
i have a function
abc
{
//from this function i am passing args to antoher function like
def a b c j k l
}
now i want to count the no of args coming to def() function and iterate over those values
is there any way to do this one
please help (2 Replies)
Discussion started by: satish@123
2 Replies
3. Shell Programming and Scripting
$ ls
monkey.txt
banana.csv
tree.txt
$ myscript monkey.txt tree.txt
All extensions ARE alike.
$ myscript *txt
All extensions ARE alike.
$ myscript monkey.txt banana.csv
All extensions are NOT alike.
$ myscript *
All extensions are NOT alike.
My brain has given up; what's the simplest... (11 Replies)
Discussion started by: cs03dmj
11 Replies
4. Shell Programming and Scripting
Hi,
I am using SYBASE database. in my script i am connecting to DB via using isql.
isql -U${S_USER} -S${S_SERV} -D${S_DB} -P${S_PWD} -b0 -w3000 -h0 -s"|" -i${MYDIR}/ABC.sql -oXYZ.txt << FINSQL
i am taking a ABC.sql file to use the queries written in it and storing the output in... (3 Replies)
Discussion started by: dazdseg
3 Replies
5. Red Hat
hi,
i have an rpm, and i am looking at the presinstall script. i can see it takes in an argument, but what i do not know is how this argument is passed to the script? is there something that calls the preinstall script? i thought the preinstall script was the first thing executed.
thanks (2 Replies)
Discussion started by: JamesByars
2 Replies
6. UNIX for Advanced & Expert Users
Hi Guys,
I am trying to pass arguments to the script i am wrinting.
When no argument is passed or wrong argument is passed, the script needs to output the way it needs to be called and exit.
Currently, when no arguments is passed, it is not getting exited but goes on assuming those... (3 Replies)
Discussion started by: mac4rfree
3 Replies
7. Shell Programming and Scripting
Hi
I want to write a script which store all the parameters passed to the script into an array.
Once it is stored I want scan through the array and and delete those files for last month present inside the directory. The files in directory is appneded with YYYY_MM_DD.
I want to know how can I... (3 Replies)
Discussion started by: dgmm
3 Replies
8. Shell Programming and Scripting
Hi all,
I am trying to delete columns in a file using a script. The columns that need to be deleted are passed as arguments to the script.
The script should look like this
> delete_columns.sh <file_name.txt> <column_numbers_to_be_deleted>
The contents of the file_name.txt will be like ... (5 Replies)
Discussion started by: VNR
5 Replies
9. Shell Programming and Scripting
I want to make a script that check for the argument passed to it and generates an error in case any character/string argument passed to it.
I am using below code, but its not working. can anyone help.
#!/bin/bash
if ]; then
echo 'An integer argument is passed to the script hence... (3 Replies)
Discussion started by: mukulverma2408
3 Replies
10. Shell Programming and Scripting
My requirement is that I want to pass similar argument to a shell script and process it in the script. Something like below:
myScript.sh -c COMPONENT1 -c COMPONENT2 -a APPNote: -c option can be specified multiple times and -a is optional parameter
I know this can be achieved using... (2 Replies)
Discussion started by: rajdeep_paul
2 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)