This awk should work, shouldn't it? Post: 302956224

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

why is this so hard when it shouldn't be?

All I ask is one thing: 1. Where can i dl unix and the driver for my modem? right now i have win xp HP notebook, and bellsouth is my provider with a westell modem.

2. Shell Programming and Scripting

why awk does not work here?

I am trying to find any line with the 9th column's number greater than 200, but why the following awk command does not work? awk '$9 > 200' /tmp/test 2007-09-05 10:13:05.714 640.847 any 1.2.3.4 719 2445 487260 32 6082 199 2007-09-05 10:13:02.686 641.827...

3. Shell Programming and Scripting

awk: assign variable with -v didn't work in awk filter

I want to filter 2nd column = 2 using awk $ cat t 1 2 2 4 $ VAR=2 #variable worked in print $ cat t | awk -v ID=$VAR ' { print ID}' 2 2 # but variable didn't work in awk filter $ cat t | awk -v ID=$VAR '$2~/ID/ { print $0}'

4. Shell Programming and Scripting

Parse file using awk and work in awk output

hi guys, i want to parse a file using public function, the file contain raw data in the below format i want to get the output like this to load it to Oracle DB MARWA1,BSS:26,1,3,0,0,0,0,0.00,22,22,22.00 MARWA2,BSS:26,1,3,0,0,0,0,0.00,22,22,22.00 this the file raw format: Number of...

5. Shell Programming and Scripting

Delimited data contains line feeds where they shouldn't be

6. Solaris

Particular user account shouldn't be locked after entering wrong passwd specfic no. times

Hi all In my system we have implemented user lockout feature after 3 failure attempt if he tries to login directly or if he run the any command through sudo and enter wrong password thrice. Now I have requirement in which particular user account shouldn't be locked when he run the command...

7. Shell Programming and Scripting

Script outputing out numbers when it shouldn't

i suspect the issue is with the IFS part. I have a script that reads a file. the problem here is that, when i run the script, it outputs a bunch of numbers. i know what these numbers are, but i dont understand why they're being sent to the screen. as you can see below, everything should be...

8. UNIX for Dummies Questions & Answers

Users of own group shouldn't be able to delete

Oracle Linux 6.5 oracle user's primary group is oinstall and its secondary group is dba,asmdba,asmoper. For the below created directory, I want the users belonging to dba,asmdba,asmoper to be able create, read and execute files but not delete them. How can I achieve that. If I use 775 as...

9. Shell Programming and Scripting

Why does this if match although it shouldn't?

Hi everyboy, I am a little confused and can't understand why I get a positive match in the following case. Shell Script section echo $SHELL echo "Server type = ${SERV_TYPE}" if ]]; then echo "foor" echo -e $(_date) "${cinfo}INFO: ${crst}Checking SAP memory on ${HOST}"This is the...

LEARN ABOUT OSF1

killall

killall(8)						      System Manager's Manual							killall(8)

NAME

       killall - Terminates all processes started by the user, except the calling process

SYNOPSIS

       /usr/sbin/killall [- | [-]signal_name | -signal_number]

       /usr/sbin/killall -l

FLAGS

       The  hyphen  character (without an argument) sends a SIGTERM signal initially and then sends a SIGKILL signal to all processes that survive
       for 30 seconds after receipt of the first signal.  This gives processes that catch the SIGTERM signal an opportunity to clean up.  A signal
       name, optionally preceded by a hyphen, sends the specified signal to processes.	The hyphen character (with a signal number argument) sends
       the specified signal, either a name, stripped of the SIG prefix (such as KILL), or a number (such as  9).   For	information  about  signal
       names and numbers, see the signal() system call.

       In  the System V habitat, the optional signal number does not have to be preceded with a hyphen (-).  Lists signal names in numerical order
       (as given in the /usr/include/signal.h file), stripped of the common SIG prefix.

DESCRIPTION

       This command provides a convenient means of killing all processes created by the shell that you control.  When started  by  the	superuser,
       the killall command kills all processes that can be terminated, except those processes that started it, the kernel processes, and processes
       0 and 1 (init).

   Security Configuration
       This command is modified in all security configurations of the system.

EXAMPLES

       To stop all background processes that have started, enter: killall This sends all background processes signal  9  (the  kill  signal,  also
       called  SIGKILL).   To  stop  all  background processes, giving them a chance to clean up, enter: killall - This sends signal 15 (SIGTERM),
       waits 30 seconds, and then sends signal 9 (SIGKILL).  To send a specific signal to the background processes, enter: killall -2  This  sends
       signal  2 (SIGINT) to the background processes.	To list the signal names in numerical order, stripped of the SIG prefix, enter: killall -l
       This displays a list of signals, which may vary from system to system.

FILES

       Specifies the command path

RELATED INFORMATION

       Calls: kill(2), sigaction(2), signal(2) delim off

																	killall(8)