How can I take input parameters after the first one?
Hi,
Is there a simple way to take input of parameters after the first one? As following example, if I assign others=$2, it only takes the second one, if I assign others=$@, it will include the first one. I may try to assign others="$2 $3 $4 $5 $6 $7 $8 $9", it looks very ugly and could missing if the number of parameters is more than 9. Appreciate any helps.
....
Thank you.
Kind regards.
hce
Last edited by vbe; 06-17-2013 at 05:11 AM..
Reason: code tags please
Dear All,
I got a table creation file in a standard format. I need to accept parameters from the user & then based on the input change the data in the file. For. eg. i will accept the database name, dbspace name & user name from the user and accordingly change the same in the table creation... (2 Replies)
I have a script which take 3 input parameters
1st - a date (i.e. current date)
2nd - type (i.e. A)
3rd - limit (i.e. 40)
normally the date parameter would be current date, so I thought I could do this
calculate.sh $(date +%Y-%m-%d) A 40
however, it seems like it can't be done,... (3 Replies)
Hi i am a newbie who is trying to input parameters into this script, but not sure where to start.
The parameters that need to be input are the baseline label "abc.0111.BL " mantioned bellow, and database string "abc/abcp@db2 @counter.sql "
Environment: Windows XP
Running script: Cygwin 3.2
... (2 Replies)
anybody know a nice way to parse long input parameters such as --path /dir1/dir2/ (see below). Now I have more than 10 input parameters and it's confusing having parameters like -q something, I would prefer longer ones
case $OPTKEY in
--path) M_PATH=$OPTARG ;;
-s) ... (3 Replies)
Hi All,
I have tried to use ckdate (sun) command in script. It checks the input parameter which should be in 'YYYYMMDD format.
date=$( echo $1 | ckdate -f "%Y%m%d") | true
if ]
then
print " success"
else
print "no success"
fi
But in whatever format i pass the parameter,... (3 Replies)
I have to write a script to verify input parameters;
say esr should be YES or NO other wise the script should print an error.
This is what i tried in my script but I get the following error
:
esr="YES"
if ; then
print " Error should specify esr options YES/NO"
else
esr =$esr
fi
... (2 Replies)
Hi,
I am facing a weird problem with input parameters. Please find more details about my problem below:
a) I am executing a korn shellscript with 11 input parameters from "Appworx" tool (it's a scheduling tool) and immediately displaying those 11 parameter values in unixscript and noticed... (4 Replies)
Hi
I wrote a script which lists the content of a given directory.
I have just one problem. If you give 2 or more parameters, then it gives a strange error. After that error, it gives also an error from my script, but normally it shouldn't give that error.
Here's my script.You can test it.
... (3 Replies)
friends
and I can validate whether to run the shell has input parameters m event date, I occasionally happen something like this does not work
if $ 1 is null then
echo has entered input parameters
else
echo "parameter ok"
fi (2 Replies)
Discussion started by: tricampeon81
2 Replies
LEARN ABOUT SUSE
qmail-users
qmail-users(5) File Formats Manual qmail-users(5)NAME
qmail-users - assign mail addresses to users
OVERVIEW
The file /var/lib/qmail/users/assign assigns addresses to users. For example,
=joe.shmoe:joe:503:78:/home/joe:::
says that mail for joe.shmoe should be delivered to user joe, with uid 503 and gid 78, as specified by /home/joe/.qmail.
Assignments fed to qmail-newu will be used by qmail-lspawn to control qmail-local's deliveries. See qmail-newu(8). A change to
/var/lib/qmail/users/assign will have no effect until qmail-newu is run.
STRUCTURE
/var/lib/qmail/users/assign is a series of assignments, one per line. It ends with a line containing a single dot. Lines must not contain
NUL.
SIMPLE ASSIGNMENTS
A simple assignment is a line of the form
=local:user:uid:gid:homedir:dash:ext:
Here local is an address; user, uid, and gid are the account name, uid, and gid of the user in charge of local; and messages to local will
be controlled by homedir/.qmaildashext.
If there are several assignments for the same local address, qmail-lspawn will use the first one.
local is interpreted without regard to case.
WILDCARD ASSIGNMENTS
A wildcard assignment is a line of the form
+loc:user:uid:gid:homedir:dash:pre:
This assignment applies to any address beginning with loc, including loc itself. It means the same as
=locext:user:uid:gid:homedir:dash:preext:
for every string ext.
A more specific wildcard assignment overrides a less specific assignment, and a simple assignment overrides any wildcard assignment. For
example:
+:alias:7790:2108:/var/lib/qmail/alias:-::
+joe-:joe:507:100:/home/joe:-::
=joe:joe:507:100:/home/joe:::
The address joe is handled by the third line; the address joe-direct is handled by the second line; the address bill is handled by the
first line.
SEE ALSO qmail-pw2u(8), qmail-newu(8), qmail-lspawn(8)qmail-users(5)