Aaron Parecki

Update:

We just got caller ID at my house. One of my roommates doesn't have a cell phone, so eventually everyone else stopped answering the house phone because it was always for him. But then he would come home and not know who called. Now of course, caller ID solves this problem by logging who called on the phone handset, but being me, that is not enough!

Ok, so I wasted about 3 hours on this, and have only sort of found a solution. I have a PHP script which is going to be running 24/7 checking a message queue and then interacting with a database when a message is received. It was mostly working, until it sat there for a day and I tried to use it the next day. The PHP script had quit, with the error "MySQL server has gone away." I figured there must be some sort of time limit that the mysql server will keep an idle connection alive. I couldn't find it, but luckily I was talking to nick, and he did! He found this blog entry. So I changed the my.cnf file to set the timeout to one week:

I had a thought of using a RAM disk as a message queue for a messaging application I am working on, as opposed to creating a table in a database, or using a regular flat text file. Every time I need a message to be sent, I'll add a text file on the RAM disk, then the sending process can scan for files. All of this is happening in RAM, so it won't be thrashing the disk!

This has happened once before. One day, photoshop decides it doesn't want to start up. During the loading screen, it just stops on "Reading text global resources."

One of my servers has a nasty habit of not reloading the firewall rules when it boots up. Iptables starts up just fine, but doing iptables-save shows that there are no rules listed. The weird part is that on all my other servers, I never had to do anything special to get it to remember the rules on restart.