Can any one give me the idea on replacing multiple blank lines with a single blank line?
Please conside it for a file having more than 100 number of characters.
Regards,
Siba (3 Replies)
This is the problem actually:
This regex:
egrep "low debug.*\".*\"" $dbDir/alarmNotification.log
is looking for data between the two quotation marks:
".*\"
When I hate data like this:
low debug 2009/3/9 8:30:20.47 ICSNotificationAlarm Prodics01ics0003 IC... (0 Replies)
I use this command to find a search (Nr of active alarms are) and print one line before and 10 lines after the search keywords.
nawk 'c-->0;$0~s{if(b)for(c=b+1;c>1;c--)print r;print;c=a}b{r=$0}' b=1 a=10 s="Nr of active alarms are:" *.log
However, I would like to know how to tell it to print... (3 Replies)
Background:
I am writing a script to help me automate tweaks and things I apply to a custom Android rom I developed. I am on the very last part of my script, and I am stuck trying to find the right command to do what I seek.
When I build roms from source, a file called updater-script is... (8 Replies)
Hi
Am confused with the usage of "sed" command
I want to replace a single line with multiple lines of a file..
eg.,
A file has
Hi, How are you?
I need to replace as
Am fine
What are You doing?
I used the script as
string1="Hi, How are you?"
echo "$string1 is the value"... (4 Replies)
Experts,
Can someone help me with the below?
I've a variable called NSPMHOME=some_value. I would like change the value of the variable with another variable and something followed by it.
E.g
From NSPHOME=some_value to NSPMHOME=$SOMETHING/test
$SOMETHING has value /opt/tag .
The end... (4 Replies)
Hello All,
just wanted to export multiple tables from oracle sql using unix shell script to csv file and the below code is exporting only the first table.
Can you please suggest why? or any better idea?
export FILE="/abc/autom/file/geo_JOB.csv"
Export= `sqlplus -s dev01/password@dEV3... (16 Replies)
Discussion started by: Hope
16 Replies
LEARN ABOUT CENTOS
fatal
Fatal(3) User Contributed Perl Documentation Fatal(3)NAME
Fatal - Replace functions with equivalents which succeed or die
SYNOPSIS
use Fatal qw(open close);
open(my $fh, "<", $filename); # No need to check errors!
use File::Copy qw(move);
use Fatal qw(move);
move($file1, $file2); # No need to check errors!
sub juggle { . . . }
Fatal->import('juggle');
BEST PRACTICE
Fatal has been obsoleted by the new autodie pragma. Please use autodie in preference to "Fatal". autodie supports lexical scoping, throws
real exception objects, and provides much nicer error messages.
The use of ":void" with Fatal is discouraged.
DESCRIPTION
"Fatal" provides a way to conveniently replace functions which normally return a false value when they fail with equivalents which raise
exceptions if they are not successful. This lets you use these functions without having to test their return values explicitly on each
call. Exceptions can be caught using "eval{}". See perlfunc and perlvar for details.
The do-or-die equivalents are set up simply by calling Fatal's "import" routine, passing it the names of the functions to be replaced. You
may wrap both user-defined functions and overridable CORE operators (except "exec", "system", "print", or any other built-in that cannot be
expressed via prototypes) in this way.
If the symbol ":void" appears in the import list, then functions named later in that import list raise an exception only when these are
called in void context--that is, when their return values are ignored. For example
use Fatal qw/:void open close/;
# properly checked, so no exception raised on error
if (not open(my $fh, '<', '/bogotic') {
warn "Can't open /bogotic: $!";
}
# not checked, so error raises an exception
close FH;
The use of ":void" is discouraged, as it can result in exceptions not being thrown if you accidentally call a method without void context.
Use autodie instead if you need to be able to disable autodying/Fatal behaviour for a small block of code.
DIAGNOSTICS
Bad subroutine name for Fatal: %s
You've called "Fatal" with an argument that doesn't look like a subroutine name, nor a switch that this version of Fatal understands.
%s is not a Perl subroutine
You've asked "Fatal" to try and replace a subroutine which does not exist, or has not yet been defined.
%s is neither a builtin, nor a Perl subroutine
You've asked "Fatal" to replace a subroutine, but it's not a Perl built-in, and "Fatal" couldn't find it as a regular subroutine. It
either doesn't exist or has not yet been defined.
Cannot make the non-overridable %s fatal
You've tried to use "Fatal" on a Perl built-in that can't be overridden, such as "print" or "system", which means that "Fatal" can't
help you, although some other modules might. See the "SEE ALSO" section of this documentation.
Internal error: %s
You've found a bug in "Fatal". Please report it using the "perlbug" command.
BUGS
"Fatal" clobbers the context in which a function is called and always makes it a scalar context, except when the ":void" tag is used. This
problem does not exist in autodie.
"Used only once" warnings can be generated when "autodie" or "Fatal" is used with package filehandles (eg, "FILE"). It's strongly
recommended you use scalar filehandles instead.
AUTHOR
Original module by Lionel Cons (CERN).
Prototype updates by Ilya Zakharevich <ilya@math.ohio-state.edu>.
autodie support, bugfixes, extended diagnostics, "system" support, and major overhauling by Paul Fenwick <pjf@perltraining.com.au>
LICENSE
This module is free software, you may distribute it under the same terms as Perl itself.
SEE ALSO
autodie for a nicer way to use lexical Fatal.
IPC::System::Simple for a similar idea for calls to "system()" and backticks.
perl v5.16.3 2013-02-22 Fatal(3)