Wicked simple issue – took a line from /etc/crontab and put in to the root’s crontab (crontab -u root -e) and it was no longer running. Getting this error:
/bin/sh: root: command not found
Simple fix – needed to remove the ‘root’ from the line that I’d moved from one file to the other, as the root’s crontab did not need the ‘root’ user mentioned.
A good blog post with some cron/crontab basics: http://rhosted.blogspot.com/2010/04/crontab-error-binsh-root-command-not.html
Over the past year, I have become more and more entangled in the Linux world, becoming a Linux System Administrator as my primary job duty. Though I have had plenty of Linux experience and exposure, and attend (when I get time) meetings of the Boston Linux Users’ Group (blu.org), I generally approach Linux from a Server angle and only play with it as a desktop, while maintaining a Mac or Windows PC for my primary ‘working’ OS. This has changed a bit over time and I find myself using Fedora 25 on both my Thinkpad T460s (a post for a different time) and now on my office Dell Precision 3620. Going to see how long I can keep it up in this windows-centric office. Desktops and laptops here have been primarily Windows, but we do run some CentOS 6.x and 5.x desktops on the ‘important computers’ side. Side-note – the Precision 3620 runs CentOS7 and all the apps listed above just fine as well.
Articles and posts such as this one, where people are switching from Mac to Linux OS, are encouraging and the more people use this ecosystem, the more things will be developed for the desktop OS. It was nice, also, to have someone as famous as Cory Doctrow talk about his switch over to a Linux OS back in January 2016.
We had an issue here recently where only an older version of OpenConnect would work for a CentOS 6.8 machine. Installation went fine, but the user was getting yum update messages for this package. In order to exclude, just make an entry in to your /etc/yum.conf directory. Instructions can be found right on Redhat’s website: https://access.redhat.com/solutions/10185
This was a great resource when I was setting up a local server here at the office and troubleshooting why the root@e-mail came from the wrong originating domain. Very concise tutorial.