Hi,

I have a .txt file with the output of a ps command as mentioned below

Apr 20 12:48:57 7590 16368 1726900 0.4 0.4
Apr 20 12:48:57 7590 16368 1726900 0.4 0.4
Apr 20 12:48:57 7590 16368 1726900 0.4 0.4
Apr 20 12:48:57 7590 16368 1726900 0.4 0.4

I have such ouptput for every 2 sec.My file will have such instances in a huge number.

I want to convert this .txt file to a csv file which i can analyze easily.

Can you please let me kknow if there is a shell script or tcl or perl script with which i can do this.

just pipe it through awk.... pretty simple stuff...

or if you want to date parts tokenized it's even easier...

Hi,

Thanks for the reply.

I have a text file which has thousands of lines. How can i get a .csv file diectly ? How i need to use the command.

Do i need o write a seperate script giving this as an input file ?

The above uses name.of.text.file as input (your file with thousands of lines) and puts (redirects) the output to a file called new.file.name.csv.

Do _not_ use the same name for both input and output file!

Hi Kamesp

with the pipe character "|" you can take the output given by what is on the left of the pipe

and do whatever you want with this output (with what is on the right of the pipe)

so instead of the echo ... put cat

# cat my_file | awk '{print $1" "$2" "$3","$4","$5","$6","$7","$8}'

= I display every line of my file and for each line I do an awk

and then don't forget to redirect in another file with >

tell me if it worked

woooops I didn't see druuna's reply

more simple indeed ( sorry I ain't a unix guru....yet)

Hi,

Thanks for the reply and it is working fine.

I have a question. In the awk command you are using awk '{print $1" "$2" "$3","$4","$5","$6","$7","$8}' where there is no " before $1 and similarly after $8. As i know awk prints the columns specififed.Can you tell me the logic here.

Hi,

One more issue is that when i copy the .csv file to my windows PC and open the same i am getting the details as below

4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1
4/19/2013 19:12 9135 12632 422804 0.3 0.1

Where i am getting the timestamp somany times eventhough it was printed only once when i see in my linux machine.

PS : Just to give a brief.I am running ps command with arguments in a loop with a gap of 2 sec

the " encloses the blank or the comma not the $n

but I don't know why there isn't any coma between $1 and $2 and $3

You have a line every two seconds. Your Excel format shows the day, hour and minute, but not second. So you should expect the same time stamp to appear on 30 lines before going to the next time stamp.

Is that what you mean by "so many times"? What do you mean by "printed only once"?

I think you are getting confused by the fact that Excel recognizes the input as a date and time, but does not pay attention to the exact format of that date and time. So it displays it in the default format for date and time. It has stored all the details that you don't see. It just isn't displaying them.

You can click the top of the first column (to select the whole column), then right click there and select format cells, then select a different date and time format. Excel does support the same format as your original date and time. It just doesn't select that by default.

acid_kewpie guessed that the time stamp (month day time) was desired as one field, not three. So most spaces in the input delimit fields and must be replaced by "," but the first two spaces are included in the first field (what awk sees as the first three fields is what Excel should see as the first single field).

1 members found this post helpful.