Skip to Content

Blogs

  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /home/watsysgr/public_html/includes/common.inc on line 2830.
  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /home/watsysgr/public_html/includes/common.inc on line 2830.
  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /home/watsysgr/public_html/includes/common.inc on line 2830.
  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /home/watsysgr/public_html/includes/common.inc on line 2830.
  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /home/watsysgr/public_html/includes/common.inc on line 2830.
  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /home/watsysgr/public_html/includes/common.inc on line 2830.

New Year - New Logo!

Thinking about things like logos and marketing (shudder) isn't really something geeks are good at or apt to spend a lot of time. We're generally too focussed on how things work. Once something is working, THEN we'll get to fixing up how it looks. WATSYS is no different.

WATSYS has grown exponentially in the last 12 months. Despite the dreaded "global recession" we've almost doubled our client load, tripled our projects, and increased revenues dramatically. I attribute this largely to the fact that small business owners are re-evaluating what they are doing with their money and are coming to the decision that paying exorbitant licensing fees to large companies for their products or their support doesn't really make sense any more. Open Source products and solutions have matured exponentially and we are seeing it in use in places where it never went before. I received an Open Office document from my town hall yesterday, for example.

I'm digressing a bit - this post isn't really about Open Source penetration; it's about reaching the cosmetic milestone of WATSYS. Now that we're working really well, it's time to spend a little time on looking good.

Our first step was to contract our sister company KLM Interior Concepts to create a new logo for WATSYS. It's on the site now and I am really liking it. It has a nice savvy web 2.0 look to it (I know, I know, the term "web 2.0" is so dead) and the incorporation of the Canadian Maple Leaf really makes me proud. It also adds a nice splash of colour to catch your eye, but that's just gravy.

While I am excited about the new logo, I am now faced with the drudgery of searching out every place on the Internet and in our marketing materials where we have used the old logo and replacing it. This is going to be a long process and I'm sure I will miss some spots, but I am going to try!

In closing, I would like to thank all our clients. It takes a lot of trust to put your entire IT infrastructure into another company's hands and I really appreciate you taking that leap of faith with us.

Now. Onward to old-logo-hunting...

Putting the Blackberry Before the Android

OK, silly title, but it was all I was able to come up with on Christmas Eve morning. The point I was trying to capture is that I have recently come to the realization that the almost decade of PDA and Smartphone use which I have just lived through has probably actually hurt my productivity. I have recently devolved to a regular old cell phone and have magically freed up a ton of time in my day.

I am an IT professional and an entrepreneur. I run my own IT consulting business and have done so for several years. I have always considered myself to be the textbook user case for a Smartphone because I am a geek and I am self-employed. In fact, in the early days, we were pretty much the only people with Smartphones because we honestly were the only people who were able to justify the expense. These days, people of all ages and all walks of life have Smartphones and it's fairly obvious to me that can be attributed to the fact that these things have become entertainment devices rather than mere work tools. In doing so, they've become less conducive to productivity so I've dropped mine entirely. A Smartphone adds to productivity in the same way that a television does. In other words - not at all.

While I liked the fancy schmancy devices and UIs, I found that because I was constantly 'on' and the thing was always buzzing (I get about 200 emails a day never mind Facebook stuff, Tweets, and IM conversations), I was constantly distracted. Even when I put it on silent and threw it into my briefcase for a meeting, I would rush right back to it after the meeting to see what I had missed rather than reviewing the meeting notes and making action items. It became such a distraction that I would go through entire afternoons or evenings with people (socially or otherwise) and come away with almost no memory of what we talked about or what we did. I became, as the say, unavailable.

So, like a good IT pro, I sat down to purposely figure out if I could live without a Smartphone. After going through all the apps and functions on my phone, it turned out that the list of things I actually used was very small.

1. I needed to have availability to email 24/7.
2. I needed to have contacts with phone numbers and email addresses available 24/7.
3. I needed good battery life.
4. I wanted to Facebook and Twitter.
5. I wanted to be able to IM anyone.

That's it. I didn't need (or want) 95% of the apps on my device. I did not see that coming.

