3 ms·
i like this post, both style and content. only thing missing would perhaps be a small reference to nis, nis+ and netinfo which were early attempts to build dist
by a-dub 5y ago
i like this post, both style and content. only thing missing would perhaps be a small reference to nis, nis+ and netinfo which were early attempts to build distributed and centrally controlled databases for /etc stuff and ye old faithful which i always preferred for production systems which was to rsync flatfiles out for maximum reliability.
not sure if i totally agree with the immutability argument for /etc, but i suppose that's more about protecting against errant devs abusing sudo privs to do weird things rather than securing things against malicious actors.
- toast0 5y ago> ye old faithful which i always preferred for production systems which was to rsync flatfiles out for maximum reliability. This is the best way. The key is making sure that somewhere you're managing user ids, cause cleaning up after assigning the same uid to different users on different systems gets icky.
- ncmncm 5y agoSome of us like to keep /etc files in git, and git clone them, and check out a branch.
- a-dub 5y agoalso forgot, it's important not to forget the spiritual successor to the client side of nis which is sssd. i think it might be a redhat or canonical thing. either way, if you are insisting on doing live network queries for passwd entries, you generally want it, as it will cache in the event that the network goes down. one of the reasons to prefer flat files is if getpwnam and friends start to hang or return inconsistent results, the system will become unresponsive or misbehave in all sorts of amusing ways.