open ( my $DAT, "paflink filename |") or die "Could not open $ARGV[0]: $!";
With this:
Code:
open(my $DAT, "-|", "paflink filename") or die $!;
Thanks - I tried the below code. It is able to capture the output in the Output.txt but its not capturing the output from the print lines which are within while loop.
Code:
open(my $DAT, "-|", " paflink -p /path/ ./InputFile.txt Output.txt") or die $!;
Last edited by ahmedwaseem2000; 02-27-2014 at 11:24 PM..
I'm working on a script that will perform a backup, save a log of said backup and send the output to me in an email. Everything is working fine so far except that I can't figure out how to specify a maximum file size for the log file. I don't want a runaway log file jamming up the server.... (7 Replies)
Hi guys,
I Have written a script,In that it will call another file which contains the sql quaries.
while wxecuting that I am getting the below exception
01/16|06:28:06:16800: Operating System Error|Failed to open output file
Can anybody help me about this,,Its urgent (0 Replies)
Hi All :
I wanted a unix command by which I could be able to print the output to a file and at the same time to a printer. Any help will be greatly appreciated.
Regards,
Ramamurthy Dasari (1 Reply)
Hello,
If I run a program from within shell, the output is displayed in the command line terminal. Is there a way I can capture that output and choose only the very last string in it to send it to a new file?
Thank you (6 Replies)
Hi,
I am running a shell script called dbProcess.sh which performs shutdown and startup of various Oracle instances we have.At the time of execution the script produces the following output to the command line window
$./dbProcess.sh stop
#### Run Details ######
Hostname : server-hop-1... (4 Replies)
Hi
I have a script that will run multiple unix & sql commands. I want to see the output as well as capture it to a log file for further analysis. Is there an easy way to do that instead of adding "tee -a logfile" on everyline or even on the execute line (i.e. script | tee -s logfile).
Thanks (1 Reply)
I want to capture the debug for the below command in output file .
i tried like this but its not working:
sh -xv <scriptname> >> output.log
i want the output in a log file.
Anyone plz help in this (2 Replies)
Hi All. Thanks for your help in advance.
I have a requirement to examine the number of delimiters in each record of a file. If the record has the expected number of delimiters it should be passed into a 'good' file. If it does not, the record should be passed into a 'bad' file. I have been able... (8 Replies)
Hello, I need to get few values from a XML file and output needs to be written in another file with pipe delimited format. The Header & Footer of the Pipe Delimited file will be constant.
The below is my sample XML file. I need to pull the values in between the XML tags <Operator_info to... (15 Replies)
Hi,
I have a script that runs a tar command to standard out then pipes to a gzip:
tar cfE - * | gzip -c > OUT.gz
At the moment, even if the tar fails (e.g. because of lack of disk space), the gzip still runs successfully.
Is there a way to make the whole line exit with a non-zero error... (6 Replies)
Perl::Critic::Policy::InputOutput::ProhibitTwoArgOpen(3)User Contributed Perl DocumentatioPerl::Critic::Policy::InputOutput::ProhibitTwoArgOpen(3)NAME
Perl::Critic::Policy::InputOutput::ProhibitTwoArgOpen - Write "open $fh, q{<}, $filename;" instead of "open $fh, "<$filename";".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
The three-argument form of "open" (introduced in Perl 5.6) prevents subtle bugs that occur when the filename starts with funny characters
like '>' or '<'. The IO::File module provides a nice object-oriented interface to filehandles, which I think is more elegant anyway.
open( $fh, '>output.txt' ); # not ok
open( $fh, q{>}, 'output.txt' ); # ok
use IO::File;
my $fh = IO::File->new( 'output.txt', q{>} ); # even better!
It's also more explicitly clear to define the input mode of the file, as in the difference between these two:
open( $fh, 'foo.txt' ); # BAD: Reader must think what default mode is
open( $fh, '<', 'foo.txt' ); # GOOD: Reader can see open mode
This policy will not complain if the file explicitly states that it is compatible with a version of perl prior to 5.6 via an include
statement, e.g. by having "require 5.005" in it.
CONFIGURATION
This Policy is not configurable except for the standard options.
NOTES
There are two cases in which you are forced to use the two-argument form of open. When re-opening STDIN, STDOUT, or STDERR, and when doing
a safe pipe open, as described in perlipc.
SEE ALSO
IO::Handle
IO::File
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::InputOutput::ProhibitTwoArgOpen(3)