Archive for the ‘technology’ Category

Recursion and namerefs in ksh93

No Comments »

Today I had a reason to use namerefs in a recursive function in a ksh93 script.  Specifically, I wanted to build a list of email addresses for the management chain above an arbitrary number of employees.  I used an associative array so duplicates would automatically be removed.  But I wanted the function adding elements to the array to potentially work with different arrays.

Originally, I wrote the function roughly like this:

function append_managers {
  typeset -l user=${1:?}
  typeset -n arr=${2:?}
  typeset manager

  lookup "$user"
  manager="${manager[$user]}"
  lookup "$manager"
  arr[${email[$manager]}]=1
  is_vp "$manager" && return
  append_manager "$manager" "${!arr}"
}

I think this is pretty self-explanatory, but the way this should work is that the function takes a user name and an array name as mandatory arguments.  It uses a function (lookup()) to populate a few global arrays, including “manager”, “email”, and one with the title (so is_vp() can later determine if the person is a VP or below).  The manager’s email address is inserted into the associative array which was passed in, and then if the manager is not a VP or above, the function calls itself to continue climbing up the management chain.  The things in here which might be unfamilar are

  • typeset -l, which forces the variable’s value to lowercase (which works better with my directory)
  • typeset -n, which makes the variable a “nameref”, so using the variable affects a variable with the name of the nameref’s value.  It’s kind of like a pointer.  In this case, referencing $arr will actually reference the variable with the same name as what was passed in as the second argument.  If you do “a=’hello’;typeset -n b=’a’;print $b”; you should get “hello” in ksh93.
  • ${!var}, which gets the name of the variable pointed to by a nameref.  In the case above of ${!arr} and a function call like “append_manager ‘danny’ ‘cc’”, that would expand to ‘cc’.

This last bullet point is where things get hung up.  The variable scoping in ksh93 with functions defined like “function f{}” (as opposed to “f(){}”) is lexical.  In general, lexical scoping means that the scope is like the code would read; if you fully expand the code by copying the whole functions into the places where they’re called, copy includes in place, etc so that you have one long procedure, then variables’ scope would be where they appear.  In this situation, that essentially translates to “variables defined in a function using typset are local to that function and to any functions called by that function.”  So, recursive calls to “append_manager” with the same array name should all be able to see the same original array.

Unfortunately, in the version of ksh93 on the machine where I’m developing this – a RHEL6 system with “AT&T ksh 93u+” – this does not work as expected.  On the second iteration through the recursion, I get an “arithmatic syntax error” when I try to use the nameref.  I tried a number of variations on the approach; I tried hard-coding the array name, I tried putting the array name into a variable and then using that variable to hold the nameref name (instead of $2), and I tried making argument $2 optional so recursive calls just provided a new name while using the nameref scoped within the first call to the function.  In all cases, I got either the same error or an empty array at the end.  I suspect that the recursion messes up the internal variable tracking.  Regardless of the cause, wWhat I finally ended up with was replacing the recursive call with this:

append_manager "$manager" "arr"

So, each call gets a new locally-scoped nameref variable pointing to the nameref array in its parent.  It makes me feel slightly ill to have a call where I’m basically doing “typeset -n a=a”, but since the new “arr” is in a different, lower scope than the first, they’re technically two separate variables.  It actually works, though, and even with various combinations of things I threw at it, it works properly.  So, that’s what’s in my final script – along with some comments hopefully saving a future programmer the time.

One final note: I mentioned that I used an associative array to avoid duplicates.  But that means I need to pull the indices (AKA “keys”) from the array in order to generate my final list of email addresses.  Considering an array named “cc”, the code to generate an Outlook-friendly (separated by semicolons – ugh) list of email address looks like this:

    OLDIFS=$IFS; IFS=";"
    print "cc: " "${!cc[*]}"
    IFS=$OLDIFS

Or like this:

    list=$( printf '; %s' "${!cc[@]}" )
    print "cc: ${list#??}"

The first option uses IFS to separate the arguments, which is limited to a single character.  The second option (the one I actually used), prints each element preceded by a semicolon and a space, then prunes the first two characters off of that list.  One could also use “${list:2}”, but I use the “prune” modifier more often than “substring” because I still have some older POSIX shell habits where the substring option wasn’t an option. :)


Keeping a directory in sync with SVN

No Comments »

I keep my CFEngine policy (and some other similar things) in a Subversion repository.  The progression from unit test to integration test to production is handled by using tags.  Basically, the integration test policy is the trunk, unit tests are done by branching the trunk, and promotion to production is done by tagging a revision of the trunk with a release name (monthly_YYYY_MM.POINT). But this discussion doesn’t need to be just about that approach; my solution should work for pretty much anyone who needs a directory to match a portion of a subversion structure.

Read the rest of this entry »


Running trac-admin from python

No Comments »

Recently, I’ve been trying to speed up my Subversion post-commit hooks.  I have several things which are run from the hook, and the number of separate commands leads to a bunch of fork() calls (or clone(), whatever).  Several of the scripts are already Python, so I figured I’d just write the hooks themselves in Python, making it so that the python interpreter would only need to start once and allowing the separate methods to be pre-compiled python.  This should decrease overall execution time, making the end-user experience slightly better overall by decreasing the time they have to wait on the server.  We’re talking about fractions of a second, but I have some operations which bulk-create directories in SVN or otherwise cause tens or hundreds of new revisions to be created at one time (which is necessary for the way some of my integration processes work), so it actually adds up.

This is also an excuse for me to learn Python, so bear with me if the code below is horrible.  Actually, don’t bear with me – leave a comment letting me know how it should have been done. :)

Read the rest of this entry »


Using a database to configure CFEngine

No Comments »

I’m responsible for a pretty large CFEngine installation.  CFEngine is designed to be pretty self-sufficient even when the network is unavailable, so it basically works by keeping its configuration local on each machine, and running from that local copy.  This is mostly implemented using a file-based configuration structure.  There’s a main configuration file (promises.cf) which includes several additional configuration files.  In pretty much every situation, one of the promises (the name for an individual policy item) or bundles of promises will ensure that the local config files are in sync with the configuration files on the central master.

While it’s possible to use LDAP or define some variables on the central master, the main way configuration is done is by putting the policy into some files on the master and then allowing individual systems to copy those files down; the central master is basically just a fairly efficient file server.

Read the rest of this entry »


Comparing Puppet and CFEngine in recursive file handling

No Comments »

So, we all know that ruby’s memory management is sketchy at best, and the Puppet is generally slow. But how can we quantify that? One of the metrics which is important to my usage is that of verifying the permissions on a large number of files. To that end, I wrote a simple script to compare the performance of ensuring that the contents of a large directory of files are owned by a specific group. Before each test, I remove a temp directory, create a set of sequentially-named files with the wrong group ownership, and then correct the ownership. I then run the same command again to see how quickly it can verify the permissions – which should be the common case.

For the baseline, I use “find | xargs chgrp”, which is slightly slower than “chgrp -R”, but not much slower (and, in my mind, slightly more fair). I then use a simple CFEngine policy and a simple Puppet policy to do the same thing.  The summary?  Puppet is dog slow at file recursion, while CFEngine is nearly as fast as pure find.  CFEngine actually uses less memory than the shell when you get to many files (probably due to the pipe to xargs), and Puppet wastes memory like it’s been surfing the web for weeks using an old version of Firefox.

Read the rest of this entry »


CFEngine vim hilighting

1 Comment »

Get the highlighting code from https://github.com/neilhwatson/vim_cf3, and set it up in a location that will be loaded by default.  I’m partial to making  directory under /usr/local/share, and then linking the files in.

Read the rest of this entry »


Galaxy S3 and stupid SSL support

No Comments »

Ok, I found something I dislike about my Galaxy S3. Apparently, in order to trust a third-party (in this case, my own) SSL signing certificate, I need to change my authentication mechanism. If I have any non-default signing authorities on my phone, the option to do face unlock and voice unlock are disabled; you can only install them if you have a pin code or passphrase lock. Further, you can’t change the auth mechanism back to a “less secure” option until after you’ve removed those signing certificates.

I guess that I have to choose between trusting my own signing authority, and using a convenient authentication mechanism to get in to my phone.

If anyone happens to know of a workaround that lets me use face unlock *and* trust a couple of SSL certificate authorities, I’d sure appreciate it. I’m willing to accept the risk of someone taking my phone, unlocking it with a picture of me, and installing an additional certificate signing authority. :/


Ping localhost failed in BackupPC after Ubuntu 12.04 upgrade

No Comments »

After upgrading my backup server from the previous LTS release (Lucid) to the new one, the config which backs up /etc on localhost was failing.  It was failing because pings to localhost were failing.  This is no good – localhost should be pingable. :)  Ultimately, this is because IPv6 is enabled by default now.  I don’t use IPv6 on my internal network, mostly because it’s new and scary and I don’t like change.  Or because I just don’t need it.  So, here’s how to disable IPv6 on your Ubuntu 12.04 / Precise box:

Read the rest of this entry »


xfs v/s reiserfs storage

No Comments »

So, since I have to rebuild my mp3 library anyway, I thought I’d do a comparison between storing my mp3s on either reiserfs or xfs.  I already know that reiserfs is horrible for recovery, but hopefully I won’t need that.  Reiser is supposed to be good for storage because of the tail-packing thing, though.

I’ve recovered about 18GB of songs now, the biggest file is about 50MB; the average is about 8MB.  Somewhat surprisingly, the xfs filesystem (/mnt/a) actually is using less space to store the identical directory structure (artist/album/mp3).

 sauer@humpy:~$ for D in /srv/nfs4/music /mnt/a;
  do find $D | wc -l; done
 1589
 1589
 sauer@humpy:~$ du -ks /srv/nfs4/music /mnt/a
 12380231        /srv/nfs4/music
 12369836        /mnt/a
 sauer@humpy:~$ df -k /srv/nfs4/music /mnt/a
 Filesystem           1K-blocks      Used Available Use% Mounted on
 /dev/mapper/idevol-music
 52427196  12414684  40012512  24% /srv/nfs4/music
 /dev/mapper/idevol-music2
 52403200  12403660  39999540  24% /mnt/a
 sauer@humpy:~$ sed -n '/music/p' /proc/mounts
 /dev/mapper/idevol-music /srv/nfs4/music reiserfs rw,noatime 0 0
 /dev/mapper/idevol-music2 /mnt/a xfs rw,relatime,attr2,delaylog,logbsize=64k,sunit=128,swidth=384,noquota 0 0

So, since xfs also recovers faster and is more actively maintained, I’m switching to xfs.


Add h264 support to ffmpeg on Ubuntu

No Comments »

So, I’ve got a handful of Ubuntu machines.  I also have a bigger handful of DVDs.  I’d like to conver the DVDs to easier-to-store videos which can be accessed by MythTV, XBMC, my mobile devices, and whatever else easily.  The best broadly-supported format to do that in is h264-encoded mp4 files.  And DVD::Rip does a nice job of letting me use all 20 or so CPUs I have laying around, rather than limiting me to just one workstation.

Unfortunately, DVD::Rip uses transcode, which uses ffmpeg to do the encoding.  And Ubuntu’s ffmpeg, for whatever reason, lacks h264 support.  There’s a guid to rebuilding it which has you pull down the latest source for all the utilities from CVS, and make new packages which don’t work right and are a pain to maintain.  I, on the other hand, want to just take the Ubuntu package and add one compile-time option, so it’ll still work like the vendor-provided package.  After all, all I ned to do is build the exact same thing with the “–enable-libx264″ option.  Here’s how.

Read the rest of this entry »