Hi:
QnX dosent have the traditional NSSwitch. But I’m guessing that that
functionality is available somewhere else (libc?) in another form.
Help would be greatly appreciated.
Add “lookup file bind” (whichever way you like it) to /etc/resolv.conf. It
will make resolver to lookup names in /etc/hosts first and then fallback to
DNS.
– igor
“Rommel Dongre” <rdongre@pillardata.com> wrote in message
news:aeo14g$nu1$1@nntp.qnx.com…
Hi:
QnX dosent have the traditional NSSwitch. But I’m guessing that that
functionality is available somewhere else (libc?) in another form.Help would be greatly appreciated.
NSSwitch provides the interface to NIS, NIS+, winbindd or the traditioanl
/etc/passwd file for naming of users, groups and hosts. What you have
suggested might work only for hosts, right?
My question is: How do I use winbindd (for example) on QnX, if it doesnt
have NSSwitch?
On my Linux box, I could specify a search order (eg. file NIS+ winbind) in
/etc/nsswitch.conf, and have lookups done by NSSwitch. On QnX, what can I do
to achieve that?
Again, help would be greatly appreciated.
“Igor Kovalenko” <kovalenko@attbi.com> wrote in message
news:aepf78$hfe$1@inn.qnx.com…
Add “lookup file bind” (whichever way you like it) to /etc/resolv.conf.
It
will make resolver to lookup names in /etc/hosts first and then fallback
to
DNS.– igor
“Rommel Dongre” <> rdongre@pillardata.com> > wrote in message
news:aeo14g$nu1$> 1@nntp.qnx.com> …
Hi:
QnX dosent have the traditional NSSwitch. But I’m guessing that that
functionality is available somewhere else (libc?) in another form.Help would be greatly appreciated.
\
You don’t expect resolver to allow using NIS if OS does not support NIS, do
you? Winbind is not supported either. I don’t think anyone cares about
Winbind at all, as for NIS - it is sorely missed in NFS environments indeed,
but that said NIS is obsolete and messy to implement. Even Sun is abandoning
it in favor of LDAP.
Of course, QNX would not support LDAP for authentication either. They need
to put some flexible mechanism in place first, like PAM (which was talked
about but never done).
– igor
“Rommel Dongre” <rdongre@pillardata.com> wrote in message
news:aeqh63$mpo$1@nntp.qnx.com…
NSSwitch provides the interface to NIS, NIS+, winbindd or the traditioanl
/etc/passwd file for naming of users, groups and hosts. What you have
suggested might work only for hosts, right?My question is: How do I use winbindd (for example) on QnX, if it doesnt
have NSSwitch?On my Linux box, I could specify a search order (eg. file NIS+ winbind) in
/etc/nsswitch.conf, and have lookups done by NSSwitch. On QnX, what can I
do
to achieve that?Again, help would be greatly appreciated.
“Igor Kovalenko” <> kovalenko@attbi.com> > wrote in message
news:aepf78$hfe$> 1@inn.qnx.com> …
Add “lookup file bind” (whichever way you like it) to /etc/resolv.conf.
It
will make resolver to lookup names in /etc/hosts first and then fallback
to
DNS.– igor
“Rommel Dongre” <> rdongre@pillardata.com> > wrote in message
news:aeo14g$nu1$> 1@nntp.qnx.com> …
Hi:
QnX dosent have the traditional NSSwitch. But I’m guessing that that
functionality is available somewhere else (libc?) in another form.Help would be greatly appreciated.
\