lathiat's blog

• Round-up of options for disabl...
• Watch out for hostname changes...
• Checking ldirectord is alive...
• At Linux.conf.au 2009 and star...
• Avahi is now 3 years old......
• Macbook broken. again....

read what lathiat reads

• Apple Removes Download Options...
• Holland Backup Manager...
• We Saved a Spot for You!...
• This is What Happens When You ...
• Why Is There a Dolphin in My D...
• I Knew I Wanted a Red Car...

lathiat's tweets

• lathiat: @tim0liver doesn't want to show up on iphone, don't understand why. is there any documentation on email requirements?... on 10/11/2012


• lathiat: @Tim0liver Can you send me the "Add to passbook" badge? https://t.co/LkYbf6TJ... on 10/11/2012


• lathiat: @Tim0liver Hrmm.. Mail.app detects the Pass attached.. but iPhone Mail is not.... on 10/10/2012

• about
• blog
• twitter
• reader
• car
• tracker
• talks
• contact
•  
•  
•  
•  
•  
• email
• facebook
• twitter
• msn
• skype
• jabber

lathiat's google reader stream

Apple Removes Download Options From Quicktime Trailers Website
Posted 8 hours, 33 minutes ago via MacRumors: Mac News and Rumors - Front Page

It appears that Apple has begun quietly phasing out its trailer download options from the trailers.apple.com website, effectively eliminating 1080p trailer availability.

Previously, the site gave users the ability to stream trailers in 480p or 720p, along with providing download options for 480p, 720p, and 1080p. Trailers uploaded to the site after an approximate date of May 22 no longer have any download options and can only be streamed in-browser at 480p or 720p.

Go to article

Holland Backup Manager
Posted 8 hours, 35 minutes ago via Planet MySQL

Part 1 - Installing Holland Backup Manager

[vagrant@node1 holland-master]$ sudo python ./setup.py install
running install
running bdist_egg
running egg_info
creating holland.egg-info
writing holland.egg-info/PKG-INFO
...
Installing holland script to /usr/bin

Installed /usr/lib/python2.6/site-packages/holland-1.0.8-py2.6.egg
Processing dependencies for holland==1.0.8
Finished processing dependencies for holland==1.0.8

[vagrant@node1 config]$ holland --version
Holland Backup v1.0.8
Copyright (c) 2008-2010 Rackspace US, Inc.
More info available at http://hollandbackup.org

[vagrant@node1 plugins]$ ls -w1
ACTIVE
holland.backup.example
holland.backup.mysqldump
holland.backup.mysqlhotcopy
holland.backup.mysql_lvm
holland.backup.pgdump
holland.backup.random
holland.backup.sqlite
holland.backup.xtrabackup
holland.lib.common
holland.lib.lvm
holland.lib.mysql
README

[vagrant@node1]$ cd holland.lib.common/
[vagrant@node1 holland.lib.common]$ sudo python setup.py install
running install
...
Adding holland.lib.common 1.0.8dev to easy-install.pth file

Installed /usr/lib/python2.6/site-packages/holland.lib.common-1.0.8dev-py2.6.egg
Processing dependencies for holland.lib.common==1.0.8dev
Finished processing dependencies for holland.lib.common==1.0.8dev

[vagrant@node1 holland.lib.common]$ cd ../holland.lib.mysql/
[vagrant@node1 holland.lib.mysql]$ sudo python setup.py install
running install
...
Adding holland.lib.mysql 1.0.8dev to easy-install.pth file

Installed /usr/lib/python2.6/site-packages/holland.lib.mysql-1.0.8dev-py2.6.egg
Processing dependencies for holland.lib.mysql==1.0.8dev
Finished processing dependencies for holland.lib.mysql==1.0.8dev

Go to article

We Saved a Spot for You!
Posted 8 hours, 42 minutes ago via FAIL Blog

Go to article

This is What Happens When You Shower at Your Girlfriend's Place
Posted 9 hours, 12 minutes ago via FAIL Blog

Go to article

Why Is There a Dolphin in My Drink?
Posted 9 hours, 42 minutes ago via FAIL Blog

