Sponsored Content
Top Forums Shell Programming and Scripting perl - print to a log file and screen Post 302132600 by cbkihong on Friday 17th of August 2007 08:28:11 PM
Old 08-17-2007
If you meant to do some logging, consider using a more sophisticated logger mechanism, such as log4perl, described here:

perl.com: Retire your debugger, log smartly with Log::Log4perl!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

echo or print to screen and file

I did a search for this topic but I couldn't find it and I was sure I have seen something similar before (hard because I am not sure of the criteria for the keywords) What I was looking for was to be able to echo a message to the screen from a bash.sh script at the same time logging it to a... (2 Replies)
Discussion started by: Shakey21
2 Replies

2. Shell Programming and Scripting

print to screen and to file using awk?!

Hello all!.. does anyone know the syntax to print to the screen and to a file? Im using something like AWK .... print header |tee -a invalid_csv_file ; END {..} ' invalid_csv_file="$invalid_csv_dir_file" but no joy? I get sh:... (2 Replies)
Discussion started by: satnamx
2 Replies

3. Shell Programming and Scripting

Putting screen output in a log file

I want to output screen messages to a logfile when executing an automated script. I have tried the script and command to do this but with no luck. Thanks, Nicole (5 Replies)
Discussion started by: nsutti
5 Replies

4. Shell Programming and Scripting

perl: howto print to screen & filehandle

Hello, I need to print messages both to screen and to file handle in perl , like tee does in unix . Any suggestions ? Thanks (2 Replies)
Discussion started by: Alalush
2 Replies

5. UNIX Desktop Questions & Answers

Output terminal sessions to screen and log file

I would like to use a terminal session to ssh to switches and routers. I need to capture data while logged into switches to a file I can email for troubleshooting. I use termial to log into Cisco switch, run the sh tech command, and then sent the output to cisco. Is there a way to run a... (4 Replies)
Discussion started by: tdelliott
4 Replies

6. UNIX for Dummies Questions & Answers

how to print script output to screen and file

Hi all, I have a script that bulk loads thousands of lines of data. I need to log the output during the execution of the script. I know I can redirect (">") the output to a file; however, I want the output going to both the screen and the log file. I thought I could use pipe to pipe the... (10 Replies)
Discussion started by: orahi001
10 Replies

7. Shell Programming and Scripting

Logging ALL standard out of a bash script to a log file, but still show on screen

Is it possible to store all standard-out of a bash script and the binaries it calls in a log file AND still display the stdout on screen? I know this is possible to store ALL stdout/stderr of a script to a single log file like: exec 1>&${logFile} exec 2>&1 But running a script with the... (3 Replies)
Discussion started by: ckmehta
3 Replies

8. Shell Programming and Scripting

Complete Screen Output to Log File

Hi, I would need to log the whole screen ouput to a log file. All Inputs from the Agent, all echo´s and DBMS Outputs from the PL/SQL. Basicly everything what I can see during the run on the screen. I tried it already with #exec 2>$BASELOG/RUN.log #exec 1>$BASELOG/RUN.log #exec >... (1 Reply)
Discussion started by: enjoy
1 Replies

9. Shell Programming and Scripting

Perl :How to print the o/p of a Perl script on console and redirecting same in log file @ same time.

How can i print the output of a perl script on a unix console and redirect the same in a log file under same directory simultaneously ? Like in Shell script, we use tee, is there anything in Perl or any other option ? (2 Replies)
Discussion started by: butterfly20
2 Replies

10. Shell Programming and Scripting

Print the one function's log to the screen

