Opened 21 years ago
Closed 21 years ago
#744 closed defect (fixed)
Remove "db" parameter from /etc/nsswitch.conf (Glibc)
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
See: http://linuxfromscratch.org/pipermail/lfs-dev/2004-January/041420.html http://linuxfromscratch.org/pipermail/lfs-dev/2004-January/041424.html
In summary, we are using an outdated /etc/nsswitch.conf. The "db" option is not needed on recent Glibc versions. Also, we are disabling NIS Name Service support, but not indicating proper references to enable this if needed/desired.
Additionally, the Linux Network Administrator's Guide (http://www.tldp.org/LDP/nag2/index.html) has many example files for some network configuration files we are using. I recommend we take a look on these examples to see if we are setting up them properly or if we could simplify them by removing unnecessary lines.
Change History (4)
comment:1 by , 21 years ago
comment:2 by , 21 years ago
Summary: | LFS-BOOK network setup needs to be reviewed → Remove "db" parameter from /etc/nsswitch.conf (Glibc) |
---|
Well, I'm using a nsswitch.conf file without "db" for months now, and did not see any problems. Some other folks also use this setup for a long time (see the mentioned threads). This is the suggested setup for nsswitch.conf: # Begin /etc/nsswitch.conf passwd: files group: files shadow: files publickey: files hosts: files dns networks: files protocols: files services: files ethers: files rpc: files netgroup: files # End /etc/nsswitch.conf I had some time to read most part of the Linux Network Administrator's Guide and came to the conclusion we have a decent setup. So we just need to fix the above issue to close this bug.
comment:3 by , 21 years ago
Owner: | changed from | to
---|
Sounds reasonable, but possibly needs a bit more research by network savvy types. Confirming.