| … | |
… | |
| 284 | |
284 | |
| 285 | =item $pinger->add_hosts ([$host...], $interval, $interleave) |
285 | =item $pinger->add_hosts ([$host...], $interval, $interleave) |
| 286 | |
286 | |
| 287 | Similar to C<add_range>, but uses a list of single addresses instead. The |
287 | Similar to C<add_range>, but uses a list of single addresses instead. The |
| 288 | list is specified as an array reference as first argument. Each entry in |
288 | list is specified as an array reference as first argument. Each entry in |
| 289 | the array should be a binary host address, either IPv4 or IPv6. Currently, |
289 | the array should be a binary host address, either IPv4 or IPv6. If all |
| 290 | all entries in the list must be either IPv4 B<OR> IPv6, so you have to |
290 | addresses are IPv4 addresses, then a compact IPv4-only format will be used |
| 291 | create two host ranges if you have mixed addresses. |
291 | to store the list internally. |
| 292 | |
292 | |
| 293 | Minimum C<$interval> is the same as for C<add_range> and can be left out. |
293 | Minimum C<$interval> is the same as for C<add_range> and can be left out. |
| 294 | |
294 | |
| 295 | C<$interlave> specifies an increment between addresses: often address |
295 | C<$interlave> specifies an increment between addresses: often address |
| 296 | lists are generated in a way that results in clustering - first all |
296 | lists are generated in a way that results in clustering - first all |
