Sponsored Content
Full Discussion: Append stderr
Top Forums Shell Programming and Scripting Append stderr Post 302422416 by canduc17 on Tuesday 18th of May 2010 10:18:34 AM
Old 05-18-2010
Excuse me, but I do not understand your answer...No ideas for the stderr/log stuff?
 

10 More Discussions You Might Find Interesting

1. Programming

stderr

in fprint(stderr, "lkjalsdi\n"); what does stderr mean? thanks (1 Reply)
Discussion started by: dell9
1 Replies

2. UNIX for Dummies Questions & Answers

stderr redirection

Does anyone know away of redirecting the stderr for a bourne or korn shell script to a file. (5 Replies)
Discussion started by: blakmk
5 Replies

3. Programming

stderr in background process

Herez the question, In a process which writes into file FILE1 with descriptor fHandler1 and it is run as a background process where would statements be directed when stderr descriptor is used. fprintf(stderr,"some message\n"); assume that session from which it is run is terminated and... (3 Replies)
Discussion started by: matrixmadhan
3 Replies

4. Shell Programming and Scripting

STDERR output

Hi, Need some help here on a script I'm writing. I know that STDERR is normally done is this manner: script 2>stderr.out However, if I wanted to output the stderr from a rsh command how do I do that? Example: su - username -c "rsh $hostname /opt/gilberteu/scriptname" 1>stdout... (5 Replies)
Discussion started by: gilberteu
5 Replies

5. Shell Programming and Scripting

Can I pipe stderr to another process

Hi there, I was wondering if it was possible to pipe stderr to another process. I need to eval commands given as arguments and I would like to redirect stderr to another process. I can redirect stderr to a file like this... toto:~$ command="one=1" toto:~$ eval $command 2> error toto:~$... (5 Replies)
Discussion started by: chebarbudo
5 Replies

6. Shell Programming and Scripting

stderr/stdout

Can somebody explain to me why the diff output is not going to stderr? Yet when I issue a diff from the command line the return code is -ne 1. I am guessing diff always writes to stdout??? Is there away I can force the difff to write to stderr USING THE CURRENT template. If possible, I... (5 Replies)
Discussion started by: BeefStu
5 Replies

7. UNIX for Dummies Questions & Answers

how to get stderr

Hello I try to store stderr into a variable, then if this var is not empty i send an email and stop my script. I think my problem is due of "<$dump" into my command line. my bad command line (see samples below on this post) if ! $returnedStr ; then echo ERROR READING DUMP: ... (8 Replies)
Discussion started by: giova
8 Replies

8. Solaris

can't get stderr port

Hi Experts, i have a solaris 9 OS and i get the following message repeated many time in my /var/adm/messages : Oct 31 16:30:44 baobab rsh: can't get stderr port: Cannot assign requested address have you any idea how can i resolve this issue ??:confused: thanks for help (2 Replies)
Discussion started by: lid-j-one
2 Replies

9. Shell Programming and Scripting

Bash - proper way to append variable to stderr

Hello, Can you please if the bellow is the proper way of appending a variable to the stderr: The easiest way to test this,I was able to imagine, was by touching 5 files and afterwards looping trough to the results: -rw-r--r-- 1 ab owner 0 Sep 14 13:45 file1 -rw-r--r-- 1 ab owner 0 Sep... (7 Replies)
Discussion started by: alex2005
7 Replies

10. Shell Programming and Scripting

Doubt regarding stderr

Hi All, I am writing a shell script code. and i want the stderr to be send to a file and the stdout to be displayed in terminal. In my shell script code i use a read command to get data from user.read -r -p "Enter the type :" data and while i execute my script i use./my_script.sh 2>... (4 Replies)
Discussion started by: Vinoth R
4 Replies
log(n)								 Logging facility							    log(n)

__________________________________________________________________________________________________________________________________________________

NAME
log - Procedures to log messages of libraries and applications. SYNOPSIS
package require Tcl 8 package require log ?1.2.1? ::log::levels ::log::lv2longform level ::log::lv2color level ::log::lv2priority level ::log::lv2cmd level ::log::lv2channel level ::log::lvCompare level1 level2 ::log::lvSuppress level {suppress 1} ::log::lvSuppressLE level {suppress 1} ::log::lvIsSuppressed level ::log::lvCmd level cmd ::log::lvCmdForall cmd ::log::lvChannel level chan ::log::lvChannelForall chan ::log::lvColor level color ::log::lvColorForall color ::log::log level text ::log::logarray level arrayvar ?pattern? ::log::loghex level text data ::log::logMsg text ::log::logError text ::log::Puts level text _________________________________________________________________ DESCRIPTION
The log package provides commands that allow libraries and applications to selectively log information about their internal operation and state. To use the package just execute package require log log::log notice "Some message" As can be seen above, each message given to the log facility is associated with a level determining the importance of the message. The user can then select which levels to log, what commands to use for the logging of each level and the channel to write the message to. In the following example the logging of all message with level debug is deactivated. package require log log::lvSuppress debug log::log debug "Unseen message" ; # No output By default all messages associated with an error-level (emergency, alert, critical, and error) are written to stderr. Messages with any other level are written to stdout. In the following example the log module is reconfigured to write debug messages to stderr too. package require log log::lvChannel debug stderr log::log debug "Written to stderr" Each message level is also associated with a command to use when logging a message with that level. The behaviour above for example relies on the fact that all message levels use by default the standard command ::log::Puts to log any message. In the following example all mes- sages of level notice are given to the non-standard command toText for logging. This disables the channel setting for such messages, assum- ing that toText does not use it by itself. package require log log::lvCmd notice toText log::log notice "Handled by "toText"" Another database maintained by this facility is a map from message levels to colors. The information in this database has no influence on the behaviour of the module. It is merely provided as a convenience and in anticipation of the usage of this facility in tk-based applica- tion which may want to colorize message logs. API
The following commands are available: ::log::levels Returns the names of all known levels, in alphabetical order. ::log::lv2longform level Converts any unique abbreviation of a level name to the full level name. ::log::lv2color level Converts any level name including unique abbreviations to the corresponding color. ::log::lv2priority level Converts any level name including unique abbreviations to the corresponding priority. ::log::lv2cmd level Converts any level name including unique abbreviations to the command prefix used to write messages with that level. ::log::lv2channel level Converts any level name including unique abbreviations to the channel used by ::log::Puts to write messages with that level. ::log::lvCompare level1 level2 Compares two levels (including unique abbreviations) with respect to their priority. This command can be used by the -command option of lsort. The result is one of -1, 0 or 1 or an error. A result of -1 signals that level1 is of less priority than level2. 0 signals that both levels have the same priority. 1 signals that level1 has higher priority than level2. ::log::lvSuppress level {suppress 1} ] (Un)suppresses the output of messages having the specified level. Unique abbreviations for the level are allowed here too. ::log::lvSuppressLE level {suppress 1} ] (Un)suppresses the output of messages having the specified level or one of lesser priority. Unique abbreviations for the level are allowed here too. ::log::lvIsSuppressed level Asks the package whether the specified level is currently suppressed. Unique abbreviations of level names are allowed. ::log::lvCmd level cmd Defines for the specified level with which command to write the messages having this level. Unique abbreviations of level names are allowed. The command is actually a command prefix and this facility will append 2 arguments before calling it, the level of the mes- sage and the message itself, in this order. ::log::lvCmdForall cmd Defines for all known levels with which command to write the messages having this level. The command is actually a command prefix and this facility will append 2 arguments before calling it, the level of the message and the message itself, in this order. ::log::lvChannel level chan Defines for the specified level into which channel ::log::Puts (the standard command) shall write the messages having this level. Unique abbreviations of level names are allowed. The command is actually a command prefix and this facility will append 2 arguments before calling it, the level of the message and the message itself, in this order. ::log::lvChannelForall chan Defines for all known levels with which which channel ::log::Puts (the standard command) shall write the messages having this level. The command is actually a command prefix and this facility will append 2 arguments before calling it, the level of the message and the message itself, in this order. ::log::lvColor level color Defines for the specified level the color to return for it in a call to ::log::lv2color. Unique abbreviations of level names are allowed. ::log::lvColorForall color Defines for all known levels the color to return for it in a call to ::log::lv2color. Unique abbreviations of level names are allowed. ::log::log level text Log a message according to the specifications for commands, channels and suppression. In other words: The command will do nothing if the specified level is suppressed. If it is not suppressed the actual logging is delegated to the specified command. If there is no command specified for the level the message won't be logged. The standard command ::log::Puts will write the message to the channel specified for the given level. If no channel is specified for the level the message won't be logged. Unique abbreviations of level names are allowed. Errors in the actual logging command are not caught, but propagated to the caller, as they may indicate miscon- figurations of the log facility or errors in the callers code itself. ::log::logarray level arrayvar ?pattern? Like ::log::log, but logs the contents of the specified array variable arrayvar, possibly restricted to entries matching the pat- tern. The pattern defaults to * (i.e. all entries) if none was specified. ::log::loghex level text data Like ::log::log, but assumes that data contains binary data. It converts this into a mixed hex/ascii representation before writing them to the log. ::log::logMsg text Convenience wrapper around ::log::log. Equivalent to ::log::log info text. ::log::logError text Convenience wrapper around ::log::log. Equivalent to ::log::log error text. ::log::Puts level text The standard log command, it writes messages and their levels to user-specified channels. Assumes that the suppression checks were done by the caller. Expects full level names, abbreviations are not allowed. LEVELS
The package currently defines the following log levels, the level of highest importance listed first. o emergency o alert o critical o error o warning o notice o info o debug BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category log of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
log, log level, message, message level COPYRIGHT
Copyright (c) 2001-2008 Andreas Kupries <andreas_kupries@users.sourceforge.net> log 1.2.1 log(n)
All times are GMT -4. The time now is 03:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy