public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Pranjal Goswami <mechanic.p@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Pranjal Goswami via Libc-help <libc-help@sourceware.org>
Subject: Re: Need help with adding a new service to nsswitch.conf
Date: Wed, 15 Jun 2022 15:28:00 +0530	[thread overview]
Message-ID: <CANrCi97LdSYSo7=4-26Uz3qa5wuvzeYBA7y7mu7mVGw9NNn8FA@mail.gmail.com> (raw)
In-Reply-To: <87fsk6qu9n.fsf@oldenburg.str.redhat.com>

Yes , by nss folder  I meant the nss subdirectory in glibc . I will  give
it a try  to build my nss module separately. Thanks for the guidance.!
Regards
Pranjal

On Wed, Jun 15, 2022 at 12:37 PM Florian Weimer <fweimer@redhat.com> wrote:

> * Pranjal Goswami:
>
> > I see. So we have an option of building my own NSS module outside the
> > glibc build system , referencing <nss.h> and using
> > NSS_DECLARE_MODULE_FUNCTIONS (secmgr) to get to the declarations for
> > the plug-in functions. So it means that for writing a new module, we
> > need <nss.h> and NSS_DECLARE_MODULE_FUNCTIONS (secmgr) only. There are
> > no other changes to be done within the nss folder ?
>
> With “nss folder”, do you mean the ”nss” subdirectory in the glibc
> source tree?  You should not have to deal with the glibc sources at all,
> you can build your NSS module separately.
>
> Thanks,
> Florian
>
>

      reply	other threads:[~2022-06-15  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 14:56 Pranjal Goswami
2022-06-15  5:51 ` Florian Weimer
2022-06-15  7:03   ` Pranjal Goswami
2022-06-15  7:07     ` Florian Weimer
2022-06-15  9:58       ` Pranjal Goswami [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANrCi97LdSYSo7=4-26Uz3qa5wuvzeYBA7y7mu7mVGw9NNn8FA@mail.gmail.com' \
    --to=mechanic.p@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).