Read a text file of multiple IPs and launch against a set of lines.

[jdash]

Upfront notice: Just started working with AutoIt3, so noob to the language still. I'm not a total noob with programming just trying to wrap my head around AutoIt3 specifically.

Okay, here's the scenario. I want to hand my script a txt file of IP addresses (could be any number of IPs). What I want to do is have the script look at the text file and perform an action against a number of those addresses (essentially creating multiprocessing) and continue to loop through the file until its ran against all IPs.

I've been looking through the help files. I'm assuming it's a mix of

_FileCountLines

_FileReadToArray

FileReadLine

I'm having a bit of trouble figuring out the format for it in the script.

So example.

You have a txt file of say 57 lines each line has one IP address.

I want to run a psexec command against each one of these IPs but I don't want to do one at a time would take to long.

So I define a variable that will stand for how many machines to run against at once (how many instances of psexec in this case). Let's say we set the variable at 5.

How can I code it for the script to read the text file grab the first 5 lines as an array run a psexec command against each simultaneously (psexec $line1 ping localhost, for example) then loop back into the file grab the next 5 lines and so on and so forth until run against all lines?

Thanks for the help!

[JLogan3o13]

Understand that AutoIt it not multi-threaded, so whether you grab one at a time or five at a time, you're going to be processing each IP one at a time. You'll probably realize better performance if you read them all into an array and be done with it, rather than the constant back and forth.

 

Something like this should get you started:

#include <Array.au3>
#include <File.au3>

$aArray = FileReadToArray(@DesktopDir & "\IPs.txt")
    ;_ArrayDisplay($aArray)
    
    For $element In $aArray
        ;Do stuff. Check out the Ping function, I would suggest pinging first, then taking action if you get a response.
    Next

Edited February 20, 2014 by JLogan3o13

[jdash]

Right thanks for the clarification on multi-threading. I get the feeling that word creates some strong responses here. I think I'm more looking for multi-processing in this case (multi-threading would be great, but I will work with what I can get. ) I've seen a few examples on ways to handle child scripts/programs. I'll dig into them more.

Looking at your example I'm assuming I could do that and couple it with a _FileCountLines to control how many child processes I launch? I get it still will only happen one at a time, but on some networks I would run this script throttling the connections would be necessary and I wouldn't want to start another child process until ones before it finished.

[BrewManNH]

You don't need _filecountlines when you use FileReadToArray or _FileReadToArray the count of lines is easy to get. Using the first function you'd use Ubound on the array to tell you how many lines it has, with the second function you'd look in the $array[0] element for the line count, if you've set it up to return it in the zero element.

[kylomas]

jdash,

Is the purpose of the ping to find out if the connection is alive?  And, what is the expected max round trip iin milliseconds?

[kylomas]

jdash,

Not exactly what you need but an example of pinging 100 randomly generated IP addresses (100 ms timeout)...

expandcollapse popup

#include <array.au3>

; generate 100 random ip addresses on node 99.xxx.xxx.xxx ----------------------------------------------

local $ip_out, $fname = @scriptdir & '\ip.txt'
for $1 = 1 to 100
    $ip_out &= '99.' & random(0,255,1) & '.' & random(0,255,1) & '.' & random(0,255,1) & @crlf
Next
filedelete($fname)
filewrite($fname,$ip_out)

; start of your code / using file generated above as input ---------------------------------------------

local $aIP = stringsplit(fileread($fname),@crlf,1), $rname = @scriptdir & '\RSLT.txt'
local $aRSLT[$aIP[0]-1][2]

for $1 = 1 to $aIP[0]-1
    $aRSLT[$1-1][0] = $aIP[$1]
Next

local $st = timerinit()

progresson("Pinging IP's",'','')
for $1 = 0 to ubound($aRSLT) - 1
    $aRSLT[$1][1] = ping($aRSLT[$1][0],100)
    progressset(($1/ubound($aRSLT)) * 100,$aRSLT[$1][0],'')
Next
progressoff()

ConsoleWrite(stringformat('Time to ping = %2.4f seconds',timerdiff($st)/1000) & @LF)

$ip_out = ''
for $1 = 0 to ubound($aRSLT) - 1
    $ip_out &= stringformat('%-20s  %-10s',$aRSLT[$1][0],$aRSLT[$1][1]) & @CRLF
Next

filedelete($rname)
filewrite($rname,$ip_out)

shellexecute($rname)

Am working on something that will read a file then run a fixed number of scripts simultaneously passing 1 line for each script as a parm, until all lines have been passed.

kylomas

Edited February 21, 2014 by kylomas

[lewisg]

I use a slightly modified version of Madadar's   _CheckOnlineStatus() UDF in a few of my scripts. I bump up the  $i_MaxProcess to 100 and can ping and get results for over 900 PCs in about 15 seconds.

[kylomas]

  On 2/21/2014 at 3:31 PM, lewisg said:

I use a slightly modified version of Madadar's   _CheckOnlineStatus() UDF in a few of my scripts. I bump up the  $i_MaxProcess to 100 and can ping and get results for over 900 PCs in about 15 seconds.

 

Post a link to it...should solve jdash's problem....

edit: >Manadar's IP Scanner

Edited February 21, 2014 by kylomas

[Gianni]

Manadar's >nping (IP Scanner) could be of help

also >my adaptation to an udf like version can simplify the use

Edited February 22, 2014 by PincoPanco

[kylomas]

jdash,

After re-visiting this thread it occured to me that we did not answer your core question, "read a file and process 'x' number of lines at a time". 

The following scripts are a driver / slave setup designed to do just that.

Driver script (Mult Runner.au3)

   Read a file.

  Call a "slave" script for each line of the file passing the line as a parameter to the "slave" script.

  Provide a throttle to control max number of "slave" scripts that can run concurrently.

  Log script start time to a common log.

Slave script (Slave.au3)

  Verify parm.

  Log start/stop time and PID to a common log.

Log Function

  All scripts write to a common log file.  File locking is done with _WinAPI_FileInUse.

  Note - I have had an intermittent file open problems when trying to run 50+ concurrent "slave" scripts.

Both scripts and the input file must reside in the same dir.  The log file will be created there also.

The "Slave" script is setup to do nothing more than start, sleep for a random time and end.  I would advise running the driver script with your input file and leaving the slave script as is till you are familiar with it's behaviour.

Driver.au3

slave.au3

kylomas