{
    "content": [
        {
            "type": "text",
            "text": "# nss (info)\n\n## NAME\n\nnss - Name Service Switch configuration file\n\n## DESCRIPTION\n\nEach  call  to  a  function which retrieves data from a system database\nlike the password or group database is  handled  by  the  Name  Service\nSwitch  implementation in the GNU C library.  The various services pro-\nvided are implemented by independent modules, each of  which  naturally\nvaries widely from the other.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **FILES**\n- **EXAMPLES**\n- **SEE ALSO**\n- **COLOPHON**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "nss",
        "section": "",
        "mode": "info",
        "summary": "nss - Name Service Switch configuration file",
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [
            "The  default  configuration  corresponds to the following configuration",
            "file:",
            "NETIDAUTHORITATIVE=FALSE",
            "SERVICESAUTHORITATIVE=FALSE",
            "SETENTBATCHREAD=FALSE"
        ],
        "see_also": [],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 47,
                "subsections": []
            },
            {
                "name": "FILES",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "EXAMPLES",
                "lines": 7,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "COLOPHON",
                "lines": 6,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "nss - Name Service Switch configuration file\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Each  call  to  a  function which retrieves data from a system database\nlike the password or group database is  handled  by  the  Name  Service\nSwitch  implementation in the GNU C library.  The various services pro-\nvided are implemented by independent modules, each of  which  naturally\nvaries widely from the other.\n\nThe  default  implementations  coming with the GNU C library are by de-\nfault conservative and do not use unsafe  data.   This  might  be  very\ncostly  in  some  situations,  especially when the databases are large.\nSome modules allow the system administrator to request taking shortcuts\nif  these  are known to be safe.  It is then the system administrator's\nresponsibility to ensure the assumption is correct.\n\nThere are other modules where the implementation changed over time.  If\nan  implementation  used  to sacrifice speed for memory consumption, it\nmight create problems if the preference is switched.\n\nThe /etc/default/nss file contains a number  of  variable  assignments.\nEach  variable controls the behavior of one or more NSS modules.  White\nspaces are ignored.  Lines beginning with '#' are treated as comments.\n\nThe variables currently recognized are:\n\nNETIDAUTHORITATIVE = TRUE|FALSE\nIf set to TRUE, the NIS backend for the  initgroups(3)  function\nwill accept the information from the netid.byname NIS map as au-\nthoritative.  This can speed up the  function  significantly  if\nthe  group.byname map is large.  The content of the netid.byname\nmap is used as is.  The system administrator has to make sure it\nis correctly generated.\n\nSERVICESAUTHORITATIVE = TRUE|FALSE\nIf  set  to  TRUE,  the NIS backend for the getservbyname(3) and\ngetservbynamer(3) functions will assume that  the  services.by-\nservicename  NIS  map  exists and is authoritative, particularly\nthat it contains both keys with /proto and  without  /proto  for\nboth  primary service names and service aliases.  The system ad-\nministrator has to make sure it is correctly generated.\n\nSETENTBATCHREAD = TRUE|FALSE\nIf set to TRUE, the NIS backend for  the  setpwent(3)  and  set-\ngrent(3)  functions  will  read  the entire database at once and\nthen hand out the requests one by one  from  memory  with  every\ncorresponding  getpwent(3)  or  getgrent(3)  call  respectively.\nOtherwise, each getpwent(3) or getgrent(3) call might result  in\na network communication with the server to get the next entry.\n",
                "subsections": []
            },
            "FILES": {
                "content": "/etc/default/nss\n",
                "subsections": []
            },
            "EXAMPLES": {
                "content": "The  default  configuration  corresponds to the following configuration\nfile:\n\nNETIDAUTHORITATIVE=FALSE\nSERVICESAUTHORITATIVE=FALSE\nSETENTBATCHREAD=FALSE\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "nsswitch.conf\n",
                "subsections": []
            },
            "COLOPHON": {
                "content": "This page is part of release 5.10 of the Linux  man-pages  project.   A\ndescription  of  the project, information about reporting bugs, and the\nlatest    version    of    this    page,    can     be     found     at\nhttps://www.kernel.org/doc/man-pages/.\n\nLinux                             2020-06-09                            NSS(5)",
                "subsections": []
            }
        }
    }
}