I seem very ancientwisdom-oriented these days. Sometimes you've got a system user on your linux server that's used to run a specific service; it's a good practice to employ those users to achieve privilege separation, since it limits the impact of many security breaches. It's security 101, really. If you've
This is another old trick, but I like to tell the world about such amenities. I often find people writing command lines such as: ssh email@example.com or, worse ssh firstname.lastname@example.org or maybe it was ssh email@example.com yes,
Sometimes when performing your daily apt-get update, you'll experience messages like E: The package lists or status file could not be parsed or opened. or The package index files are corrupted Such messages usually don't go away for quite a long time, and may prevent legitimate updates from installing. This
If you develop enough software, most probably you'll have a test/development network at your service. In such networks, which are usually handled through a virtualization infrastructure, machines come and go very quickly. But ssh clients are usually unhappy about that: alan@melquiades:/etc/ssh$ ssh firstname.lastname@example.org.
Bash builtin disown is a not-so-well known [job control command] http://www.gnu.org/software/bash/manual/html_node/Job-Control-Builtins.html), and yet it's an extremely useful one. So what? You've started a remote ssh session, launched some command which is taking very, very long to complete, and you just
Whenever I install a production system/server I tend to enable full automatic updating, because it's usually better that something breaks because of a failed update rather than leaving a production machine unpatched; and if you pick a rather stable distribution (Centos or Ubuntu LTS are good examples) chances that