←back to thread

804 points jryio | 1 comments | | HN request time: 0.205s | source
Show context
speedgoose ◴[] No.45661785[source]
Looking at the htop screenshot, I notice the lack of swap. You may want to enable earlyoom, so your whole server doesn't go down when a service goes bananas. The Linux Kernel OOM killer is often a bit too late to trigger.

You can also enable zram to compress ram, so you can over-provision like the pros'. A lot of long-running software leaks memory that compresses pretty well.

Here is how I do it on my Hetzner bare-metal servers using Ansible: https://gist.github.com/fungiboletus/794a265cc186e79cd5eb2fe... It also works on VMs.

replies(15): >>45661833 #>>45662183 #>>45662569 #>>45662628 #>>45662841 #>>45662895 #>>45663091 #>>45664508 #>>45665044 #>>45665086 #>>45665226 #>>45666389 #>>45666833 #>>45673327 #>>45677907 #
RobRivera ◴[] No.45665226[source]
To learn tricks like this what resource do you recommend I read? System administrators handbook? (Still on my TOREAD queue)
replies(1): >>45667176 #
1. eitland ◴[] No.45667176[source]
"The practice of System and Network administration" by Tom Limoncelli and Christine Hogan[1] was, together with "Principles of Network and Systems Administration" by Mark Burgess have probably been the books that influenced my approach to sysadmin the most. I still have them. Between them they covered at a high level (at least back when I was sysadmin before devops and Kubernets etc) anything and everything from

- hardware, networks, monitoring, provisioning, server room locations in existing buildings, how to prepare server rooms

- and so on up to hiring and firing sysadmins, salary negotiations[2], vendor negotiations and the first book even had a whole chapter dedicated to "Being happy"

[1] There is a third author as well now, but those two were the ones that are on the cover of my book from 2005 and that I can remember

[2] Has mostly worked well after I more or less left sysadmin behind as well