Go to article

I Knew I Wanted a Red Car
Posted 9 hours, 57 minutes ago via FAIL Blog

Go to article

Don't Ask Why, Just Accept It
Posted 10 hours, 12 minutes ago via FAIL Blog

Go to article

RPi control your server PSU over the Internet
Posted 10 hours, 41 minutes ago via Hack a Day

Here’s an interesting use of a Raspberry Pi to control the PSU on a server. [Martin Peres] is going to be away for a few months and still wants access to his PC. This isn’t really all that tough… it’s what SSH is made for. But he also wants lower-level access to the hardware. Specifically he needs to control and get feedback on what the PSU is doing, and even wanted to have access to the serial console without having to go through the computer’s NIC.

The image above shows one part of his solution. This is a custom Ethernet port that connects to his Rasberry Pi header breakout board. Inside the computer the jack is wired to the motherboard power LED to give feedback about the current state of the power supply. It also patches into the green wire on the PSU, which lets him turn on the power by pulling it to ground. After working out the cable routing he developed a web interface that makes it easy to interact with the setup.

As with other hacks along these lines letting an embedded computer run 24/7 is a lot less wasteful than leaving a PC on. That’s a concept we can really get behind.

Go to article

Nice Crop Job
Posted 10 hours, 42 minutes ago via FAIL Blog

Go to article

It's All Fun and Games Until. . .
Posted 11 hours, 12 minutes ago via FAIL Blog

Go to article

Percona Server for MySQL 5.5.31-30.3 now available
Posted 11 hours, 18 minutes ago via Planet MySQL

Percona Server for MySQL version 5.5.31-30.3

Percona is glad to announce the release of Percona Server for MySQL 5.5.31-30.3 on May 24, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.31, including all the bug fixes in it, Percona Server 5.5.31-30.3 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.5.31-30.3 milestone at Launchpad.

New Features:

• Percona Server has ported the Atomic write support for Fusion-io devices patch from MariaDB. This feature adds atomic write support for directFS filesystem on Fusion-io devices. This feature implementation is considered BETA quality.
• Percona Server has introduced innodb_read_views_memory and innodb_descriptors_memory status variables in the Extended Show Engine InnoDB Status to improve InnoDB memory usage diagnostics.

Bugs Fixed:

• Fix for bug #1131187 introduced a regression that could cause a memory leak if query cache was used together with InnoDB. Bug fixed #1170103.
• Fixed the RPM packaging regression that was introduced with the fix for bug #710799. This regression caused mysql schema to be missing after the clean RPM installation. Bug fixed #1174426.
• Fixed the Percona-Server-shared-55 and Percona-XtraDB-Cluster-shared RPM package dependences. Bug fixed #1050654.
• Fixed the upstream bug #68999 which caused compiling Percona Server to fail on CentOS 5 and Debian squeeze due to older OpenSSL version. Bug fixed #1183610.
• If a slave was running with its binary log enabled and then restarted with the binary log disabled, Crash-Resistant Replication could overwrite the relay log info log with an incorrect position. Bug fixed #1092593.
• Fixed the CVE-2012-5615 vulnerability. This vulnerability would allow remote attacker to detect what user accounts exist on the server. This bug fix comes originally from MariaDB (see MDEV-3909). Bug fixed #1171941.
• Fixed the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts efficiently. This bug fix comes originally from MariaDB (see MDEV-3915). Bug fixed #1172090.
• mysql_set_permission was failing on Debian due to missing libdbd-mysql-perl package. Fixed by adding the package dependency. Bug fixed #1003776.
• Rebuilding Debian source package would fail because dpatch and automake were missing from build-dep. Bug fixed #1023575 (Stephan Adig).
• Backported the fix for the upstream bug #65077 from the MySQL 5.6 version, which removed MyISAM internal temporary table mutex contention. Bug fixed #1179978.

Release notes for Percona Server for MySQL 5.5.31-30.3 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

The post Percona Server for MySQL 5.5.31-30.3 now available appeared first on MySQL Performance Blog.

Go to article

