08-01-2019
I didn't think of that. Thanks for bringing that up. I will be writing several other variables to the stream.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i have following statement in the script
echo -e "$str_XML_col_name:$str_field_type;" >> $i_DC_Key_$i_Tgt_DC_key_Schema
here $i_DC_Key is DC key and $i_Tgt_DC_key are the variables...............
when i ran the script i am getting error rec_merge.sh: $i_DC_Key_$i_Tgt_DC_key_Schema:... (1 Reply)
Discussion started by: mahabunta
1 Replies
2. Shell Programming and Scripting
Hi,
I'm trying to code a simple script (c-shell) on a Solaris box and I'm getting an "Ambiguous" error. These are the lines that cause the error:
On c-shell:
> set var = ""
> @ var = `ls -l`
`ls -l`: Ambiguous
However if I change the second line to:
> set var = `ls -l`
This works... (2 Replies)
Discussion started by: Guillermo Lopez
2 Replies
3. Shell Programming and Scripting
Hi everyone, While I was trying to do
DATE=`date +"%Y%m%d_%H%M%S"`
STARTLOG=$TUXSTDDIR/start_$DATE.log
tmboot -y > $STARTLOG 2>&1
I got an error i.e. Ambiguous output redirect error. Here the first part is to boot the account so there is nothing wrong with that.... (6 Replies)
Discussion started by: pareshan
6 Replies
4. Shell Programming and Scripting
Hi Everyone,
# ll
total 0
-rw-r--r-- 1 root root 0 2010-05-13 11:29 a1.log
-rw-r--r-- 1 root root 0 2010-05-13 11:29 a2.log
-rw-r--r-- 1 root root 0 2010-05-13 11:29 a3.log
# rm a.log
above rm no problem, but when i use "> a.log", it says "-bash: a.log: ambiguous redirect".
... (3 Replies)
Discussion started by: jimmy_y
3 Replies
5. UNIX for Dummies Questions & Answers
I am trying to run the following script and I am getting an "ambiguous redirect" error. I have checked to make sure that the files are all where I have specified and are read/write as needed. Any ideas?
Note: I have removed the actual path info for privacy sake. I have triple checked to make... (1 Reply)
Discussion started by: malantha
1 Replies
6. Shell Programming and Scripting
Hello there,
I'm totally new in bash programming and ran into my first problem.
My script should generate 3 textfiles where the content of the first and the third row are the same in each file. Only the second row is different.
This is what I did in a very simplified explanation:
... (6 Replies)
Discussion started by: johndoe
6 Replies
7. Shell Programming and Scripting
This script has ambiguous redirect error.
...
cd $HOME
cd folder/work
# search all subfolders in work directory
find -mindepth 1 -maxdepth 1 -type d | while read directory
do
CUR_FOLDER="${directory#"./"}"
cd $CUR_FOLDER
chmod 644 *
for ff in *; do
if ; then
... (5 Replies)
Discussion started by: candyme
5 Replies
8. Shell Programming and Scripting
I came across the command string on https://www.unix.com/shell-programming-scripting/141885-awk-removing-data-before-after-pattern.html which was what I was looking for to be able to remove data before a certain pattern. However, outputting the result to a file seems to work on an individual basis... (4 Replies)
Discussion started by: HLee1981
4 Replies
9. Linux
Hi,
I need help on following linux bash script. When I linux commands for loop or while loop on individual file it runs great. but now I want the script to run on N number of files so it gives me ambiguous redirect error on line 12 and syntax error on line 22 : (pls help );
#!/bin/bash
#... (16 Replies)
Discussion started by: Madhusudan Das
16 Replies
10. Shell Programming and Scripting
Hi all,
I've been working on a bash script to help with backups that I have to do at work.
One of the lines in the script is supposed to launch an xterm, log into a specific server node and launch a tar backup to tape. This part works ok, but I've been trying to get stdout and stderr to... (2 Replies)
Discussion started by: Exitalterego
2 Replies
LEARN ABOUT ULTRIX
freopen
fopen(3s) fopen(3s)
Name
fopen, freopen, fdopen - open a stream
Syntax
#include <stdio.h>
FILE *fopen (filename, type)
char *filename, *type;
FILE *freopen (filename, type, stream)
char *filename, *type;
FILE *stream;
FILE *fdopen (fildes, type)
int fildes;
char *type;
Description
The routine opens the file named by filename and associates a stream with it. The routine returns a pointer to the FILE structure associ-
ated with the stream.
The filename points to a character string that contains the name of the file to be opened.
The type is a character string having one of the following values:
"r" Open for reading
"w" Truncate or create for writing
"a" Append; open for writing at end of file, or create for writing
"A" Append with no overwrite; open for writing at end-of-file, or create for writing
"r+" Open for reading and writing
"w+" Truncate or create for reading and writing
"a+" Append; open or create for reading and writing at end-of-file
"A+" Append with no overwrite, open or create for update at end-of-file
The letter "b" can also follow r, w, or a. In some C implementations, the "b" is needed to indicate a binary file, however, it is not
needed in ULTRIX. If "+" is used, the "b" may occur on either side, as in "rb+" or "w+b".
The routine substitutes the named file in place of the open stream. The original stream is closed, regardless of whether the open ulti-
mately succeeds. The routine returns a pointer to the FILE structure associated with stream.
The routine is typically used to attach the preopened streams associated with stdin, stdout and stderr to other files.
The routine associates a stream with a file descriptor. File descriptors are obtained from or which open files but do not return pointers
to a FILE structure stream. Streams are necessary input for many of the Section 3s library routines. The type of stream must agree with
the mode of the open file.
When a file is opened for update, both input and output may be done on the resulting stream. However, output may not be directly followed
by input without an intervening or and input may not be directly followed by output without an intervening or an input operation which
encounters end-of-file.
When a file is opened for append with no overwrite (that is when type is "A" or "A+"), it is impossible to overwrite information already in
the file. The routine may be used to reposition the file pointer to any position in the file, but when output is written to the file, the
current file pointer is disregarded. All output is written at the end of the file and causes the file pointer to be repositioned at the
end of the output. If two separate processes open the same file for append, each process may write freely to the file without fear of
destroying output being written by the other. The output from the two processes will be intermixed in the file in the order in which it is
written.
Return Values
The and routines return a NULL pointer on failure.
Environment
SYSTEM_V
When your program is compiled using the System V environment, append with no overwrite is specified by using the "a" or "a+" type string,
and the "A" and "A+" type strings are not allowed.
POSIX
In the POSIX environment, the "a" and "a+" strings, and the "A" and "A+" strings specify append with no overwrite.
See Also
creat(2), dup(2), open(2), pipe(2), fclose(3s), fseek(3s).
fopen(3s)