Unable to open a file in perl


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Unable to open a file in perl
# 8  
Old 07-22-2011
Is the verinfo.txt is created by you ?

this clearly permission issue.

create a simple txt file using notepad and put inside the directory which u have the perl file. And try to open the file using your perl program

right click on the verinfo.txt
Right click => Properties => Security => Advanced => Owner => Take Ownership
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Unable to open input kickstart file curl#37

Hi, Getting the below error while installing from ks.cfg unable to open input kickstart file curl#37 Couldn't open file /tmp/swappart Here am trying to include /tmp/swappart file from pre section under disks and partition section. Dont know where exactly am doing wrong My kickstart file... (3 Replies)
Discussion started by: Sumanthsv
3 Replies

2. Shell Programming and Scripting

Perl - Grep open file more then once.

Hi, I am using File::Find to go through a very large tree. I am looking for all xml files and open only those that contain a tag <Updated>. I then want to capture the contents of two tags <Old> and <New>. My problem is, after I open the file and do the first grep for <Updated> (which does... (3 Replies)
Discussion started by: OldGaf
3 Replies

3. Red Hat

unable to open / create any file in vi

Hi, I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5, example vi test it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies

4. Shell Programming and Scripting

PCC-F-NOERRFILE, unable to open error message file

Hi, I was compiling few C programs in the unix server and getting the following error message rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE ... (1 Reply)
Discussion started by: kavithakuttyk
1 Replies

5. UNIX for Advanced & Expert Users

Unable to delete an open file

I am working on a unix server. I killed all the processes with my id on the machine. After that I tried to delete a file, I got an error:- file not removed.Text File busy. Deletion of directory prompted:- Directory not empty. Can anyone help me regarding this...??? Thanks, Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies

6. AIX

Probably an easy SMIT question- "Unable to open temp file"

Hi All, Can't find any documentation on the web for this anywhere, except about three web pages that are in Chinese. When I enter SMIT on this box, I get ERROR MESSAGE: Unable to open temp file I suspected smit.log, but it is universal readable, writeable by root, and I am root.... (6 Replies)
Discussion started by: jeffpas
6 Replies

7. Solaris

unable to open a .log(4MB) file in vi

am unable to open a .log file which is 4MB size. (18 Replies)
Discussion started by: venkatramana
18 Replies

8. UNIX for Dummies Questions & Answers

Unable to open .sql file

Hi , I am running Oracle 8.1.7 on HP-UX B.11.00. Recently I have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out . However I receive the error SP2-0310: unable to open file... (2 Replies)
Discussion started by: Ananth.p
2 Replies

9. UNIX for Dummies Questions & Answers

SP2-0310 unable to open file

Hi , We are running Oracle 8.1.7 on HP-UX B.11.00. Recently we have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script we use has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out . However we receive the error SP2-0310: unable to open file... (2 Replies)
Discussion started by: guru_2007
2 Replies

10. UNIX for Advanced & Expert Users

PCC-F-NOERRFILE, unable to open error message file, facility PR2

I am trying to build a tuxedo server which in turn depends on several Pro*C programs. I am doing it on HP-UX system. It looks to me that the ORACLE_HOME is set properly. But I am getting error message when trying to build. PCC-F-NOERRFILE, unable to open error message file, facility PR2 exit... (1 Reply)
Discussion started by: asutoshch
1 Replies
Login or Register to Ask a Question
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)