c() { if something failed;then echo "failed" exit 1 fi } f() { functinona #if something failed call "c" functionb #if something failed call "c" } f > log 2>&1 #put the log to file not print on the screen I want all the stdout/stdrr to the log file... (3 Replies)
Discussion started by: yanglei_fage
3 Replies
Config(3)						User Contributed Perl Documentation						 Config(3)

NAME
Log::Log4perl::Config - Log4perl configuration file syntax DESCRIPTION
In "Log::Log4perl", configuration files are used to describe how the system's loggers ought to behave. The format is the same as the one as used for "log4j", just with a few perl-specific extensions, like enabling the "Bar::Twix" syntax instead of insisting on the Java-specific "Bar.Twix". Comment lines (starting with arbitrary whitespace and a #) and blank lines (all whitespace or empty) are ignored. Also, blanks between syntactical entities are ignored, it doesn't matter if you write log4perl.logger.Bar.Twix=WARN,Screen or log4perl.logger.Bar.Twix = WARN, Screen "Log::Log4perl" will strip the blanks while parsing your input. Assignments need to be on a single line. However, you can break the line if you want to by using a continuation character at the end of the line. Instead of writing log4perl.appender.A1.layout=Log::Log4perl::Layout::SimpleLayout you can break the line at any point by putting a backslash at the very (!) end of the line to be continued: log4perl.appender.A1.layout= Log::Log4perl::Layout::SimpleLayout Watch out for trailing blanks after the backslash, which would prevent the line from being properly concatenated. Loggers Loggers are addressed by category: log4perl.logger.Bar.Twix = WARN, Screen This sets all loggers under the "Bar::Twix" hierarchy on priority "WARN" and attaches a later-to-be-defined "Screen" appender to them. Settings for the root appender (which doesn't have a name) can be accomplished by simply omitting the name: log4perl.logger = FATAL, Database, Mailer This sets the root appender's level to "FATAL" and also attaches the later-to-be-defined appenders "Database" and "Mailer" to it. The additivity flag of a logger is set or cleared via the "additivity" keyword: log4perl.additivity.Bar.Twix = 0|1 (Note the reversed order of keyword and logger name, resulting from the dilemma that a logger name could end in ".additivity" according to the log4j documentation). Appenders and Layouts Appender names used in Log4perl configuration file lines need to be resolved later on, in order to define the appender's properties and its layout. To specify properties of an appender, just use the "appender" keyword after the "log4perl" intro and the appender's name: # The Bar::Twix logger and its appender log4perl.logger.Bar.Twix = DEBUG, A1 log4perl.appender.A1=Log::Log4perl::Appender::File log4perl.appender.A1.filename=test.log log4perl.appender.A1.mode=append log4perl.appender.A1.layout=Log::Log4perl::Layout::SimpleLayout This sets a priority of "DEBUG" for loggers in the "Bar::Twix" hierarchy and assigns the "A1" appender to it, which is later on resolved to be an appender of type "Log::Log4perl::Appender::File", simply appending to a log file. According to the "Log::Log4perl::Appender::File" manpage, the "filename" parameter specifies the name of the log file and the "mode" parameter can be set to "append" or "write" (the former will append to the logfile if one with the specified name already exists while the latter would clobber and overwrite it). The order of the entries in the configuration file is not important, "Log::Log4perl" will read in the entire file first and try to make sense of the lines after it knows the entire context. You can very well define all loggers first and then their appenders (you could even define your appenders first and then your loggers, but let's not go there): log4perl.logger.Bar.Twix = DEBUG, A1 log4perl.logger.Bar.Snickers = FATAL, A2 log4perl.appender.A1=Log::Log4perl::Appender::File log4perl.appender.A1.filename=test.log log4perl.appender.A1.mode=append log4perl.appender.A1.layout=Log::Log4perl::Layout::SimpleLayout log4perl.appender.A2=Log::Log4perl::Appender::Screen log4perl.appender.A2.stderr=0 log4perl.appender.A2.layout=Log::Log4perl::Layout::PatternLayout log4perl.appender.A2.layout.ConversionPattern = %d %m %n Note that you have to specify the full path to the layout class and that "ConversionPattern" is the keyword to specify the printf-style formatting instructions. Configuration File Cookbook Here's some examples of often-used Log4perl configuration files: Append to STDERR log4perl.category.Bar.Twix = WARN, Screen log4perl.appender.Screen = Log::Log4perl::Appender::Screen log4perl.appender.Screen.layout = Log::Log4perl::Layout::PatternLayout log4perl.appender.Screen.layout.ConversionPattern = %d %m %n Append to STDOUT log4perl.category.Bar.Twix = WARN, Screen log4perl.appender.Screen = Log::Log4perl::Appender::Screen log4perl.appender.Screen.stderr = 0 log4perl.appender.Screen.layout = Log::Log4perl::Layout::PatternLayout log4perl.appender.Screen.layout.ConversionPattern = %d %m %n Append to a log file log4perl.logger.Bar.Twix = DEBUG, A1 log4perl.appender.A1=Log::Log4perl::Appender::File log4perl.appender.A1.filename=test.log log4perl.appender.A1.mode=append log4perl.appender.A1.layout = Log::Log4perl::Layout::PatternLayout log4perl.appender.A1.layout.ConversionPattern = %d %m %n Note that you could even leave out log4perl.appender.A1.mode=append and still have the logger append to the logfile by default, although the "Log::Log4perl::Appender::File" module does exactly the opposite. This is due to some nasty trickery "Log::Log4perl" performs behind the scenes to make sure that beginner's CGI applications don't clobber the log file every time they're called. Write a log file from scratch If you loathe the Log::Log4perl's append-by-default strategy, you can certainly override it: log4perl.logger.Bar.Twix = DEBUG, A1 log4perl.appender.A1=Log::Log4perl::Appender::File log4perl.appender.A1.filename=test.log log4perl.appender.A1.mode=write log4perl.appender.A1.layout=Log::Log4perl::Layout::SimpleLayout "write" is the "mode" that has "Log::Log4perl::Appender::File" explicitely clobber the log file if it exists. SEE ALSO
Log::Log4perl::Config::PropertyConfigurator Log::Log4perl::Config::DOMConfigurator Log::Log4perl::Config::LDAPConfigurator (coming soon!) COPYRIGHT AND LICENSE
Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.1 2010-02-07 Config(3)
All times are GMT -4. The time now is 02:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy