Thanks, I'll try it, but from your code, I still don't understand how activate screen log OR file log!
Because I don't need both at the same time, and the flow is something like:
Code:
Start Application >> Log files
execute some commands >> Log files
execute other commands >> Log files
if $1 = "--debug" then disable Log files and show the output on screen
execute some commands > Screen Log
else
execute other commands >> Log files
exit
How can I redirect and append stdout and stderr to a file when using cron? Here is my crontab file:
*/5 * * * * /dir/php /dir/process_fns.php >>& /dir/dump.txt
Cron gives me an 'unexpected character found in line' when trying to add my crontab file.
Regards,
Zach Curtis
POPULUS (8 Replies)
Hi all,
I need to redirect stdout and stderr to a file in a ksh shell. That's not a problem. But I need also the correct exit code for the executed command. In the example below I redirect correctly the stdout & stderr to a file, but I have the exit code of tee command and not for the mv... (2 Replies)
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)
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)
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)
EDIT: Nevermind, figured it out! Forgot to put backslashes in my perl script to not process literals!
Hi everyone. I am trying to have this command pass silently. (no output)
chsh -s /bin/sh news
Currently it outputs.
I've tried....
&> /dev/null
1> /dev/null
2>&1 /dev/null
1>&2... (1 Reply)
Hello
I read a lot of post related to this topic, but nothing helped me. :mad:
I'm running a ksh script with subshell what processing some ldap command. I need to check output for possible errors.
#!/bin/ksh
...
readinput < $QCHAT_INPUT |&
while read -p line
do
echo $line
... (3 Replies)
Currently I am redirecting STDERR and STDOUT to a log file by doing the following
{
My KSH script contents
} 2>&1 | $DEBUGLOG
Problem is the STDERR & STDOUT do not have any date/time associated.
I want this to be something that i can embed into a script opposed to an argument I use... (4 Replies)
I have to redirect STDERR messages both to screen and also capture the same in a file but STDOUT only to the same file.
I have searched in this formum for a solution, but something like
srcipt 3>&1 >&2 2>&3 3>&- | tee errs
doesn't work for me...
Has anyone an idea??? (18 Replies)
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 DEBIAN
log::nullloglite
NullLogLite(3pm) User Contributed Perl Documentation NullLogLite(3pm)NAME
Log::NullLogLite - The "Log::NullLogLite" class implements the Null Object pattern for the "Log::LogLite" class.
SYNOPSIS
use Log::NullLogLite;
# create new Log::NullLogLite object
my $log = new Log::NullLogLite();
...
# we had an error (this entry will not be written to the log
# file because we use Log::NullLogLite object).
$log->write("Could not open the file ".$file_name.": $!", 4);
DESCRIPTION
The "Log::NullLogLite" class is derived from the "Log::LogLite" class and implement the Null Object Pattern to let us to use the
"Log::LogLite" class with null "Log::LogLite" objects. We might want to do that if we use a "Log::LogLite" object in our code, and we do
not want always to actually define a "Log::LogLite" object (i.e. not always we want to write to a log file). In such a case we will create
a "Log::NullLogLite" object instead of the "Log::LogLite" object, and will use that object instead. The object has all the methods that
the "Log::LogLite" object has, but those methods do nothing. Thus our code will continue to run without any change, yet we will not have to
define a log file path for the "Log::LogLite" object, and no log will be created.
CONSTRUCTOR
new ( FILEPATH [,LEVEL [,DEFAULT_MESSAGE ]] )
The constructor. The parameters will not have any affect. Returns the new Log::NullLogLite object.
METHODS
write( MESSAGE [, LEVEL ] )
Does nothing. The parameters will not have any affect. Returns nothing.
level( [ LEVEL ] )
Does nothing. The parameters will not have any affect. Returns -1.
default_message( [ MESSAGE ] )
Does nothing. The parameters will not have any affect. Returns empty string ("").
AUTHOR
Rani Pinchuk, rani@cpan.org
COPYRIGHT
Copyright (c) 2001-2002 Ockham Technology N.V. & Rani Pinchuk. All rights reserved. This package is free software; you can redistribute
it and/or modify it under the same terms as Perl itself.
SEE ALSO Log::LogLite(3), The Null Object Pattern - Bobby Woolf - PLoP96 - published in Pattern Languages of Program Design 3
(http://cseng.aw.com/book/0,,0201310112,00.html)
perl v5.10.0 2009-05-13 NullLogLite(3pm)
07-25-2012
