Sponsored Content
Full Discussion: Awk is killing me.
Top Forums Shell Programming and Scripting Awk is killing me. Post 302562916 by yazu on Sunday 9th of October 2011 12:36:40 AM
Old 10-09-2011
A sketch. If you don't have too many flavors:
Code:
cat INPUTFILE
0,21
0,22
3,29
0,23
2,17
1,41
0,24
3,30
3,31
3,32
2,18
2,19

awk -F, '{ print $2 > $1 }' INPUTFILE

# GNU sed  Change to literal tabs and -e ':a' -e '...' for an old one.
paste [0-9]* | sed  ':a s!\t\t!\t0\t!; ta'  
21	41	17	29
22	0	18	30
23	0	19	31
24	0	0	32

===

I don't see any easy way to do it with awk only. It would be easy but awkward with Perl. Python or Ruby or even Javascript are better.

Last edited by yazu; 10-09-2011 at 01:50 AM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Killing Connections

Say, for instance, that you are running a website. You are playing around, using netstat, etc. You notice all the people whom are connected to the site. You then wonder if there is a way to kill one or more of these connections. However, they are not PIDs so could you use the kill command? I was... (1 Reply)
Discussion started by: Phobos
1 Replies

2. SCO

users killing

:confused: When users logout from the server 'who -u' command shows existance of the user without any prcess ID and 'kill -9' command becomes invalid. Any body have any idea how to solve this problem. let me know please. (0 Replies)
Discussion started by: utpol_68
0 Replies

3. What is on Your Mind?

DNS killing me

Does anyone here know DNS backwords and forwards to include knowing how to set it up for internal and external users (private and public ip addresses)??? Any help would be great! (1 Reply)
Discussion started by: nbredthauer
1 Replies

4. UNIX for Dummies Questions & Answers

killing the process

Hi, First, I am running a scipt.While the script is running I realize that I dont want the script to be run so I am killing the script externally.Before the process gets terminated or killed it should delete all the temporary files created by the script.How to do this?Can anyone help me? ... (3 Replies)
Discussion started by: arthi
3 Replies

5. Shell Programming and Scripting

Help in killing the session !

Hello, I am new to unix scripts and have been experimenting with do-while structure. I have run into a problem. my script is, --- while true do ./redir --lport=55083 --caddr=14.121.119.21 --cport=55083 2>&1 >> /tmp/out.txt echo "Restarting `date`" done --- As you can see, i didnt handle... (3 Replies)
Discussion started by: script_newbie
3 Replies

6. Shell Programming and Scripting

Killing process!!!!

Hi friends, i m in big trouble.... i have one script which connects two server ...like below.. script1.sh ------------------------------------- bash test.sh & eval x=$@ export x=`echo $x` #echo $x # ssh user@8.2.5.6 bash /mbbv/location/script.sh $x|sed '/Binary file/d'... (1 Reply)
Discussion started by: Shahul
1 Replies

7. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

8. Shell Programming and Scripting

Killing a subshell

I am calling a script from with another script and reading its output one line at a time (using <childscript> | while read line) in the parent script. If the output exceeds a predefined number of lines I want to kill the child shell from within the parent shell. I decided to print the process ID... (2 Replies)
Discussion started by: slash_blog
2 Replies

9. Shell Programming and Scripting

Killing the process ID's

Hi , I have a list of application process id's. Is there a way to kill all the process listed below using the script, except the once which are starting with " Genesis " adm 1522 ABC_Process.tra adm 1939 Genesis_Process.tra adm 2729 Genesis_Archive.tra adm 3259 xyz_Process.tra (5 Replies)
Discussion started by: murali1687
5 Replies
RUBY(1) 						 Ruby Programmers Reference Manual						   RUBY(1)

