<snip>Does anybody know how to limit the amount of time that linux RPC's clnt_create() takes to detect that a host is not running?
The delay is always near 3.0 seconds. I would like to reduce this wait, so I can monitor more computers with less time.
Does anybody know how to limit the amount of time that clnt_create() takes to detect that a host is not running? This is not restricted to rstat, any RPC program would have this issue.
You can set a client timeout using clnt_control(), in general. What I'm not sure about is whether this applies to clnt_create() on Linux or not. Some man pages I've seen ( here, for example: http://www.die.net/doc/linux/man/man3/clnt_create.3.html ) specifically mention that the default timeout for clnt_create() can be modified using clnt_control(), but the man page on my Red Hat 9 box, for example, doesn't mention that.
I guess it depends on how faithful Linux's implementation of RPC is to the Sun stuff. You might cook up a little test program and try and test it empirically to be sure.
HTH,
Phillip Rhodes
--
When the 1st Amendment no longer protects your voice.
And when the 4th Amendment no longer protects your privacy or your stuff.
Thank God we have the 2nd Amendment to tell our elected representatives that enough is enough.
It's time to put "... from my cold, dead hands" back where it belongs.
FREE AMERICA Vote Libertarian www.lp.org
-- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
