Receiving the above error from an application. I narrowed it down to a problem with rsh. If the rsh command is issued too rapidly it fails intermittently.
Try this script on your linux box...
#!/bin/sh -f
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
do
echo $i
rsh... (1 Reply)
I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it?
I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame.
Any help is appreciated. (1 Reply)
Email::Sender::Failure(3pm) User Contributed Perl Documentation Email::Sender::Failure(3pm)NAME
Email::Sender::Failure - a report of failure from an email sending transport
VERSION
version 0.110005
ATTRIBUTES
message
This method returns the failure message, which should describe the failure. Failures stringify to this message.
code
This returns the numeric code of the failure, if any. This is mostly useful for network protocol transports like SMTP. This may be
undefined.
recipients
This returns a list (or, in scalar context, an arrayref) of addresses to which the email could not be sent.
METHODS
throw
This method can be used to instantiate and throw an Email::Sender::Failure object at once.
Email::Sender::Failure->throw(\%arg);
Instead of a hashref of args, you can pass a single string argument which will be used as the "message" of the new failure.
SEE ALSO
o Email::Sender::Permanent
o Email::Sender::Temporary
o Email::Sender::Multi
AUTHOR
Ricardo Signes <rjbs@cpan.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Ricardo Signes.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-03-06 Email::Sender::Failure(3pm)