03-23-2013
When shell encounters a redirection operator > the file will be truncated first (0 byte size) and then opened for writing, so after the redirection file is opened for writing, then shell starts test.awk process. This is the reason why you get a blank output file.
But in case of append >> the previous data is retained and then shell starts test.awk process. This is the reason why the data gets appended.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi..
I have a file having record on in 1 line....
I want every 400 characters in a new line...
means in 1st line 1-400
in 2nd line - 401-800 etc
pl help. (12 Replies)
Discussion started by: clx
12 Replies
2. Shell Programming and Scripting
I'm trying to strip any garbage that may be at the end of my text file and that part is working. The problem only seems to be with the really long lines in the file. When the head command is executed I am directing the output to a new file. The new file always get a null in the 4096 position but... (2 Replies)
Discussion started by: geauxsaints
2 Replies
3. Shell Programming and Scripting
I need a script to process a huge single line text file:
The sample of the text is:
"forward_inline_item": "Inline", "options_region_Australia": "Australia", "server_event_err_msg": "There was an error attempting to save", "Token": "Yes", "family": "Family","pwd_login_tab": "Enter Your... (1 Reply)
Discussion started by: hmsadiq
1 Replies
4. Shell Programming and Scripting
I want to use an awk for the following scenario but not sure if it will work or not. I have two input file: F1 and F2
F1
02
05
08
F2
00
01
02
03
04
05
06
07
08
09
10 (1 Reply)
Discussion started by: jclanc8
1 Replies
5. Shell Programming and Scripting
Hi Very much appreciate if somebody could give me a clue ..
I undestand that it could be done with awk but have a limited experience.
I have the following text in the file
1 909 YES NO
2 500 No NO
.
...
1 ... (8 Replies)
Discussion started by: zam
8 Replies
6. Shell Programming and Scripting
i have a file with following type of data
abcd : gggggg
gggggg ; 1234
gggggg ; 5678
gggggg ; 3434
gggggg ; 6565
gggggg ; 1231
1234 ; vvvv ;Eng=Myfirstname
5678 ; xyzf ;Eng=Mysecondname
3434 ; xyzf ;Eng=Mythirdname
6565 ; xyzf ;Eng=Mysfourthname
1231 ; xyzf ;Eng=Mysfifthname... (7 Replies)
Discussion started by: telangmadhuri
7 Replies
7. Shell Programming and Scripting
Hi, all
I have a file containing the following data:
name: PRODUCT_1
date: 2010-01-07
really_long_name: PRODUCT_ABCDEFG
I want to get the date (it is "2010-01-07" here), I could use the following code to do that:
awk... (6 Replies)
Discussion started by: kevintse
6 Replies
8. Shell Programming and Scripting
I dispose of two tab-delimited files (the first column is the primary key):
File 1 (there are multiple rows sharing the same key, I cannot merge them)
A 28,29,30,31
A 17,18,19
B 11,13,14,15
B 8,9File 2 (there is one only row beginning with a given key)
A 2,8,18,30,31
B ... (3 Replies)
Discussion started by: dovah
3 Replies
9. Shell Programming and Scripting
P { margin-bottom: 0.25cm; line-height: 120%; }CODE.cjk { font-family: "WenQuanYi Micro Hei",monospace; }CODE.ctl { font-family: "Lohit Hindi",monospace; }A:link { } I'm trying to build an awk statement to print from a file (file1):
A 1,2,3 *
A 4,5,6 **
B 1
... (4 Replies)
Discussion started by: dovah
4 Replies
10. Shell Programming and Scripting
Hi,my file is in this format
",
\"symbol\": \"Rbm38\"
} ]"
I want to convert it to a more user readable format
_id pubmed text symbol
67196 18667844 Overexpression of UBE2T in NIH3T3 cells significantly promoted colony formation in mouse cell cultures Ube2t
56190 21764855 ... (3 Replies)
Discussion started by: biofreek
3 Replies
POPEN(3) BSD Library Functions Manual POPEN(3)
NAME
pclose, popen -- process I/O
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <stdio.h>
FILE *
popen(const char *command, const char *mode);
int
pclose(FILE *stream);
DESCRIPTION
The popen() function ``opens'' a process by creating a bidirectional pipe, forking, and invoking the shell. Any streams opened by previous
popen() calls in the parent process are closed in the new child process. Historically, popen() was implemented with a unidirectional pipe;
hence, many implementations of popen() only allow the mode argument to specify reading or writing, not both. Because popen() is now imple-
mented using a bidirectional pipe, the mode argument may request a bidirectional data flow. The mode argument is a pointer to a null-termi-
nated string which must be 'r' for reading, 'w' for writing, or 'r+' for reading and writing.
The command argument is a pointer to a null-terminated string containing a shell command line. This command is passed to /bin/sh, using the
-c flag; interpretation, if any, is performed by the shell.
The return value from popen() is a normal standard I/O stream in all respects, save that it must be closed with pclose() rather than
fclose(). Writing to such a stream writes to the standard input of the command; the command's standard output is the same as that of the
process that called popen(), unless this is altered by the command itself. Conversely, reading from a ``popened'' stream reads the command's
standard output, and the command's standard input is the same as that of the process that called popen().
Note that output popen() streams are fully buffered, by default.
The pclose() function waits for the associated process to terminate; it returns the exit status of the command, as returned by wait4(2).
RETURN VALUES
The popen() function returns NULL if the fork(2) or pipe(2) calls fail, or if it cannot allocate memory.
The pclose() function returns -1 if stream is not associated with a ``popened'' command, if stream already ``pclosed'', or if wait4(2)
returns an error.
ERRORS
The popen() function does not reliably set errno.
SEE ALSO
sh(1), fork(2), pipe(2), wait4(2), fclose(3), fflush(3), fopen(3), stdio(3), system(3)
BUGS
Since the standard input of a command opened for reading shares its seek offset with the process that called popen(), if the original process
has done a buffered read, the command's input position may not be as expected. Similarly, the output from a command opened for writing may
become intermingled with that of the original process. The latter can be avoided by calling fflush(3) before popen().
Failure to execute the shell is indistinguishable from the shell's failure to execute command, or an immediate exit of the command. The only
hint is an exit status of 127.
The popen() function always calls sh(1), never calls csh(1).
HISTORY
A popen() and a pclose() function appeared in Version 7 AT&T UNIX.
Bidirectional functionality was added in FreeBSD 2.2.6.
BSD
May 3, 1995 BSD