November 5th, 2013, 01:37 AM
Perl script comes out because of a command failure. How to overcome it?
I've a command which installs android apks one after the other. These apks names are stored in a file. I'm accessing the text file and issuing the below commmand to install apks.
$t = new Net::Telnet (Timeout => undef);
$req_apks = "re2.txt";
open(F2, "<", "$req_apks") or die "Cannot open APK Filelist file:$!";
while ($req = <F2>)
@b= $t->cmd("./adb install $req");
But the command "./adb install " is failing after 1 or 2 apks are installed. I've around 10 apks in the text file to be installed. Is there any way so that even if ./adb install commmand fails the script should continue without dying?
Last edited by ramki067; November 5th, 2013 at 02:28 AM.
November 22nd, 2013, 09:16 AM
Think you need to set the errmode to "return" on the connection, the default is "die" which prints the error and dies.
Set the mode using:
You can then check if there has been an error after calling cmd() as per the docs:
When mode is "return" then the method generating the error places an error message in the object and returns an undefined value in a scalar context and an empty list in list context. The error message may be obtained using errmsg().
Originally Posted by ramki067