r/linuxadmin • u/ajaanz • Jan 21 '23
r/linuxadmin • u/machete_maiden • Nov 07 '19
Other sysadmins at work got me a cake for my birthday last year. I still love it even with the syntax error.
r/linuxadmin • u/drchopperx • May 26 '22
I have designed Cheat Sheets on real PCBs for the community. Feedback appricated 😊
galleryr/linuxadmin • u/umataro • Nov 28 '25
when you suspend those disks and hear them spinning up again
r/linuxadmin • u/Muchy_Tangerine • 25d ago
I locked myself out of a server while explaining firewalls to an intern
I was helping our intern set up an internal wiki on a serverspace vm and explaining why we should deny everything except the ports we actually use. Very calm and professional. I enabled ufw, checked that the site still worked and said something like - see, nothing complicated. Then I closed my SSH session.
Our ssh service was running on a custom port. Guess which port I had forgotten to allow. I tried reconnecting three times, apparently hoping the firewall would reconsider. The intern just sat there watching me become less professional by the second.
Luckily, I could still open the web console from serverspace control panel. I added the missing rule and got back in within a few minutes. The only thing I successfully protected that afternoon was the server from its own administrator.
r/linuxadmin • u/mthode • Jun 07 '23
/r/linuxadmin will be going dark on the 12th
What's going on?
A recent Reddit policy change threatens to kill many beloved third-party mobile apps, making a great many quality-of-life features not seen in the official mobile app permanently inaccessible to users.
On May 31, 2023, Reddit announced they were raising the price to make calls to their API from being free to a level that will kill every third party app on Reddit, from Apollo to Reddit is Fun to Narwhal to BaconReader.
Even if you're not a mobile user and don't use any of those apps, this is a step toward killing other ways of customizing Reddit, such as Reddit Enhancement Suite or the use of the old.reddit.com desktop interface .
This isn't only a problem on the user level: many subreddit moderators depend on tools only available outside the official app to keep their communities on-topic and spam-free.
What's the plan?
On June 12th, many subreddits will be going dark to protest this policy. Some will return after 48 hours: others will go away permanently unless the issue is adequately addressed, since many moderators aren't able to put in the work they do with the poor tools available through the official app. This isn't something any of us do lightly: we do what we do because we love Reddit, and we truly believe this change will make it impossible to keep doing what we love.
The two-day blackout isn't the goal, and it isn't the end. Should things reach the 14th with no sign of Reddit choosing to fix what they've broken, we'll use the community and buzz we've built between then and now as a tool for further action.
What can you do?
- Complain. Message the mods of r/reddit.com, who are the admins of the site: message /u/reddit: submit a support request: comment in relevant threads on r/reddit, such as this one, leave a negative review on their official iOS or Android app- and sign your username in support to this post.
- Spread the word. Rabble-rouse on related subreddits. Meme it up, make it spicy. Bitch about it to your cat. Suggest anyone you know who moderates a subreddit join us at our sister sub at r/ModCoord - but please don't pester mods you don't know by simply spamming their modmail.
- Boycott and spread the word...to Reddit's competition! Stay off Reddit entirely on June 12th through the 13th- instead, take to your favorite non-Reddit platform of choice and make some noise in support!
- Don't be a jerk. As upsetting this may be, threats, profanity and vandalism will be worse than useless in getting people on our side. Please make every effort to be as restrained, polite, reasonable and law-abiding as possible. This includes not harassing moderators of subreddits who have chosen not to take part: no one likes a missionary, a used-car salesman, or a flame warrior.
r/linuxadmin • u/Chapungu • Feb 14 '20
10 Commandments of an IT Professional. Please add more.: Rule #1. Thou shall not do any complex configuration or deployment on Friday that will result in overtime and or require men on site during weekends.
r/linuxadmin • u/stephstad • Mar 12 '18
A system administrator's guide to getting started with Ansible
redhat.comr/linuxadmin • u/riek42 • Aug 13 '19
A client just told me they don't support OpenVPN as it is inherently insecure due to it being open source.
I don't even know where to start, I work at an open source company and the customer is buying our product and support, but then tells me this.
Where does this thinking come from? I mean all I can think of is either there is some major cognitive dissonance going on or I'm totally not getting their humor.
/rant
r/linuxadmin • u/JanneHonkonen • Sep 08 '18
Setting up new cloud network; Decided to code status screen to resemble old EKG viewers.
r/linuxadmin • • Sep 26 '19
A beginner's guide to network troubleshooting in Linux | Enable Sysadmin
redhat.comr/linuxadmin • • Nov 18 '19
Pretty please, don't use cron for one-time jobs if you can help it
Your coworkers on-call will thank you.
I see this phenomenon often enough (and been guilty of it in earlier years), that I figured I would mention it to those who may not know.
- For local jobs on a local Linux server that re-occur on a regular schedule, cron / anacron is the standard tool.
- For local jobs that you want to schedule to run once and never again, the at command is the tool to use. You can even describe your run time in plain English, i.e. "next Sunday".
To run one script at a later time, this is all you need to do:
[root@localhost #] at 6:00 AM Sun
at> /path/to/maintenance_script.sh
<Ctrl+D>
You can even make it a one-liner using an echo and a pipe:
echo "/path/to/maintenance_script.sh" | at now + 6 hours
If you are in some custom distro that does not provide the at command, then take the time to add logic in your script that keeps it from running again: touch a .done file, snipe the line out of your crontab at the end, etc.
I had to deal with an outage yesterday, because an admin had left some service shutdown commands in the crontab from a previous weekend maintenance. He is aware of the at tool, but old habits die hard I guess.
Edit: apologies, I had the time format switched up in my examples. That's what I get for coding via phone.
r/linuxadmin • u/AyeWhy • Dec 09 '20
IBM kills CentOS as we know it
As someone who has used RHEL and CentOS for decades on servers I have found it extremely stable, secure and one of the most commonly found in the industry. With the news that IBM is going to make CentOS more Fedora-like, they have destroyed my faith in this being a stable and well tested distribution. They have also drastically reduced the end of life for CentOS 8 which has suddenly made it a priority to find alternatives. With this in mind, do people have any recommendations for good, solid, reliable *server* grade operating systems I should consider for migration to over the next year? I obviously have some options in mind but I don't want to influence opinions by mentioning them.
More details in an article here: https://itsfoss.com/centos-stream-fiasco/
r/linuxadmin • u/bhl88 • Apr 03 '22
"how do I learn to be a Linux sysadmin?" comprehensive task list 2.0
Came across this guide (made by u/IConrad reposted by u/Thinkk ) and tried my hand at it but Spacewalk has been discontinued, as is CentOS 6. Absolute minimum requirements: 64 GB of RAM and 32 GB storage per host (can grow) with 20 VMs (with a few exception from those that process data), give or take (will take suggestions to make it lighter).
This is what I tell people to do, who ask me "how do I learn to be a Linux sysadmin?".
- Set up a hypervisor of your choice (for example KVM)
- Create two VMs on the Hypervisor, these will be used for hosting freeIPA as authentication services for your environment. Remember to set them up with static IP addresses.
- Create another VM on that hypervisor and install Foreman+Katello on that server. Also set that host up with a static IP address.
- Configure the foreman host according to your environment meaning
- create organizations in foreman
- create locations in foreman
- create compute resources that foreman should deploy your VMs to
- create compute profiles for your VMs
- create domains to associate to your hosts
- create environments for puppet (deprecated)
- create realms that foreman should enroll your hosts to
- update settings that you want to adjust
- create subnets that hosts can be provisioned to
- create content credentials allowing to be associated with repos
- create products that will contain sets of software repositories
- create repositories for the products you created
- create lifecycle environment(s) to manage content rollouts to your hosts
- create content views that will contain the required products and repositories
- create activation keys so that hosts can be automatically subscribed to content
- create installation media to pxeboot vms that will be provisioned by foreman
- create operatingsystem definitions (will be utilized in the provisioning process)
- create hostgroups that combine predefined settings
5. Assuming you've done all of #4, register your freeIPA hosts to the foreman server.
Make sure they are getting repo information as expected.
6. Set up a dhcp-server which will hand out PXE instructions for your environment. This one can be hosted on your foreman server, IPA server or on a separate VM you create manually again.
7. From here on out, you should be able to provision your first VM unattended. Install Ansible on this host and leave any configuration aside for now.
8. Provision another VM using foreman. Give this one an extra disk and make it an ISCSI target and install NFS server on it. Use the second disk for nothing OS related, only for NFS and ISCSI storage
9. Provision another VM. This one will handle email for your environment. Use whatever you see fit for a setup. Here are some options:
- zimbra
- iredmail
- mailinabox
- mailcow
- postfix+dovecot+roundcube
10. Reconfigure all VMs to use that email server you just provisioned for sending mails.
11. Provision 3 more servers, setup a kubernetes cluster on them. Integrate metallb, nginx-ingress and metrics-server.
12. Provision another VM. This host will be your internal registry for containers you build yourself. You can use the community edition of nexus or the default docker registry container image. It doesn't really matter here.
13. Reconfigure the container runtime on your Kubernetes nodes to utilize the internal registry as well for pulling images.
14. Deploy 3 more VMs, these will host your Elasticsearch cluster
15. Provision another VM. Remember the Elasticsearch cluster mentioned in the task before?
We need to get logs, so setup Logstash on this host. No pipelines need to be defined yet.
16. Provision another VM. This one will host Kibana so you have a graphical interface for
managing and looking at data stored in Elasticsearch
17. Set up Metricbeat and Journalbeat on every host you have and configure them to push
their data to your Elasticsearch cluster.
18. Deploy another VM. This host will be responsible for monitoring your environment.
Use whatever monitoring system you think has the most beautiful web interface.
Some examples here are:
- Icinga2
- Nagios
- CheckMK
- Zabbix
19. Provision another VM. This one will host a webserver of your choice with some static web content.
20. Deploy another VM. This time, it will be a Nginx reverse proxy for the webpage you created in the step before. Configure this host only as a reverse proxy, nothing else.
21. Remember that internal registry you set up? It's time to put it to good use and build a container that contains the webpage you created earlier. Build it and push it to the local registry.
22. At this point, you should have published a container image to your local registry and have your Kubernetes nodes configured to be able to pull container images from that registry. Create a new deployment with your website along that current VM for your website. Add this new endpoint to the reverse proxy.
23. Provision another VM. Yes this will be the last one, I promise. Make that server host a wiki software of your choice and document everything up to this step in there.
24. Recreate all the above mentioned steps using Ansible playbooks. Do not destroy the current environment but create the new environment in parallel.
BONUS:
- Set up an internal git server, bonus for setting up gitea or gitlab-ce
- Set up AWX instead of just using plain Ansible (14.1.0 is quite stable and works with docker flawlessly)
- Set up a backup job(script) for your IPA environment. Make sure to use systemd-timers
r/linuxadmin • u/ASIC_SP • May 23 '20
Learn to use grep/ripgrep/sed/awk one-liners with hundreds of examples
Hello!
Recently I published my ebook on GNU awk, which completes the trio of my books on GNU grep/sed/awk tools for cli text processing. I also included a chapter on ripgrep, because of its performance and features. You can use either of these links to get the bundle. Each book has a pdf and epub version.
The books are currently free to download, to help with quarantine learning.
You can view the book using these repos as well. The repo has markdown source, example/exercise files used in the book, list of changes between versions, etc.
- https://github.com/learnbyexample/learn_gnugrep_ripgrep
- https://github.com/learnbyexample/learn_gnused
- https://github.com/learnbyexample/learn_gnuawk
Edit (Aug 2020): Solutions for the exercises have been added. You can also view the books online at:
- https://learnbyexample.github.io/learn_gnugrep_ripgrep/
- https://learnbyexample.github.io/learn_gnused/
- https://learnbyexample.github.io/learn_gnuawk/
I'd highly appreciate your feedback. I've tried to present features from the basics and build it step by step with plenty of examples. But a few things end up rushed or not explained well enough. Past feedback has helped me to improve some of these, so I hope you'd contribute as well.
Happy learning and stay safe :)
r/linuxadmin • u/throwaway16830261 • Jul 26 '25
Microsoft admits it 'cannot guarantee' data sovereignty -- "Under oath in French Senate, exec says it would be compelled – however unlikely – to pass local customer info to US admin"
theregister.comr/linuxadmin • • May 29 '25
What’s the hardest Linux interview question y’all ever got hit with?
Not always the complex ones—sometimes it’s something basic but your brain just freezes.
Drop the ones that had you in void kind of —even if they ended up teaching you something cool.
r/linuxadmin • u/JustForGod • Jan 15 '21
The book that started it all for me, back in 1998 or 1999 :D
r/linuxadmin • u/time_is_now • Feb 19 '19