{"id":2,"date":"2016-07-12T20:46:12","date_gmt":"2016-07-12T20:46:12","guid":{"rendered":"https:\/\/fs.wp.odu.edu\/sobrien\/?page_id=2"},"modified":"2024-11-26T06:27:41","modified_gmt":"2024-11-26T10:27:41","slug":"sample-page","status":"publish","type":"page","link":"https:\/\/fs.wp.odu.edu\/sobrien\/sample-page\/","title":{"rendered":"About Sean"},"content":{"rendered":"<p>I&#8217;ve been a Systems Administrator for going two decades\u00a0now, and I&#8217;ve learned a thing or two about how dumb I am. This blog is mostly errata that I think might help my users: if I googled it, they might eventually too, and so I want to be able to point them to something that will work in our environment.<\/p>\n<p>Having said that, stuff that I blog about here should work for you too. If you have questions or problems, just ask!<\/p>\n<p>In my computer career I&#8217;ve worked at <a href=\"https:\/\/www.cs.jhu.edu\/\" target=\"_blank\" rel=\"noopener\">Johns Hopkins University Computer Science<\/a>, the <a href=\"http:\/\/www.prattlibrary.org\/\" target=\"_blank\" rel=\"noopener\">Enoch Pratt Free Library<\/a>, the <a href=\"http:\/\/health.hawaii.gov\/cab\/\" target=\"_blank\" rel=\"noopener\">State of Hawaii Clean Air Branch<\/a> &amp; various <a href=\"https:\/\/www.nasa.gov\/\" target=\"_blank\" rel=\"noopener\">NASA<\/a> contracting firms.<\/p>\n<p>I&#8217;m currently the senior UNIX &amp; Mac SysAdmin at the <a href=\"http:\/\/odu.edu\">Old Dominion University<\/a> <a href=\"http:\/\/www.ccpo.odu.edu\/\">Center for Coastal Physical Oceanography<\/a>. My scientists study the effects of climate change on sea level rise, among other things.<\/p>\n<p>I have the best systems job in the world, because all of my users are power users. You should be so lucky. If you find a job like mine,\u00a0<em>take it!<\/em> Added bonus: working at my alma mater.<\/p>\n<p>A few points of troubleshooting &amp; meta advice for junior systems administrators in general:<\/p>\n<ul>\n<li><strong>Document everything you do.<\/strong> <em>There are no exceptions.<\/em> You <em>will<\/em> forget the specifics of your localized configurations. Documentation is non-negotiable. You &amp; your team require reliable documentation.<\/li>\n<li>There are no stupid questions. If someone asks you a technical question that you think should be obvious to them, don&#8217;t insult them, don&#8217;t tell them to RTFM, instead just educate them (politely). They&#8217;re just <code>grep<\/code>ping your brain. It&#8217;s a compliment.<\/li>\n<li><em><strong>Keep the machines up to date. Set them to apply security patches (and preferably all patches) automatically.<\/strong><\/em><\/li>\n<li>It&#8217;s probably just not in your <code>$PATH.<\/code><\/li>\n<li>If it&#8217;s in your <code>$PATH<\/code>, it&#8217;s probably a permissions error.<\/li>\n<li>If it isn&#8217;t a permissions error, and you tried it with an absolute path, make sure you&#8217;re executing it as the proper user.<\/li>\n<li>Don&#8217;t <code>su -<\/code>. Just don&#8217;t. <code>sudo<\/code> instead.<\/li>\n<li>Since all senior admins are going to ignore that last one, at least don&#8217;t enable color in your root <code>.tcshrc<\/code> or <code>.bashrc<\/code> or whatever. Then remember: <em>If\u00a0it&#8217;s white, make sure it&#8217;s right.\u00a0<\/em>Or, if you use a terminal with black text and a white background,\u00a0<em>If it&#8217;s black, you can&#8217;t go back.<\/em><\/li>\n<li>There will always be someone smarter &amp; more experienced than you. Those people are a resource. Use that resource if you can. Likewise, you may know more than the person next to you. Be their resource.<\/li>\n<li>You can fix it. \u00a0Step number one is <em>don&#8217;t panic.<\/em> If you can&#8217;t fix it, maybe somebody will help you (see above). If nobody will help you, then maybe you could try another solution. If you can&#8217;t try another solution, you probably have another computer. In any case,\u00a0you <em>can<\/em> solve\u00a0the problem.<\/li>\n<li><strong>If you&#8217;re in systems, you need to work on your customer service. We all do.<\/strong><\/li>\n<li>Always ask the user what she&#8217;s actually trying to do. Sometimes we all get too annoyed with details. There may be a much simpler, faster way to do something that your users don&#8217;t know about, or even services you have that are poorly advertised.<\/li>\n<li>Begin to accept that you aren&#8217;t just root, you&#8217;re also a user. They are you &amp; you are them.<\/li>\n<li>Never argue or evangelize about your chosen <code>$EDITOR<\/code> or your beloved <code>$SHELL<\/code>. Give the user the tools he wants to do his job. And smile about it.<\/li>\n<li>Everyone has something to teach you. Therefore everyone is your teacher. Respect them. Soft skills are as valuable as technical ones.<\/li>\n<li>Disks that are full will cause you problems. They will be weird problems. If weird shit happens, <code>$ df -h<\/code>.<\/li>\n<li>Make sure you <code>lsof -i<\/code> to see what the system is opening to the world, then run <code>nmap<\/code> on your systems from the outside.<\/li>\n<li>If you don&#8217;t know how to harden a linux machine, try <a href=\"http:\/\/bastille-linux.sourceforge.net\/\" target=\"_blank\" rel=\"noopener\">bastille<\/a>.<\/li>\n<li><a href=\"http:\/\/denyhosts.sourceforge.net\/\" target=\"_blank\" rel=\"noopener\"><code>denyhosts<\/code><\/a>. For days.<\/li>\n<li>Every Single Time:\n<ul>\n<li><code>whoami<code><\/code><\/code><\/li>\n<li><code>sudo cp aFileImAboutToEdit aFileImAboutToEdit.date<code><\/code><\/code><\/li>\n<\/ul>\n<\/li>\n<li><strong>If you call yourself a systems administrator, you better make sure you can restore from your backups.<\/strong><\/li>\n<li>You should hold yourself to the highest ethical standards. Consider posting the <a href=\"https:\/\/lopsa.org\/CodeOfEthics\" target=\"_blank\" rel=\"noopener\">Systems Administrator&#8217;s Code of Ethics<\/a> by your door, and encourage your users to hold you to it.<\/li>\n<li>Never take a service down without notifying your users.<\/li>\n<li>Remember that users come to rely upon your services. If you offer a service, then take it away, they&#8217;ll become understandably upset. So don&#8217;t. Or, if you have to, offer an upgraded version, and understand that change is a process.<\/li>\n<li><strong>Your job is to empower excellence.<\/strong> That is your goal. You maintain the tools your users need to succeed. Satisfaction guaranteed is the <em>minimum<\/em> level of service you should shoot for.<\/li>\n<li>Never change anything on Friday after noon.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve been a Systems Administrator for going two decades\u00a0now, and I&#8217;ve learned a thing or two about how dumb I am. This blog is mostly errata that I think might help my users: if I googled it, they might eventually too, and so I want to be able to point them to something that will [&hellip;]<\/p>\n","protected":false},"author":3412,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"open","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/pages\/2"}],"collection":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/users\/3412"}],"replies":[{"embeddable":true,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/comments?post=2"}],"version-history":[{"count":5,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/pages\/2\/revisions"}],"predecessor-version":[{"id":142,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/pages\/2\/revisions\/142"}],"wp:attachment":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/media?parent=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}