Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Redirecting STDERR to file and screen, STDOUT only to file
Top Forums Shell Programming and Scripting Redirecting STDERR to file and screen, STDOUT only to file Post 302698681 by bakunin on Monday 10th of September 2012 11:10:41 AM
Old 09-10-2012
As it is, alister did most of the work and you should thank him.

Quote:
Originally Posted by thuranga
I tried your adjustments, but the STDOUT will always displayed on screen.
hmm, that is unexpected. With the example script i gave (see up this thread). I was able to get the result you wanted, albeit we learned from alister that it was more out of chance and won't work in larger scales.

Quote:
I need this for a cronjob. Actually everything (STDOUT & STDERR) is written to a log. But I want to get informed, when an error occurs.
A cron job has no terminal attached to it at all and output to <stdout> is usually mailed to the owner of the cron job. This is the reason why <stderr> and <stdout> in cronjobs are always redirected - you don't want to get all these mails.

If you want output to go to the "system console" (don't confuse this with a terminal - the console can be any terminal, but not every terminal is the console) use syslogs facilities instead of simple output. Syslog messages can be configured to go either to the system console or every terminal. An example for this would be the "shutdown" command, which usually prints a "The system is about to go down"-message on every terminal. This is done via a syslog facility.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
thuranga
 

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? (9 Replies)
Discussion started by: jshinaman
9 Replies

2. Shell Programming and Scripting

Redirecting STDERR message to STDOUT & file at same time

Friends I have to redirect STDERR messages both to screen and also capture the same in a file. 2 > &1 | tee file works but it also displays the non error messages to file, while i only need error messages. Can anyone help?? (10 Replies)
Discussion started by: vikashtulsiyan
10 Replies

3. Shell Programming and Scripting

How to redirect stderr and stdout to a file

Hi friends I am facing one problem while redirecting the out of the stderr and stdout to a file let example my problem with a simple example I have a file (say test.sh)in which i run 2 command in the background ps -ef & ls & and now i am run this file and redirect the output to a file... (8 Replies)
Discussion started by: sushantnirwan
8 Replies

4. Shell Programming and Scripting

sending stdout and stderr to a file

working on a c sell script I think I understand the concept of it, which is: filename >> file.txt (to appaend) or filename | tee -a file.txt (to append) The problem is that my shell script is used with several parameters, and these commands don't seem to work with just filename. They... (2 Replies)
Discussion started by: mistermojo
2 Replies

5. Shell Programming and Scripting

Redirect stdout/stderr to a file globally

Hi I am not if this is possible: is it possible in bach (or another shell) to redirect GLOBALLY the stdout/stderr channels to a file. So, if I have a script script.sh cmd1 cmd2 cmd3 I want all stdout/stderr goes to a file. I know I can do: ./script.sh 1>file 2>&1 OR ... (2 Replies)
Discussion started by: islegmar
2 Replies

6. Shell Programming and Scripting

Preserve output order when redirecting stdout and stderr

Hi, I already searched through the forum and tried to find a answer for my problem but I didn't found a full working solution, thats way I start this new thread and hope, some can help out. I wonder that I'm not able to find a working solution for the following scenario: Working in bash I... (8 Replies)
Discussion started by: Boemm
8 Replies

7. Programming

stderr stdout to a log file

I originally wrote my script using the korn shell and had to port it to bash on a another server. My script is working find for backing up but noticed that now after the move, I am not getting any output to my log files. Using Korn shell, this worked for me for some odd reason. This was sending... (2 Replies)
Discussion started by: metallica1973
2 Replies

8. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that? Thanks Lucas (4 Replies)
Discussion started by: Lord Spectre
4 Replies

9. Shell Programming and Scripting

Lost redirecting stderr & stdout to 3 files - one each plus combined

Hi folks I need/want to redirect output (stdout, stderr) from an exec call to separate files. One for stderr only and two(!) different (!) ones for the combined output of stderr and stdout. After some research and testing i got this so far : (( exec ${command} ${command_parameters} 3>&1... (6 Replies)
Discussion started by: MDominok
6 Replies

10. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: Code: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log But during script execution I would like the output come back again to screen, how to do that? Thanks Luc edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies

LEARN ABOUT BSD

setupcon

SETUPCON(1)						    Console-setup User's Manual 					       SETUPCON(1)

NAME

       setupcon - sets up the font and the keyboard on the console

SYNOPSIS

       setupcon [OPTION]... [VARIANT]

DESCRIPTION

       setupcon  is  a	program for fast and easy setup of the font and the keyboard on the console.  Most of the time you invoke setupcon without
       arguments.  The keyboard configuration is specified in ~/.keyboard or  /etc/default/keyboard.   The  font  configuration  is  specified	in
       ~/.console-setup  or  /etc/default/console-setup.   Consult  keyboard(5)  and  console-setup(5) for instructions how to configure these two
       files.

       If you have to switch often between different encodings, keyboards or languages, you can prepare several  alternative  configuration  files
       for setupcon.  Suppose that most of the time you will use Greek language with Greek keyboard layout, but sometimes you need to type in Ger-
       man with German keyboard layout.  In this situation you should customize the main configuration	files  (keyboard  and  console-setup)  for
       Greek.  Also, create alternative configuration files for German named keyboard.german and console-setup.german.	Then in order to configure
       the console for Greek you will simply run the command with no arguments: setupcon and in order to configure the console for German you will
       use setupcon german.

OPTIONS

       VARIANT
	      Specifies  which	configuration  file to use.  With no variant, the configuration files of setupcon are named console-setup and key-
	      board.  On the other hand, if you use e.g.  chukchi as VARIANT then the  configuration  files  are  console-setup.chukchi  and  key-
	      board.chukchi.   In this way you can have easy access to several different configurations - for example one for the Chukchi language
	      and another for the default configuration.

       -v, --verbose
	      Be more verbose.	 Use this option if something goes wrong or while experimenting with the configuration files.

       -k, --keyboard-only
	      Setup the keyboard only, do not setup the font or the terminal.  On Linux it is enough to do this configuration only once.

       -f, --font-only
	      Setup the font only, do not setup the keyboard or the terminal.  On Linux this configuration should be repeated each time a new con-
	      sole driver is activated (for example when the frame buffer becomes active).

       -t, --terminal-only
	      Setup the terminal only, do not setup the keyboard or the font.

       --current-tty
	      Setup the only the current virtual terminal.

       --force
	      Do  not  check  whether  we are on the console.  Notice that you can be forced to hard-reboot your computer if you run setupcon with
	      this option and the screen is controlled by a X server.

       --save This option can be useful if you want to use setupcon early in the boot process while /usr is not yet mounted and the required  data
	      are  not	available.   This option will make setupcon copy the required files in /etc/console-setup/ in order to make them available
	      before /usr is mounted.  If you use setupcon early in the boot process, then you should run it with this option after  every  change
	      of the console configuration.

       --save-only
	      The  same as --save, but does not setup anything.  This option can be useful if you want to save the required files while the screen
	      is controlled by a X server.

       --save-keyboard FILE
	      For use by initrd builders.  Do not configure anything.  Save an usable keyboard layout in FILE.

       --setup-dir DIR
	      For use by initrd builders.  Do not configure anything.  Arrange in the directory DIR everything necessary in order to configure the
	      console.	 The  file DIR/morefiles lists all binaries the initrd builder has to install in the initrd image.  All other files in DIR
	      have to be copied unchanged in the initrd.  In order to configure the console one has to run the script DIR/bin/setupcon.

       -h, --help
	      Display usage information.

FILES

       ~/.console-setup
       ~/.keyboard
       /etc/default/console-setup
       /etc/default/keyboard
       /etc/default/console-setup.VARIANT
       /etc/default/keyboard.VARIANT
       /etc/console-setup/

SEE ALSO

       keyboard(5), console-setup(5)

console-setup							    2011-03-17							       SETUPCON(1)
All times are GMT -4. The time now is 03:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy