awk command not working as expected Post: 302970399

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

awk not working as expected with BIG files ...

I am facing some strange problem. I know, there is only one record in a file 'test.txt' which starts with 'X' I ensure that with following command, awk /^X/ test.txt | wc -l This gives me output = '1'. Now I take out this record out of the file, as follows : awk /^X/ test.txt >...

2. Shell Programming and Scripting

Var substitution in awk - not working as expected

countA=`awk '/X/''{print substr($0,38,1)}' fName | wc -l` countB=`wc -l fName | awk '{print int($1)}'` echo > temp ratio=`awk -va=$countA -vc=$countB '{printf "%.4f", a/c}' temp` After running script for above I am getting an error as : awk: 0602-533 Cannot find or open file -vc=25. The...

3. UNIX for Dummies Questions & Answers

Find command not working as expected

I have a script with a find command using xargs to copy the files found to another directory. The find command is finding the appropriate file, but it's not copying. I've checked permissions, and those are all O.K., so I'm not sure what I'm missing. Any help is greatly appreciated. This is...

4. OS X (Apple)

Cat command not working as expected

I've been trying to figure this out since last night, and I'm just stumped. The last time I did any shell scripting was 8 years ago on a Unix box, and it was never my strong suit. I'm on a Mac running Leopard now. Here's my dilemma - hopefully someone can point me in the right direction. I'm...

5. Shell Programming and Scripting

bash variable (set via awk+sed) not working as expected

Hi! Been working on a script and I've been having a problem. I've finally narrowed it down to this variable I'm setting: servername=$(awk -v FS=\/ '{ print $7 } blah.txt | sed 's\/./-/g' | awk -v FS=\- '{print $1}')" This will essentially pare down a line like this: ...

6. Shell Programming and Scripting

Read command not working as expected

I was trying to write a simple script which will read a text file and count the number of vowels in the file. My code is given below - #!/bin/bash file=$1 v=0 if then echo "$0 filename" exit 1 fi if then echo "$file not a file" exit 2 fi while read -n...

7. Shell Programming and Scripting

awk not working as expected in script

Dear all, I had script which used to work, but recently it is not working as expected. I have command line in my shell script to choose the following format from the output_elog and perform some task afterwards on As you see, I want all numbers in foramt following RED mark except for...

8. Shell Programming and Scripting

Cp command not working as expected in HPUX

Hi, I'm having trouble with a simple copy command in a script on HPUX. I am trying to copy a file and append date & time. The echo command prints out what I am expecting.. echo "Backing up $file to $file.$DATE.$FIXNUM" | tee -a $LOGFILE + echo 'Backing up...

9. Shell Programming and Scripting

awk gsub not working as expected

Hi Experts, Need your kind help with gsub awk. Below is my pattern:"exec=1_host_cnt=100_dup=4_NameTag=targetSrv_500.csv","'20171122112948"," 100"," 1"," 1"," 4","400","","", " aac sample exec ""hostname=XXXXX commandline='timeout 10 openssl speed -multi 2 ; exit 0'"" ","-1","-1","1","...

10. Shell Programming and Scripting

awk matching script not working as expected

This is my ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial $ /bin/awk -V | head -n1 bash: /bin/awk: No such file or directory I have gotten a script that helps me to parse,...

LEARN ABOUT OSF1

badsect

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

NAME

       badsect - Creates files to contain bad sectors

SYNOPSIS

       /usr/sbin/badsect bbdir sector...

DESCRIPTION

       The  badsect  command  makes  a file to contain a bad sector.  Normally, bad sectors are made inaccessible by the standard formatter, which
       provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is  preferable  to  use  that
       method  to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1).
       The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of
       file systems or in swap areas.

       On  some  disks,  adding  a  sector  that is suddenly bad to the bad sector table currently requires the running of the standard formatter.
       Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be  used  to  good
       effect.

       Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory.  Make a direc-
       tory BAD there.	Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add.   (The  sector  numbers
       must  be  relative to the beginning of the file system, as reported in console error messages.)	Change back to the root directory, unmount
       the file system, and run fsck(8) on the file system.  The bad sectors should show up in two files or in the bad sector files and  the  free
       list.   Have  fsck  remove  files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files.  This operation will
       leave the bad sectors in only the BAD files.

       The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an	illegal  file  whose  first  block
       address	is  the  block containing bad sector and whose name is the bad sector number.  When fsck discovers the file, it will ask "HOLD BAD
       BLOCK?"	An affirmative response will cause fsck to convert the inode to a regular file containing the bad block.

RESTRICTIONS

       If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks  in  the
       bad sector files cover all the sectors in a file system fragment.

ERRORS

       The  badsect  command refuses to attach a block that resides in a critical area or is out of range of the file system.  A warning is issued
       if the block is already in use.

SEE ALSO

       Commands: fsck(8)

																	badsect(8)