I know the guy who suggested their using a different updater (he's a heavy coder and I don't understand much of what he does) but he had wrote this same script for another major bank when they were patching and upgrading, I believe it emulates a drive mirror/image or something. This would have not have happened if they had used the newer scripts, NOTE: This guy also custom codes their PKI system so he's already known by the bank.
Oh well, didn't slow or impede a single cent of my money, it was apprently only effecting a VERY small portion of thier transactions during a 3-hour period (even though that adds up, it was only a couple of hours, not days )which has apparently been sorted now.
Your URl is broken, they added a %20 space in the word article, here's the condensed URL for anyone having problems.
http://tinyurl.com/2ttzd
The issue with the code was that this is ONE bank that still uses C++ scripting and the code is MUCH MUCH harder to debug and not as stable as Python.
If this was a Python script, as the PKI is structured, it would have never happened as it is (so I am told) due to a redundant code error, this is eliminated in Python as the code is far easier to comprehend and doesn't use redundat statements.
They are now asking for a second proposal from my friend's company and are investigating using Python in the future.