Psy Impostor Crashes the Cannes Film Festival
Posted 11 hours, 27 minutes ago via FAIL Blog

Go to article

Roommate Sabotage
Posted 11 hours, 42 minutes ago via FAIL Blog

Go to article

New stable kernels 3.9.4, 3.4.47, and 3.0.80
Posted 11 hours, 59 minutes ago via LWN.net

There are three new stable kernels available: 3.9.4, 3.4.47, and 3.0.80. All contain important fixes.

Go to article

Tungsten University: Load a Vertica data warehouse with MySQL data
Posted 12 hours, 10 minutes ago via Planet MySQL

Continuent Tungsten offers real-time replication from MySQL to a variety of DBMS types including Vertica. In this Tungsten University webcast we will show you the details of setting up MySQL-to-Vertica replication, including the following topics: Introduction to Continuent Tungsten features for data warehouse loading Installation for MySQL to Vertica replication Best practices for applications:
PlanetMySQL Voting: Vote UP / Vote DOWN

Go to article

This is the Most Insane LEGO Creation You'll See This Week
Posted 12 hours, 12 minutes ago via FAIL Blog

Go to article

McCain Puts Politics Aside and Asks the Tough Questions
Posted 12 hours, 42 minutes ago via FAIL Blog

Go to article

Morgan Freeman Falls Asleep During a TV Interview
Posted 12 hours, 57 minutes ago via FAIL Blog

Go to article

iPhone Urinalysis App Draws U.S. Government Scrutiny
Posted 13 hours, 9 minutes ago via MacRumors: Mac News and Rumors - Front Page

The U.S. Food and Drug Administration has sent a letter to BioSense Technologies over its iPhone uChek urinalysis system, asking why its medical app hasn't been cleared by the agency. The app is one of the first that turns the iPhone into a medical device, designed to read urinalysis test strips that are normally examined by users and compared to a color-coded chart.

With the uChek system, patients can take a picture of the strip with the iPhone's camera and then receive an automated readout of parameters like glucose, urobilinogen, pH, ketone and more. The app also stores results which then can be analyzed over time.


Though medical device makers have adopted the iPhone for some measurements like blood glucose monitoring for diabetics, large scale use of smartphones and tablets as a replacement for existing medical devices has yet to take off -- likely due in large part to government regulation of medical devices.

From Bloomberg:

Biosense Technologies Private Ltd.’s uChek system isn’t cleared by the Food and Drug Administration and the agency said it wants to know why not, in a first-of-its-kind letter to a maker of a mobile-device application. The app relies on users, such as diabetics checking their glucose, to dip test strips in urine and use the smartphone’s camera to allow the system to processes and generate automated results.

UChek works with test strips made by Siemens AG (SIE) and Bayer AG (BAYN), which are only approved for visual reading and require new clearance for automated analysis, the FDA said in the letter. The agency has said it wants stricter rules for apps that directly diagnose or treat conditions, proposing in 2011 to apply similar quality standards as for heart stents, ultrasound machines and other medical devices.

Go to article

Implementing asynchronous cascade delete in MySQL
Posted 3 days, 5 hours ago via Planet MySQL

A while back one of my foreign keys started causing trouble. The problem was that some parent rows had tens of thousand of child rows, and the foreign key was defined with CASCADE DELETE enabled. When we deleted one of those parent rows on a master database, it took several seconds to execute the delete because of the cascade. This led to latency for the end user, and also led to replication delays.

The immediate solution was make the application tolerant of orphaned rows in the child table and to drop the explicit foreign key constraint.

I didn't really want to leave those orphaned rows hanging around in the child table, so I decided to implement an asynchronous process to delete the orphaned rows on a scheduled basis. Read on for a description of that process.

Using the sakila database as an example, imagine I drop the foreign key between file_category and category, like so:

alter table sakila.film_category drop foreign key fk_film_category_category;

Without the foreign key in place, deletes on the category table lead to orphaned rows in film_category. For example, I will delete the "New" category:

``` mysql> delete from sakila.category

-> where name = 'New';

Query OK, 1 row affected (0.01 sec) ```

