$ bash a.sh -9 1 3 4 5
All arguments: -9 1 3 4 5
name of script is a.sh
first argument is -9
second argument is 1
seventeenth argument is -97
number of arguments is 5
Code:
$ cat a.sh
echo "All arguments: $@"
echo name of script is $0
echo first argument is $1
echo second argument is $2
echo seventeenth argument is $17
echo number of arguments is $#
Say I write something like the following:
var1=1
var2=2
for int in 1 2
do
echo "\$var$int"
done
I want the output to be:
1
2
Instead I get something like:
$var1
$var2 (2 Replies)
I have written a function that fills an array and another function where if a parameter is supplied it will jump to that part of the array and cat it to the screen.
I need to put in some checks to make sure the parameter supplied is firstly a number and then not a number great than the length of... (2 Replies)
Hey I'm new in linux,
I'm looking for a code to check whether the parameter is a number or a string.
I have already tried this code:
eerste=$(echo $1 | grep "^*$">aux)
if
But it doesn't work.:confused:
Thanks (2 Replies)
I have a task. The scenario is like this. I have a operation program (OPR1) , whose function is to simply double the (single)value it receives as input.
I have to write a script to operate the OPR1 and save its output in a file.
Later, I have to modify the script so as to be able to operate ... (0 Replies)
Hi,
Is there a maximum number of processes kernel parameter in AIX.
Solaris has max_nprocs,
HP-UX has nproc,
I can only find max user process (maxuproc) for AIX.
Thanks,
Wilson. (3 Replies)
I have the below script running for generating file from PL/SQL stored procedure. I need to declare a shell variable and then pass this to sqlplus command to pass the same as a INPUT parameter for the stored procedure. Please help to do this.
#!/bin/sh
minlimit=0
maxlimit=10
size=100
while... (0 Replies)
Conversion of string into currency value..
ex1:
number_of_positions=2
input_string=345987
Output= 345,987.00
ex2:
number_of_positions=4
input_string=1345987
Output= 1,345,987.0000
Please respond as soon as possible
edit by bakunin: we will gladly respond as soon as... (15 Replies)
Hi there,
I am having a problem on an AIX server running a WebSphere MQ instance. The problem is that sometimes it seems to reach process limit, but I do not find the processes themselves.
What I see: succeed to log in (as root from console os as nonpriviliged user via ssh). Trying to run... (19 Replies)
Discussion started by: trifo75
19 Replies
LEARN ABOUT NETBSD
kill
KILL(1) BSD General Commands Manual KILL(1)NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the process(es) specified by the pid operand(s).
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
Display the name of the signal corresponding to exit_status. exit_status may be the exit status of a command killed by a signal (see
the special sh(1) parameter '?') or a signal number.
If no operand is given, display the names of all the signals.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following pids have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
0 Broadcast the signal to all processes in the current process group belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill argu-
ments. See csh(1) for details.
SEE ALSO csh(1), pgrep(1), pkill(1), ps(1), kill(2), sigaction(2), signal(7)STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 6 AT&T UNIX.
BSD April 28, 1995 BSD