Nevermind, found it.
Editing NISPlus.xs (NISPlus source code) and redefining MASTER_ONLY to be 0 fixed the
problem.
#include <rpcsvc/nis.h>
#ifdef MASTER_ONLY
#undef MASTER_ONLY
#endif
#define MASTER_ONLY 0 /* <<<<---------- */
thanx
:)
fred
-----Original Message-----
From: Fred Albrecht
Sent: 27 March 2002 12:26 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Re: Fwd: (RADIATOR) AuthBy NISPlus
HI Hugh
I find no reference to MASTER_ONLY in my Net::NISPlus code. What version of the
NISPlus module are you refering to?
:)
fred
:wq--------------
<snip>
PS looking at the Net::NISPlus code, I see that nis_lookup etc use the flag
MASTER_ONLY:
MASTER_ONLY
When specified, the client library will bypass any
object caches and any domain replicas and fetch the
object from the NIS+ master server for the object's
domain. This insures that the object returned is up to
date at the cost of a possible performance degradation
and failure if the master server is unavailable or
physically distant.
Looks like a change in the NISPlus library would be required to go further?
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
