Electronox Blog Electronox Photo Gallery Electronox Forum
most recent blog posts
most recent comments
most recent forum posts

Update multiple domains with Namecheap and ddclient August 18th, 2012 by Justin


ddclient is a dynamic DNS client for multiple services, however Namecheap support is lacking in that multiple domain names are not handled correctly. If you are running into problems, here is a guide to fixing ddclient, tested on Debian, so that all your hosted domains are updated.

Note: this has been taken and modified from http://robertianhawdon.me.uk/2010/09/03/making-ddclient-work-with-multiple-domains-on-namecheap/

Copy the DDClient binary to the directory you’re working in:

$ sudo cp /usr/sbin/ddclient .

Open your copy of ddclient

$ sudo nano ddclient

Find this code section at line 3376 in the nic_namecheap_update section:

 my $url;
 $url = "http://$config{$h}{'server'}/update";
 $url .= "?host=$h";
 $url .= "&domain=$config{$h}{'login'}";
 $url .= "&password=$config{$h}{'password'}";
 $url .= "&ip=";
 $url .= $ip if $ip;

And change it to:

 my $url;
 $url = "http://$config{$h}{'server'}/update";
 my $domain = $config{$h}{'login'};
 my $host = $h;
 $host =~ s/(.*)\.$domain(.*)/$1$2/;
 $url .= "?host=$host";
 $url .= "&domain=$domain";
 $url .= "&password=$config{$h}{'password'}";
 $url .= "&ip=";
 $url .= $ip if $ip;

Write the changes and save.

Copy modified ddclient back:

$ sudo cp ddclient /usr/sbin/ddclient

For good measure, delete the ddclient cache (may be in different location):

$ sudo rm /var/cache/ddclient.cache

Edit your /etc/ddclient.conf file to include the top-level domain name with every subdomain. For example, if your domain name is example.com you would change your sub-domain line from:

@, www, subdomain


@.example.com, www.example.com, subdomain.example.com

An example for two domains would look like this:

use=web, web=checkip.dyndns.com, web-skip='IP Address'
use=web, web=checkip.dyndns.com, web-skip='IP Address'

Now you can restart ddclient:

$ sudo /etc/init.d/ddclient restart

DDClient should now be patched and able to work with multiple namecheap domains.

This process will need to be done every time DDClient is updated on your system, unless, of course, the patch has been merged in a later version of ddclient (last updated Nov 2011).

So, you can block ddclient updates with these few lines:

$ sudo echo "ddclient hold" | sudo dpkg --set-selections


$ sudo aptitude hold ddclient


Windows 7/Vista Power Settings Not Working May 17th, 2010 by Ryan


Recently I began having trouble with my machine going to sleep and while awake spinning down hard drives.  Waiting for drives to spin back up when changing tabs in Firefox and trying to remote desktop and vnc into an asleep machine got old very quickly. What was maddening was that the power profiles under the control panel were configured to not do either of these.

Browsing some forums, at least one other person started having this issue after install an update for .NET 2.0, and although this might do it I am pretty sure this can happen for other reasons as well.

What is happening is that the registry entry that tells the system what power profile to use is not being updated when you save the settings in the control panel.  Here is how to fix it.

Read the rest of this entry »

300zx Bose Restoration April 7th, 2010 by Dane


While Bose may have a reputation for innovation in the audio world, they also have a reputation for failure in the automotive world.  I will be documenting my experiences in restoring a Bose system in a 1990 Nissan 300zx 2+2. Much of this information will be applicable to other Bose automotive systems in Nissans, Infiniti’s, and other makes. I have gleaned information from sources relating to Corvettes and Infiniti Q’s. This has provided me a start in the restoration.


This website provides a good detail of Bose systems found in the 300zx family of cars.

Z Max Stystems Bose Page

Here are the high points:

  • Bose automotive systems use individual amplifiers for each speaker.
  • The amplfier/driver/enclosure are all tuned to each other (as they should be) http://en.wikipedia.org/wiki/Thiele/Small
  • The amplifier gain, equalization and compression are all changed based on what car the speaker is located in, where the speaker is located in the car, and it is rumored that even cloth/leather trims are considered.

Root of the problem:

That being said, it is common for these complex systems to fail.  The most common problem is capacitor failure. Much of the blame can be put on Bose for attempting to save a couple cents, opting for capacitors with a 16v tolerance. Now, a typical car circuit works on 12v (12v battery up front, right?). However, when the car is on, the alternator typically brings the voltage up into the 14-15v range. Getting awful close to that 16v break down voltage, huh? There are additional stresses that can be caused by jump-starting as well. While a higher break down tolerance may have helped most problems, the truth about electrolytic capacitors is that they can deteriorate in time, lowering the breakdown voltage. Let’s not forget the stress that all the bumping around can cause. Also moisture in the air, hot and cold… It’s really a miracle that more car stereos aren’t broken.

Solutions to the problem :

  • Buying New/Used Bose

Its still possible to purchase speaker/amp modules from Bose. They charge $140 a pop for a new unit. For a lot of people, this may be a solid option if convenience outweighs cost. You know for sure you’ll get a working unit that is up to factory spec. There are also amps that come up on ebay that have been used or are refurbished. One must be careful they are getting the EXACT replacement for their make/model/year/trim/speaker position.  Other amps may work, but they won’t be matched as they were from the factory.

  • Repair

For those who want to spend the least amount of money, this is the option. 20 bucks, one can purchase replacement capacitors for all of the amps in their car. However, some mechanical know-how, soldering skills, and time are the trade off. Some sources also claim that the performance will not be as good as new amps, however, I contest that IC’s, inductors, and ceramic capacitors don’t deteriorate like electrolytic caps, so upon replacement, the unit should work like new.

  • Aftermarket Replacement

This option has the advantage that sound quality can be improved (ie louder), modern equipment can be used (cd/dvd/nav systems) and other personal touches can be added. However, this means a non-stock headunit, which leads to two things: thieves like stereos and new headunits won’t match your interior. Also, all speakers must be replaced. Bose uses speakers whose DCR is <2 ohms. Most amps (and no head units I’ve ever seen) cannot run these speakers.

Personally, repair is what avenue I have chosen. For an heirloom car like a 1990 300zx in great condition, having the stock system is a definite plus. I’ve had a loud bumping system before, but the cleanness of a stock system is nice, especially in a small car like a 300zx. Not to mention, there are some weight savings to be had over a large system!  The notes below should help anyone trying to restore their 300zx or any early 90’s car equipped with a Bose system.


Source code repository with SVN and Trac on Debian Lenny April 30th, 2009 by Justin


There exist guides innumerable for this, but I recently went through this somewhat of a hassle and figured more documentation certainly wouldn’t hurt the situation. This is for a server located at trac.yourdomain.tld with multiple projects located in the the folders trac.yourdomain.tld/projectname1, trac.yourdomain.tld/projectname2.

Replace $projectnameX with your project’s name. Use the defaults for the trac-admin installer, except where it asks for your SVN Repository folder.

# apt-get install subversion libapache2-svn trac
# mkdir -p /var/local/svn/$projectname1
# mkdir -p /var/local/trac/$projectname1
# mkdir -p /var/local/svn/$projectname2
# mkdir -p /var/local/trac/$projectname2
# svnadmin create --fs-type fsfs /var/local/svn/$projectname1
# svnadmin create --fs-type fsfs /var/local/svn/$projectname2

# trac-admin /var/local/trac/$projectname1 initenv
# trac-admin /var/local/trac/$projectname2 initenv

# htpasswd -c /var/local/svn/$projectname1/conf/passwd $proj1username
# htpasswd -c /var/local/svn/$projectname2/conf/passwd $proj2username

//Additional users
# htpasswd /var/local/svn/$projectnameX/conf/passwd $addUser

Next, we need to configure Apache, this assumes you have SSL on port 443 configured. If not, you can just run over port 80 without the redirect.

Read the rest of this entry »

most recent blog posts
most recent comments
most recent forum posts