Live data from Hacker News

New Year's Resolutions for SysAdmins

usenix.org

1–10 of 46 posts

Re: New Year's Resolutions for SysAdmins

#6
post #3

Excuse my ignorance, but what's wrong with nslookup and ifconfig?

They're a bit dated. Use dig instead of nslookup, and right from the ifconfig man page:

NOTE

This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link.

Re: New Year's Resolutions for SysAdmins

#7
post #2

I'd also recommend any sysadmin to start looking into an automation framework like Chef, Puppet, Ansible, or any other of the myriad options.

Absolutely. Automate relentlessly. As a bonus, the recipes/playbooks you develop serve as documentation for how things are configured.

Re: New Year's Resolutions for SysAdmins

#8
post #7
post #2

I'd also recommend any sysadmin to start looking into an automation framework like Chef, Puppet, Ansible, or any other of the myriad options.

Absolutely. Automate relentlessly. As a bonus, the recipes/playbooks you develop serve as documentation for how things are configured.

Yeah that's a huge bonus that I didn't anticipate before beginning. My cookbooks are essentially dynamic documentation that morph with my changes in system requirements.

Re: New Year's Resolutions for SysAdmins

#9
post #2

I'd also recommend any sysadmin to start looking into an automation framework like Chef, Puppet, Ansible, or any other of the myriad options.

Automation is a fine thing except for some of this damn "enterprise software" that not only doesn't automate real well[1], but actually cannot be installed on VMWare[2] or even go to a hot swap machine[3]. Sysadmins always love government required software and stuff bought before we got there.

1) luckily backup seem to be reasonably automation friendly

2) "We do not support virtualization of any kind"

3) tied to hardware on one machine - f'n brilliant.

Post reply on HN