For a long time now, there have been rumours about SysAdmins, creatures who work in the shadows, avoid sunlight, enjoy Korean cuisine and are pure nerds. You aspire to join this magnificent community and you feel ready to dive into this dark, joyful, mysterious world... But you wonder: What do SysAdmins actually do? What are their responsibilities and everyday tasks?
Here you will find an attempt for slow, ongoing documentation of some essential SysAdmin tasks written by feminists. Some of us have long experience in this kind of work, while others are new to this. Together, we enjoy exploring SysAdmin work, collectively educating ourselves and making efforts to maintain our feminist infrastructures: Systerserver and Anarchaserver.
As a Sysadmin, one of the frequent activities is to reboot a server.
-That looks cool, but hey, I have a dull question! Why do we need to reboot the server? When do we know that this is something we have to do? -A server reboot could be essential because of regular maintenance activity such as software and operating system (OS) updates for security reasons. -Do we have to do these updates/upgrades manually or are they automated processes? -There are Automatic Security Updates. Administrators receive an email when this happens, so we know when to perform the reboot/shutdown. Would you like to be added to this list, so you also receive these emails? -Yes, let's do that!
Sysadmins emails should be added in /etc/aliases
# vi /etc/aliasesroot: email@example.com, firstname.lastname@example.org, email@example.com
The server sends emails for the security updates that have been installed overnight and inform the sysadmins if a reboot is necessary.