I then purchased a regular old LG 8100 flip phone. I bought an SMS messaging package for $10 a month, and a WAP data package for another $10 a month, and have never looked back.

I have been using IMAP email from Fastmail,fm for year. Fastmail is really, really, really serious about email and they have tons of features. One of the features they have which I had never made use of before is a full-blown IMAP WAP interface. I can retrieve email from any of the 30 or so IMAP folders in my account as well as compose and other general things like reply and forward.

Both Facebook and Twitter fully support two-way SMS. In fact, the whole reason Twitter only accepts 140 characters is because waaaay back in 2006 when Twitter came to life, it was solely an SMS gig. You updated your status and receive other's Tweets solely through SMS. Over the past year, Facebook has become consumed with Twitter envy so they have recently introduced SMS support as well. I can set my status, receive other's statuses and reply to comments all through SMS.

Anyone who has ever owned a regular cell phone and then switched to a Smartphone of any ilk has noticed that the Smartphone battery life is pretty abysmal. The Blackberry is the best of breed for battery life, but it still has trouble lasting 48 hours when used. Conversely, since a regular old cell phone is not constantly screaming out to the Internet for updates and emails, battery life is great. I can get almost four days out of my cell phone if I need to and since I have two batteries, that's a week. Can't argue with that.

Lastly, since every phone on the planet (I think) has the ability to send and receive SMS messages, that took the last item off the table. Rather than running GTalk, Windows Live and Skype just to be sure everyone I knew would be able to get hold of me, I just went to the great equalizer: SMS. Everyone can send and receive SMS messages regardless of their carrier, their handset or their apps.

So, strangely enough, by dropping one of the mostly highly marketed 'productivity' devices on the planet, I am actually more productive. I'm not saying that I will never need or want a Smartphone again, but I can say that my friends, family, and my clients all appreciate the fact that I am actually present and attentive when we're talking.

Oh, and I appreciate that my cell phone bill has dropped from $200 a month to $40 with zero needed or wanted loss of functionality.

The Insidious Power of Cron

In an incredibly rare turn of events, two servers that I manage for a client have had their cron daemons lock up over the past 24 hours. That bears it's own investigation, but that's for another post. In this post I want to share some of the ramifications of this problem.

For the unitiated, cron is a daemon (meaning service for you Windows folk) that is used to schedule tasks. In true Linux form, tasks are stored as straight text in files called crontabs. Each user on a Linux system can have a crontab file. Every minute of every day, the cron daemon reads every crontab on the system and attempts to execute any commands that are listed to be done at that time.

I say 'attempt' because cron jobs are executed as the user who owns the crontab file containing the task so proper file system permissions are applied which may foil an execution. But I digress...

In a typical Linux server, cron is used extensively to automate routine maintenance tasks and it's very rare to see a machine that has no tasks at all cronned. On the server in question, cron was used to perform the following at least daily and in some cases, many times per day:

  • monitor the health of the RAID array
  • keep the server's time in sync
  • perform unattended backups of several remote servers
  • monitoring the load on the server
  • monitor the disk space of all the partitions on the server

I was sent to look at the server because one of the disk partitions had filled up and no alert was sent. Through log diving, I was able to ascertain that the reason no email alerts were sent is because the cron job that checks the disk space did not fire. After manually running the script to ensure the script was sound, I then restarted the cron daemon. Everything then returned to normal.

That's a nice ending, but stop for a second and think about what was not happening on that server for at least a day and perhaps longer. No backups of the other remote servers in the cluster were occurring. The server's time was potentially out of whack (not a huge deal in this case, but can be in some cases). The server's load was not being monitored so proactive action would not have been possible had the server gone down. The RAID could have died and the disk partitions could have filled up. These are all Bad Things (tm) and although we had put very careful measures in place to notify us of impending Bad Things (tm), there was still a single point of failure that I had not considered: the cron daemon itself. Due to the failure of the cron daemon this server was basically running down the rails with no brakes. Anything could have happened and we would have had no clue until it was all over.

So now the challenge is to figure out some way to monitor the cron daemon without using cron. Never a dull moment.