NAME
ruby - Interpreted object-oriented scripting language SYNOPSIS
ruby [ --version ] [ -c ] [ -w ] [ -d ] [ -l ] [ -p ] [ -n ] [ -a ] [ -s ] [ -0[octal] ] [ -Kc ] [ -ecommand ] [ -Fpattern ] [ -i[extension] ] [ -Idir ] [ -rlibrary ] [ -S ] [ -v ] [ -x[directory] ] [ -Cdirectory ] [ -y] [ -- ] [ programfile ] [ argument ] ... PREFACE
Ruby is an interpreted scripting language for quick and easy object-oriented programming. It has many features to process text files and to do system management tasks (as in Perl). It is simple, straight-forward, and extensible. If you want a language for easy object-oriented programming, or you don't like the Perl ugliness, or you do like the concept of lisp, but don't like too much parentheses, Ruby may be the language of your choice. DESCRIPTION
Ruby's features are as follows: o Interpretive Ruby is an interpreted language, so you don't have to recompile programs written in Ruby to execute them. o Variables have no type (dynamic typing) Variables in Ruby can contain data of any type. You don't have to worry about variable typing. Consequently, it has a weaker com- pile time check. o No declaration needed You can use variables in your Ruby programs without any declarations. Variable names denote their scope, local, global, instance, etc. o Simple syntax Ruby has a simple syntax influenced slightly from Eiffel. o No user-level memory management Ruby has automatic memory management. Objects no longer referenced from anywhere are automatically collected by the garbage collec- tor built into the interpreter. o Everything is an object Ruby is the purely object-oriented language, and was so since its creation. Even such basic data as integers are seen as objects. o Class, inheritance, methods Of course, as an object-oriented language, Ruby has such basic features like classes, inheritance, and methods. o Singleton methods Ruby has the ability to define methods for certain objects. For example, you can define a press-button action for certain widget by defining a singleton method for the button. Or, you can make up your own prototype based object system using singleton methods, if you want to. o Mix-in by modules Ruby intentionally does not have the multiple inheritance as it is a source of confusion. Instead, Ruby has the ability to share implementations across the inheritance tree. This is often called `Mix-in'. o Iterators Ruby has iterators for loop abstraction. o Closures In Ruby, you can objectify the procedure. o Text processing and regular expression Ruby has a bunch of text processing features like in Perl. o Bignums With built-in bignums, you can for example calculate factorial(400). o Exception handling As in Java(tm). o Direct access to the OS Ruby can use most UNIX system calls, often used in system programming. o Dynamic loading On most UNIX systems, you can load object files into the Ruby interpreter on-the-fly. COMMAND LINE OPTIONS
Ruby interpreter accepts following command-line options (switches). They are quite similar to those of Perl. -0[octal] specifies the input record separator ($/) as an octal number. If no digit is given, the null character is taken as the separator. Other switches may follow the digits. -00 turns Ruby into paragraph mode. - 0777 makes Ruby read whole file at once as a single string since there is no legal character with that value. -a turns on auto-split mode when used with -n or -p. In auto-split mode, Ruby executes $F = $_.split at beginning of each loop. -c causes Ruby to check the syntax of the script and exit without executing. If there are no syntax errors, Ruby will print "Syntax OK" to the standard output. --copyright prints the copyright notice. -d --debug turns on debug mode. $DEBUG will set true. -e command specifies script from command-line while telling Ruby to not search argv for script filenames. -F pattern specifies input field separator ($;). -h --help prints a summary of the options. -i extension specifies in-place-edit mode. The extension, if specified, is added to old filename to make a backup copy. example: % echo matz > /tmp/junk % cat /tmp/junk matz % ruby -p -i.bak -e '$_.upcase!' /tmp/junk % cat /tmp/junk MATZ % cat /tmp/junk.bak matz -I directory used to tell Ruby where to load the library scripts. Directory path will be added to the load-path variable ($:'). -Kkcode specifies KANJI (Japanese) encoding. -l enables automatic line-ending processing, which means to firstly set $ to the value of $/, and secondly chops every line read using chop!. -n causes Ruby to assume the following loop around your script, which makes it iterate over filename arguments somewhat like sed -n or awk. while gets ... end -p acts mostly same as -n switch, but print the value of variable $_ at the each end of the loop. example: % echo matz | ruby -p -e '$_.tr! "a-z", "A-Z"' MATZ -r library causes Ruby to load the library using require. It is useful with switches -n or -p. -s enables some switch parsing for switches after script name but before any filename arguments (or before a --). Any switches found there are removed from ARGV and set the corresponding variable in the script. example: #! /usr/local/bin/ruby -s # prints "true" if invoked with `-xyz' switch. print "true " if $xyz -S makes Ruby use the PATH environment variable to search for script, unless if its name begins with a slash. This is used to emulate #! on machines that don't support it, in the following manner: #! /usr/local/bin/ruby # This line makes the next one a comment in ruby exec /usr/local/bin/ruby -S $0 $* On some systems $0 does not always contain the full pathname, so you need -S switch to tell Ruby to search for the script if neces- sary. To handle embedded spaces or such. A better construct than $* would be ${1+"$@"}, but it does not work if the script is being interpreted by csh. -v --verbose enables verbose mode. Ruby will print its version at the beginning, and set the variable `$VERBOSE' to true. Some methods print extra messages if this variable is true. If this switch is given, and no other switches are present, Ruby quits after printing its version. -T[level] turns on taint checks at the specified level (default 1). --version prints the version of Ruby interpreter. -w enables verbose mode without printing version message at the beginning. It set the `$VERBOSE' variable to true. -x[directory] tells Ruby that the script is embedded in a message. Leading garbage will be discarded until the first that starts with "#!" and contains the string, "ruby". Any meaningful switches on that line will applied. The end of script must be specified with either EOF, ^D (control-D), ^Z (control-Z), or reserved word __END__.If the directory name is specified, Ruby will switch to that directory before executing script. -C directory causes Ruby to switch to the directory. -y --yydebug turns on compiler debug mode. Ruby will print a bunch of internal state messages during compiling scripts. You don't have to specify this switch, unless you are going to debug the Ruby interpreter. AUTHOR
Ruby is designed and implemented by Yukihiro Matsumoto <matz@netlab.jp>. 2001-12-25 ruby 1.6 RUBY(1)
All times are GMT -4. The time now is 12:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy