08-27-2008
My guess is that the misplaced comma in your third segment is causing the error to be lost. You probably mean die "Can't ftp the file: $!" rather than (die "Can't ftp the file"), $! which is what your code currently seems to do, if I managed to get the precedence right.
Where in your code is there a reference to Local file test2.log? Is that the file you are attempting to upload? (What's the value of $filename?)
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does exception handling exist in any UNIX enviornment? I develop on Windows MSVC++ land and need to port to UNIX. (1 Reply)
Discussion started by: RichardS
1 Replies
2. UNIX for Advanced & Expert Users
Hi, I am trying to use swremove to remove some old software packages before an upgrade. I keep getting the same error below. I have restarted swagent, i have killed the swagent process and started it, and I have restarted the entire system. I have now run out of ideas. Anyone know what the problem... (0 Replies)
Discussion started by: ejbrever
0 Replies
3. HP-UX
Hi, I am trying to use swremove to remove some old software packages before an upgrade. I keep getting the same error below. I have restarted swagent, i have killed the swagent process and started it, and I have restarted the entire system. I have now run out of ideas. Anyone know what the problem... (2 Replies)
Discussion started by: ejbrever
2 Replies
4. UNIX for Dummies Questions & Answers
Dear friends,
I am transferring some files to a windows system from Unix m/c thru FTP Script given below.
echo "open $host
quote USER $userid
quote PASS $pwd
$verbose
$type
cd $dir
bin
put $file
close
quit"|$ftp... (0 Replies)
Discussion started by: Vijayakumarpc
0 Replies
5. Linux
I hope to post in the right forum, otherwise I apologize for this.
if a MMU exception is caused by a process which tries to access to other memory segment (out of its own address space) what the kernel does in this case ?
maybe kernel kills the "bad" process ? (2 Replies)
Discussion started by: Puntino
2 Replies
6. Shell Programming and Scripting
Sometimes when I try to use curl to upload to an ftp server, I get the message:
$curl -T file.wmv ftp.eu.filesonic.com --user user:password
curl: (8) Got a 421 ftp-server response when 220 was expected
How do I get the script to try again if I get the message curl: (8)? (2 Replies)
Discussion started by: locoroco
2 Replies
7. Programming
Hello All,
I have a question ....which I am totally confused about!
If I have a fxn foo in a program which returns a logical value. But it has a posssiblity to throw some exception.
Now my exception handler returns a value as a string stating why the exception occured.
But my... (1 Reply)
Discussion started by: mind@work
1 Replies
8. Solaris
Hi all,
An application works well under 2.6 but under 7 it gives TEXT_IO exceptions. (Is_Open, Check_Is_Open, Get_Line procedures). Any idea?
Regards (3 Replies)
Discussion started by: endoavour
3 Replies
9. Shell Programming and Scripting
I have following file:
NAME=ora.DG1.svc
TYPE=ora.service.type
CARDINALITY_ID=1
TARGET=ONLINE
STATE=ONLINE
NAME=ora.orlene.DG2.svc
TYPE=ora.service.type
CARDINALITY_ID=1
TARGET=ONLINE
STATE=OFFLINE
NAME=ora.MN.acfs
TYPE=ora.registry.acfs.type
TARGET=ONLINE (4 Replies)
Discussion started by: rcc50886
4 Replies
10. Shell Programming and Scripting
Hi Folks,
please advise , I have logs generated on unix machine at location /ops/opt/aaa/bvg.log , now sometimes there come exception in these logs also, so I want to write such a script such that it should continuously monitor these logs and whenever any exception comes that is it try to find... (3 Replies)
Discussion started by: tuntun27272727
3 Replies
LEARN ABOUT OSX
xml::sax::exception
XML::SAX::Exception(3) User Contributed Perl Documentation XML::SAX::Exception(3)
NAME
XML::SAX::Exception - Exception classes for XML::SAX
SYNOPSIS
throw XML::SAX::Exception::NotSupported(
Message => "The foo feature is not supported",
);
DESCRIPTION
This module is the base class for all SAX Exceptions, those defined in the spec as well as those that one may create for one's own SAX
errors.
There are three subclasses included, corresponding to those of the SAX spec:
XML::SAX::Exception::NotSupported
XML::SAX::Exception::NotRecognized
XML::SAX::Exception::Parse
Use them wherever you want, and as much as possible when you encounter such errors. SAX is meant to use exceptions as much as possible to
flag problems.
CREATING NEW EXCEPTION CLASSES
All you need to do to create a new exception class is:
@XML::SAX::Exception::MyException::ISA = ('XML::SAX::Exception')
The given package doesn't need to exist, it'll behave correctly this way. If your exception refines an existing exception class, then you
may also inherit from that instead of from the base class.
THROWING EXCEPTIONS
This is as simple as exemplified in the SYNOPSIS. In fact, there's nothing more to know. All you have to do is:
throw XML::SAX::Exception::MyException( Message => 'Something went wrong' );
and voila, you've thrown an exception which can be caught in an eval block.
perl v5.16.2 2011-09-14 XML::SAX::Exception(3)