There are several ways to count the orphaned rows. Here are two different naive implementations using OUTER JOIN or NOT EXISTS:

``` mysql> select count(*)

-> from sakila.film_category c 
-> left outer join sakila.category p on p.category_id = c.category_id 
-> where p.category_id is null;

+----------+ | count(*) | +----------+ | 63 | +----------+ 1 row in set (0.00 sec)

mysql> select count(*)

-> from sakila.film_category c 
-> where not exists 
-> (
->   select NULL from sakila.category p where p.category_id = c.category_id
-> );

+----------+ | count(*) | +----------+ | 63 | +----------+ 1 row in set (0.01 sec) ```

I can also delete the orphaned rows using the same query approaches. I'll roll the first delete back so I can demonstrate the second query in the same session:

``` mysql> set autocommit = 0; Query OK, 0 rows affected (0.00 sec)

mysql> delete c.*

-> from sakila.film_category c 
-> left outer join sakila.category p on p.category_id = c.category_id 
-> where p.category_id is null;

Query OK, 63 rows affected (0.02 sec)

mysql> rollback; Query OK, 0 rows affected (0.00 sec)

mysql> delete c.*

-> from sakila.film_category c 
-> where not exists (select NULL from sakila.category p where p.category_id = c.category_id);

Query OK, 63 rows affected (0.01 sec)

mysql> commit; Query OK, 0 rows affected (0.00 sec) ```

This approach will be very slow for tables containing millions of rows, so in my real world case I didn't use this approach. Instead I decided it would be a lot easier and faster to delete the orphaned rows if I knew who their parent was. To this end I created a new table to track the deleted rows, and populated it using a trigger. Continuing the example in the sakila database:

``` CREATE TABLE category_deleted ( category_id tinyint(3) unsigned NOT NULL, name varchar(25) NOT NULL, last_update timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, delete_time timestamp NOT NULL, PRIMARY KEY (category_id) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

DELIMITER $$

DROP TRIGGER IF EXISTS sakila.TR_A_DEL_CATEGORY $$

CREATE TRIGGER sakila.TR_A_DEL_CATEGORY AFTER DELETE ON sakila.category FOR EACH ROW BEGIN

INSERT IGNORE INTO sakila.category_deleted (category_id, name, last_update, delete_time) VALUES (old.category_id, old.name, old.last_update,now());

END $$

DELIMITER ; ```

Now I can delete another category to test the trigger:

``` mysql> -- delete a single category mysql> delete from sakila.category

->     where name = 'Classics';

Query OK, 1 row affected (0.01 sec)

mysql> -- verify the trigger worked mysql> select * from sakila.category_deleted; +-------------+----------+---------------------+---------------------+ | category_id | name | last_update | delete_time | +-------------+----------+---------------------+---------------------+ | 4 | Classics | 2006-02-15 04:46:27 | 2013-05-21 18:21:53 | +-------------+----------+---------------------+---------------------+ 1 row in set (0.00 sec)

mysql> -- count the orphaned rows using the _deleted table mysql> select count(*)

-> from sakila.film_category c 
->     inner join sakila.category_deleted p on p.category_id = c.category_id;   

+----------+ | count(*) | +----------+ | 57 | +----------+ 1 row in set (0.00 sec) ```

I also wanted to execute the deletes on the child table in chunks, so I implemented a stored procedure to delete the orphaned rows by iterating through the rows in the _deleted table, deleting the child rows, and then deleting from the _deleted table. If I had to implement it again, I would probably use common_schema to chunk the deletes so I wouldn't need the stored procedure.

Here's an implementation using common_schema:

``` -- first delete the orphaned rows from the child table set @script := " split(sakila.film_category: delete sakila.film_category.*

from sakila.film_category 
inner join sakila.category_deleted on sakila.category_deleted.category_id = sakila.film_category.category_id 

) SELECT $split_total_rowcount AS 'rows deleted so far'; "; call common_schema.run(@script);

-- then delete the rows from the _deleted table (assuming they have no children) delete p.* from sakila.category_deleted p left outer join sakila.film_category c on c.category_id = p.category_id where c.category_id is null; ```

Go to article