Shell Programming and Scripting

I have a feeling this may have something to do with the amount of data you are attempting to write into the file. If so, it's possible that the resources just aren't there on the box. If you're on a shared vhost the admins could be killing the process off before it completes writing as it may alert as a runaway process. So on that note, I hope your on a managed or doing from your own box at home.

If it is a large amount of data, better to save yourself from having to open that file. My suggestion would be to redirect stderr to an empty file. Then look for broken pipes or another from there.

Hello All,

Below code is giving the same output as this:/omp/bin/TICLI "op:alarm,all" > outputfile.can you please explain what 2>&1 is doing.

Code:

/omp/bin/TICLI "op:alarm,all" > outputfile 2>&1

Second Solution:

Code:

OUT=$(/omp/bin/TICLI "op:alarm,all") && echo $OUT > outputfile

Above code is giving this error on execution:

KarachiOMP root> ./code2
./code2: syntax error at line 5: `OUT=$' unexpected

Can you please find whats the issue.

Third there is no issue of resources as i have the admin rights of the box.

My requirement is to just get complete output of the command in the outputfile.
/omp/bin/TICLI "op:alarm,all" > outputfile

but problem is this that everytime differnet amount of data comes into output file, sometimes only few lines and sometime enough but not complete.

Regards,
Waqas Ahmed

OK "$(command)" is a command expansion technique to get the output of a command into a variable, if your shell does not like that format then you could use:

Code:

OUT=`/omp/bin/TICLI "op:alarm,all"` && echo $OUT > outputfile

Instead of "$(...)" you use backticks (not single quotes) like `...`

By "resources" I believe phpfreak is referring to physical resources NOT permissions.

You could be limited by memory, cpu, file handles, drive space, etc...

Code:

OUT=`/omp/bin/TICLI "op:alarm,all"` && echo $OUT > outputfile

I used the above code and it is also not giving the complete output, second it is also changing the output format.

i also want to share one more thing. That we have one log folder in which our logs files are maintained on daily basis. Every command we run on TICLI shell that command's output also goes into that logs files.

So whenever i run my script so it do not gives complete output, but in log file complete output of the command comes.

Any idea how that happens, but why its not happening through my script.

Actually "op:alarm,all" takes time for giving complete output. Those commands which output is not very large are working properly with my script but because "op:alarm,all" command takes time for output, the complete output is not coming through script.

That is because you need to quote the "$OUT" variable as follows:

Code:

OUT=`/omp/bin/TICLI "op:alarm,all"` && echo "$OUT" > outputfile

Note:

echoing a variable that has newlines in the variable contents can cause all \n (newline) characters to be stripped out when not quoting.

Is "/omp/bin/TICLI" a compiled application? Does it call a compiled application? What you may be running into is that the code inside the compiled application is told to output MORE info to a log than what it does on the command line. If that is the case you may be unable to change this without editing the source code to that application and re-compiling.