Redirecting stdout inside a loop Post: 302912871

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Redirecting stdout inside a loop Post 302912871 by Corona688 on Tuesday 12th of August 2014 11:03:56 AM

08-12-2014

Registered User

Quote:

Originally Posted by hmortens

how would you integrate this with summary.txt in this example?

I have no idea.

I am completely unable to give details, due to your complete inability to give details. I don't think that "$LOCATION"/*_fastqc is what you want since that will match all fastqc as I understand it, but cannot say what you do want.

I still don't know which things of your code generate what bits of your output. I still don't know where most of your files are stored... I am not even sure if these fastqc files are inside or outside your 'sample' things or not, which would have helped me answer your last question. In four days and three pages of pulling teeth, I have found one eye, one ear, and one toe of the elephant. I suppose these must be proprietary things you're not allowed to divulge.

I do note that you're blindly continuing to redirect >>summary.fastqc.$date_formatted even though you've told me you don't want to put it there. To not redirect into that file, I suggest not redirecting into that file... It will end up in stdout instead, which will be caught by the outer loop.

If that's not exactly when you wanted it, then print it sooner -- or later. If you wanted only part of it, then filter it then and there. If you print exactly what you want, in the order you want, that's what you'll get in your output.

I think I have given you all the techniques you need.

Last edited by Corona688; 08-12-2014 at 12:41 PM..

Corona688

View Public Profile for Corona688

Visit Corona688's homepage!

Find all posts by Corona688

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

redirecting STDOUT & STDERR

In bash, I need to send the STDOUT and STDERR from a command to one file, and then just STDERR to another file. Doing one or the other using redirects is easy, but trying to do both at once is a bit tricky. Anyone have any ideas?

2. Shell Programming and Scripting

implicitly redirecting stdout to a file

Is there a way to redirect all stdout to a file implicitly - like defining stdout=/home/me/process.log - so that all "echo" commands in several scripts/subscripts are written to that file; instead of having to edit all scripts to redirect the "echo" (e.g. echo 'This is a test ' >>...

3. Shell Programming and Scripting

Redirecting part of output to stdout

Hi, I am trying to execute a command like this: find ./ -name "*.gz" -exec sh -c 'zcat {} | awk -f parse.awk' \; >> output If I want to print the filename, i generally use the -print argument to the find command but when I am redirecting the output to a file, how can I print just the...

4. UNIX for Dummies Questions & Answers

Redirecting several outputs to /dev/stdout

I have an executable that, depending on its input, outputs to either one file or several. It usually prints nothing on screen. The usual way to call this program is to specify an input and output filenames, like this: ./executable.exe -i inputfile -o outputfileIt will then try to use the output...

5. Shell Programming and Scripting

redirecting to stdout in betwen command

can anyone help me in making singleline command for Capital Letters are folders ,small letter are files X,Y,Z are subfolders of A as shown below A - X,Y,Z Folder X has three files a.txt,b.txt,c.txt similarly Y,Z. as shown below X- a.txt,b.txt,c.txt Y- a.txt,b.txt,c.txt Z-...

6. Shell Programming and Scripting

Redirecting stdout to variable while printing it

Hi everybody, I am trying to do the thing you see in the title, and I can't simply do a=$(svn up) echo $a because the program (svn) gives output on lots of lines and in the variable the output is stored on only one line (resulting in a horribly formatted text). Any tips? Thanks,...

7. Shell Programming and Scripting

Redirecting stdout on background task

Hello, I have a script (videostream.sh) which invokes the GStreamer command-line tool gst-launch with all the correct command line parameters. When I invoke this program, I add the '&' character at the end to make it a background task, so that my script can complete and exit, i.e. gst-launch...

8. Shell Programming and Scripting

Redirecting stdout problem

I have a simple bash script that prints sth every 5 seconds. What I do is the following. I redirect the output of the script to a file, tail the file and see that it works and then from another console I delete the file where the output is redirected to. Even though I have deleted the file, the...

9. Shell Programming and Scripting

Redirecting stdout continously to a file

I have a C program that continously outputs info to stdout. The problem is that I am redirecting the stdout and stderr to a file and stdout is written at the end of the problem rather than continously to the file. This could be a problem if for example the program is killed and the stdout output is...

10. Shell Programming and Scripting

Redirecting stdion, stdout within an AT command

Hello, I'm strugling with some redirecting and all help is apreciated. The following program is working as expected, but the result of the AT command doesn't go to any file. Thanks in advance for the help. #!/bin/bash modem=/dev/ttyUSB1 file=/root/imsi.txt # print error to stderr and exit...

LEARN ABOUT OSX

intro

INTRO(9)						   BSD Kernel Developer's Manual						  INTRO(9)

NAME

     intro -- introduction to system kernel interfaces

DESCRIPTION

     This section contains information about the interfaces and subroutines in the kernel.

PROTOTYPES ANSI-C AND ALL THAT
     Yes please.

     We would like all code to be fully prototyped.

     If your code compiles cleanly with cc -Wall we would feel happy about it.	It is important to understand that this isn't a question of just
     shutting up cc, it is a question about avoiding the things it complains about.  To put it bluntly, don't hide the problem by casting and
     other obfuscating practices, solve the problem.

INDENTATION AND STYLE

     Believe it or not, there actually exists a guide for indentation and style.  It isn't generally applied though.

     We would appreciate if people would pay attention to it, and at least not violate it blatantly.

     We don't mind it too badly if you have your own style, but please make sure we can read it too.

     Please take time to read style(9) for more information.

NAMING THINGS

     Some general rules exist:

     1.   If a function is meant as a debugging aid in DDB, it should be enclosed in

		#ifdef DDB

		#endif /* DDB */

	  And the name of the procedure should start with the prefix DDB_ to clearly identify the procedure as a debugger routine.

SCOPE OF SYMBOLS

     It is important to carefully consider the scope of symbols in the kernel.	The default is to make everything static, unless some reason
     requires the opposite.

     There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea
     here either.

     For device drivers and other modules that don't add new internal interfaces to the kernel, the entire source should be in one file if possi-
     ble.  That way all symbols can be made static.

     If for some reason a module is split over multiple source files, then try to split the module along some major fault-line and consider using
     the number of global symbols as your guide.  The fewer the better.

SEE ALSO

     style(9)

HISTORY

     The intro section manual page appeared in FreeBSD 2.2.

BSD
								 December 13, 1995							       BSD