Last week, I pulled the plug on logstripper. Today, I’m announcing my plans of bringing it back as a new service.
Update on June 4, 2014: It’s coming back!
As of today, logstripper is no more. With this post, I’d like to explain why I have decided to pull the plug on it, and what you can do if you were still using it.
This post may seem like it should be blatantly obvious, but in the last month alone, I’ve heard of numerous people using screen and/or cron to keep daemons alive. Worse, there’s even semi-official guides out there that still recommend it, even in this day and age. Now, don’t get me wrong, screen is absolutely awesome (though I prefer the newer tmux) for what it’s meant to do, such as multiplexing terminals and providing window management of those terminals.
How to restore stable WiFi on the Broadcom Corporation BCM4331 wireless chip after upgrading from Ubuntu 13.04 (Raring) to 13.10 (Saucy Salamander).
About a week ago, we at TravelBird had this bizarre problem with nginx workers segfaulting on TLS connections from Safari and curl, but not Firefox or Chrome. Nginx logs would state the worker process
exited on signal 11and
dmesgwould show the feared
nginx: segfault at 8 ip 000000000042a08d sp 00007fffe5eebca0 error 4 in nginx[400000+b9000]
It’s been a few months since my last post and a lot has happened during that time. One of the biggest has been that of leaving my old job at a&m impact and instead accepting a position at TravelBird, a relatively young startup in Amsterdam (our capital city).