Re^2: Net::Ping broken on Solaris?

Thanks shmem. Unfortunately, my colleague can bind any address he wants, even weird or non-existent ones, and the module flawlessly fails to notice. It still uses the... er, default interface.

Any clues? Should I go and try to patch the module myself?

Ciao!
--bronto

In theory, there is no difference between theory and practice. In practice, there is.

Comment on Re^2: Net::Ping broken on Solaris? Download Code

Replies are listed 'Best First'.
Re^3: Net::Ping broken on Solaris? by shmem (Chancellor) on Sep 11, 2006 at 16:20 UTC
No further clue atm; and - if it's broken, u-fix-it :-) But it might be the case that binding a socket to an interface just isn't possible on Solaris. Why is interface binding necessary? --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]
Re^4: Net::Ping broken on Solaris? by bronto (Priest) on Oct 07, 2006 at 15:37 UTC
Sorry for not being back for a while... `:-(` Because the script is part of a monitoring system, and he needs to check that a device is reachble from that specific interface. Hmm... I guess that, unless he already solved the problem, I'll have to try a patch `:-D`. Thanks anyway! Ciao! `--bronto` In theory, there is no difference between theory and practice. In practice, there is.	[reply]


go ahead... be a heretic
	PerlMonks