I'm a web developer/sysadmin/host (NERD TRIPLE THREAT!) and this is my attempt to write about...leaving the house. Sometimes. Like, to go backpacking. And take some pictures. And justify spending the money on all the gear WHY SO MUCH?!?
Feel free to write and complain.
A handy little cron command for Ubuntu is @reboot. For some reason I am too lazy to research properly I kept getting
[psad-status] firewall setup warning
on startup. Not hard to fix, but annoying. So creating a quick script to run
/sbin/iptables -A FORWARD -j LOG
/sbin/iptables -A INPUT -j LOG
and call it from crontab with
does the trick.
A little something to save frustration when working with rsync and public/private keys. Be sure to pass the key you'd like to use (if not using default values):
ssh -i /root/.ssh/key_file_you_want_to_use
And if you're using cPanel, you might consider using
to limit CPU usage when running something that might take a while (like rsync-ing your backups to external locations). The 1.5 parameter above checks to make sure the server load is below that value before continuing.
This mainly helps me since I will inevitably forget this and need to know where to look. Leaving these breadcrumbs around makes a certain kind of sense.
Pulling your last remaining hairs out trying to get MailChimp templates to work right? Wondering why your perfectly set design suddenly looks horrible after saving a copy? Well, MailChimp DOES THINGS IT'S OWN WAY.
Picking a template, choosing Edit Code and then hitting the Save button gives you the option to Overwrite or Save As. Save As makes a copy, but it will NOT retain all of the modifications you've made. You actually need to go to the plain Edit button (or click on the template image). This gets you into the MailChimp editor, which now has a button at the top called Rename or Replicate template.
If you want a true template copy, you need to choose Replicate. Why simply doing Save As doesn't work I have no idea.
So, if you're running into the "I have an authentication key all set why won't it work right" and you've gone through all the helpful suggestions like "make sure permissions" and "check sshd config", one last thing to check would be what you named your private key when you ran
If you named it something other than the default prompted filename, you need to use the -i switch when trying to ssh so it will know where to look. So try
ssh -i /path/to/your_clever_filename user@hostname
It seems I find something new to add each time I log in. (I mean this in the code-sense, less so in the meaningful-writing-sense. I feel this is obvious). The trick is not to overdo it with all the bells and whitles. I will try to stick to just bells. Hate whitles.
YES I SAID WHITLES.