4 ms·
I don't know how chef or puppet or that sort of scripts look like but my administration scripts are littered with: #Here I do A because B didn't work and we nee
by teekert 8y ago
I don't know how chef or puppet or that sort of scripts look like but my administration scripts are littered with: #Here I do A because B didn't work and we need it for C.
Or in fstab: # This is the disk I bought together with father. Or in crontab: # This syntax looks weird but otherwise it does not select the correct python env.
(I'm just a home-server admin ;) but that also means significant stuff only happens every 3-5 years at a new LTS or with some major problem, so notes to self are important.)
Such notes to self not only help when things go wrong, they also make for easy repetition of stuff years later. When I reinstall, I first back up the entire old root with all configs and thus all my notes (I could limit myself to /etc probably).
- pbhjpbhj 8y agoI'm primarily a home admin, I keep all `history`, and have a little search script (grep really), that helps a lot.
- teekert 8y agoYeh, I guess the time gaps are so large that you have to. Still, I guess from time to time one also needs to update their orchestration scripts... Tbh, about the ssh, I know its in /etc, the I hit ssh, tab tab / tab tab, ah there is sshd_config, lets search for "root". I also don't really know by heart.
- pnutjam 8y agoA useful tool for tracking system changes and comparing servers. http://sysconfcollect.sourceforge.net/ http://sysconfcollect.sourceforge.net/ It's basically a collection of bash scripts that pull all the config files from your servers. You can view the results as text, or they have a server that helps with long term trending and comparison. For example, I used this to figure out which servers were using specific ssl certs when I renewed them.