"Scott R. Godin" wrote: > .... I think it probably would be better to quote the entire parameter > > list for perl, but it did run fine once the call to the non-existent > > bind() function was commented out. > > non-existent? since when? > > perldoc Net::Ping > > $p->bind($local_addr); > Sets the source address from which pings will be sent. This must > be the address of one of the interfaces on the local host. > $local_addr may be specified as a hostname or as a text IP > address such as "192.168.1.1". > > If the protocol is set to "tcp", this method may be called any > number of times, and each call to the ping() method (below) will > use the most recent $local_addr. If the protocol is "icmp" or > "udp", then bind() must be called at most once per object, and > (if it is called at all) must be called before the first call to > ping() for that object.
You are right. It is there. OTOH, that does not mean that it is a good idea to use it. In the way that ramprasad was using it, the code assumed the interface IP to be static. Now, I don't know the innards of his LAN, but the IP used sure looks like one dished up by DHCP. Most of the hosts list also look like DHCP. Those would not hang the process, though; they would only return 0 from the ping() call. So, whether the function exists or not, it should probably not be used unless there is a very specific reaswon why it needs to be. If you scan through the synopsis for the module, you may notice that it is not even mentioned. Joseph -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
