It's UWAweek 25 (mid-year break)

helpOSTS

This forum is provided to promote discussion amongst students enrolled in Open Source Tools and Scripting.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 3 articles in this topic
Showing 3 of 439 articles.
Currently 5 other people reading this forum.


 UWA week 20 (1st semester, week 11) ↓
SVG not supported

Login to reply

👍?
helpful
6:16pm Thu 16th May, ANONYMOUS

Hi Professor, If i come across any inconsistent rows more than the header i should be redirect them to stderr.I was trying the same ,still its print me the msg on the screen(redirected to /dev/stderr).so i tried with simple echo statement in terminal to check whether its really redirecting or not.but still its showing me on screen.but when i use the path /dev/null it not showing. So am i doing wrong in redirection or should be done differently? Thanks.



This article has 2 attachments:

 

 

SVG not supported

Login to reply

👍?
helpful
11:34am Sat 18th May, ANONYMOUS

By default both stdout and stderr will be displayed on the screen. This implies, texts displayed on the screen may come from different sources. So, if you are redirecting in a correct manner, you should not worry about that.


SVG not supported

Login to reply

👍x1
helpful
3:48pm Sun 19th May, Michael W.

ANONYMOUS wrote:

By default both stdout and stderr will be displayed on the screen. This implies, texts displayed on the screen may come from different sources. So, if you are redirecting in a correct manner, you should not worry about that.

Hi When you are working to the screen you cannot tell whether the data came from stdout or stderr. The only way is to redirect the streams:

program_tested > from_stdout 2> from_stderr

Cheers MichaelW

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy