Wine tasting review – 14 July 2012

Today is Saturday, 14 July 2012, which means it is French National Day (known as Bastille Day in many English-speaking countries). That also means that it is only appropriate to celebrate with a selection of French wines at the weekly tasting. Also, the tasting was led by Rich Haynes of Dionysus Wine Distributors, LLC, who eagerly shared his amazing depth of understanding about these wines, which greatly contributed to the experience. So without further adieu, let’s discuss today’s featured pours.

HV Bottle Shop tasting - 14 July 2012
Wines are discussed from right to left

The first wine of the day was a 2009 Sauvignon Blanc from producer Hubert Brochard in a western section of the Loire Valley. This Terroir de Silex comes from vines that are approximately 30 years old, and planted in very flint-saturated soil (that also has some limestone), which lends a strong minerality to the taste. As a Sauvignon Blanc (or, more specifically, Sancerre Blanc), it is very fruit-forward with highly floral aromas, dry, and has a bright acidity. It was very lightly golden in colour, and had virtually no legs at all. It would pair nicely with just about any seafood, but particularly a white fish such as Tilapia.

The second offering was a 2010 Chenin Blanc (Réserve de Vignerons) from the producer Cave de Saumur in the town of, none other than, Saumur. It was very light yellow–indeed, almost clear at a tilt–and, though it had no legs, left a ring of medium thickness. Residing in stainless steel barrels, it was clean, crisp, and had a vibrant acidity. The melon and honeysuckle flavours prevailed in this delicate wine, and the finish was a combination of the melon and, to me, a slight apricot taste. Overall, this was a wonderful wine, and as such, the one that I purchased today. At under $10 USD (~ €8), this is a beautiful wine that illustrates how price does not determine quality.

The third pour was a 2011 Rosé of Cabernet Franc from the same producer as the previous. The maceration process (during which the juice is left in contact with the skins) was only two days. Visually, this wine was stunning as it had a light pink centre with a virtually clear edge. It had medium, slightly viscous legs, and beautiful aromas of raspberry and strawberry. It had a very thin mouth-feel, light flavour, and great finish of strawberry, a hint of cherry, and some herbal crispness.

The fourth wine was a 2006 red blend (80% merlot / 20% Cabernet Sauvignon) from producer Château Malmaison Moulis in the Bordeaux region. It had a lovely garnet-coloured centre and ruby edge on tilt, with medium, slow-moving legs. There were very earthy aromas mixed with forest fruits, and even a slight cigar smell. Unfortunately, that earthiness didn’t come through in the flavour, which focused more on the blackberries and currants. It was quite dry, and had a heavy mouth-feel to me, but that may have been partly because of the ambient heat. I feel that this wine needed more time for the flavours to round.

The fifth tasting of the day was a 2008 second-label (younger vines) red Bordeaux blend (~60% Cabernet Sauvignon / the rest a mix of Merlot and Cabernet Franc) from Producer La Chapelle de Calon. It was a light ruby colour throughout with very low contrast between the centre and edge. It featured a smoky aroma, and taste predominantly of berries (with a hint of chocolate at the back). It was medium-bodied, but a little underwhelming.

The last offering of the day was a 2009 Syrah from producer Emmanuel Darnaud. The vineyard is located in the Crozes-Hermitage region of the Rhône Valley, which is a significantly larger region than the more prestigious Hermitage region. This particular producer uses very old-fashioned methods for making his wines (including foot-stomping, and small batches). This particular vintage had a deep red centre with a vibrant purple edge, and aromas of dark berries. The flavour very much followed the aroma of dark berry. It was very fruit-forward, with a light-to-medium mouth feel. To me, it was a little too juicy, and the finish was somewhat anticlimactic.

Cheers,
Zach

Amazon’s White Power toothbrush, or why word order is important…

Well, I was going to post a review of a new CD today, but when something jam-packed with failure (and subsequently, humour) arrives in my inbox, I simply can’t let it go to waste. This morning during my typical routine, I checked my email, and had to see what Amazon’s Deal of the Day would be today. At first, I didn’t think anything of it being a battery-powered toothbrush (and really I have no desire to own one), but Amazon’s title for the product was a bit… errrmmm… unusual:

Philips Sonicare Healthy White Power Toothbrush - Amazon Deal of the Day
Click to enlarge

The White Power toothbrush?! I’ll bet that that product doesn’t go over well in certain markets, and with particular demographics. I will also bet that Philips didn’t approve of the new description of their product, which they refer to as the HealthyWhite Rechargeable Sonic Toothbrush.

Apparently, Amazon realised their poor wording, and quickly changed the title of the product to the Philips Sonicare HealthyWhite Toothbrush:

Amazon Deal of the Day - Philips Sonicare HealthyWhite Toothbrush - corrected
Click to enlarge

but it was far too late, as many people commented on the Deal of the Day discussion today (which by the way, is Friday the 13th). My personal favourite comment is the one from DigitalBug, which can be found here. I have also excerpted it below, just in case it disappears at some point:

Posted on Jul 13, 2012 12:39:01 AM PDT
Last edited by the author 9 hours ago
DigitalBug says:

I wonder if this is a big seller in Harlem?

The “White Power” toothbrush has to be one of the all-time worst product names in history.

EDIT:
The title of the product when I wrote this was “Sonicare Healthy White Power Toothbrush”.

This seems to be an Amazon mistake. The official name of the toothbrush is the “Sonicare’s HealthyWhite Rechargeable Sonic Toothbrush”. Amazon is trying to be descriptive in calling it a power toothbrush, which is a term Sonicare does not use for this, or any other model they make. Also, Amazon added a space to “HealthyWhite” further compounding the problem and allowing the title to read “White Power”.

Hopefully it is corrected before you even read my post, but it would make an interesting poster that Bill Maher’s dentist might hang in his/her office: White Power — Good for Teeth, Bad for Society!

What have we learned today? Repeat after me, “word order is important for conveying the intended meaning.” 🙂

Cheers,
Zach

Apache access logs, error logs, and Cronolog

Apache has two main logs at the vhost level, and those are the access_log and error_log. These two logs keep track of just what you might think–visitor information for each vhost, and any errors encountered, respectively. Though Apache has a lot of built-in customisation abilities regarding these logs (including the format of each, the log location, et cetera), it does not have much in the way of organising them. Before delving into the solution to that problem, let’s look at some of the customisation that can be done for each of these logs within Apache itself. For the access_log, one can choose what level of information is logged by setting up a LogFormat directive such as the one below:


LogFormat "%h %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined

What does this directive actually do? The first portion–LogFormat–is the Apache directive itself, and as such, instructs Apache that all of the options thereafter will be related to your desired formatting of its logs. Each element within the quotation marks instructs Apache to log certain elements, and here’s what each element listed above is:

  • %h – The host of the remote connection (the IP address of the visitor)
  • %u – The user that is trying to connect to a resource protected by HTTP Authentication (like Apache BasicAuth)
  • %t – The timestamp of the activity (in the default format of DD/MMM/YYYY:HH:MM:SS GMT+/- offset)
  • %r – The request line, which contains the method (i.e. GET / POST), the resource requested, and the protocol used
  • %>s – The HTTP status code that the user received for that resource (200 OK, 404 Not Found, et cetera)
  • %b – The size (in bytes) of the requested resource
  • %{Referer}i – The site from which the user came to request this resource
  • %{User-agent}i – Information about the user’s browser (e.g. Firefox, Chromium) and their OS (e.g. Windows 7, Linux, Android)

The last portion of the LogFormat directive is the nickname, which in this case is “combined.” That nickname can be referenced in conjunction with the CustomLog directive in each vhost in order to call the particular format. For instance, if I had a particular vhost for which I wanted this LogFormat, I would reference it with a line like:


CustomLog /var/www/domains/somedomain.com/host/logs/access_log combined

Where the first field (CustomLog) is the directive itself, the second field is the location of the log, and the third field is the nickname of the LogFormat that we previously defined.

One thing that Apache doesn’t have built in regarding logging, though, is organisation of the logs based on a time frame or similar. There is a programme that, even though it hasn’t been updated for some time now, works really well in achieving this goal. That programme is Cronolog. Many distributions might not have it in their repositories, and in those cases, one needs to compile it from source. However, Gentoo does offer it via Portage. Once you have it installed (either from your distribution’s package manager or compiled from source), configuring Cronolog is quite simple and straightforward. All that needs to be done is a slight change of syntax in the CustomLog directive from above. Here’s an example:


CustomLog "|/usr/sbin/cronolog /var/www/domains/somedomain.com/host/logs/%Y/%m/access_log" combined

Let’s break down that syntactical change piece by piece. The first field remains the same, as it is the Apache directive of CustomLog itself. The second field is now encased in quotation marks, and features the pipe to start. The pipe is essentially taking the logged information that Apache is gathering and passes it to the programme mentioned thereafter; namely, Cronolog (which is, by default, located at /usr/sbin/cronolog). Thereafter, the same log location is called, except for one key difference: the %Y and %m folders are now in the path. As you may have guessed, Cronolog creates a folder for the year (%Y), and subfolders for each month (%m) within it. When either of those stamps change (in this case, each month), new folders / subfolders are created, and Cronolog instructs Apache to log to the access_log file within the appropriate subfolder.

Pretty neat, and easy to set up eh? I hope that you feel empowered to use Cronolog within your Apache environment.

Cheers,
Zach