22nd October 2011 – 4:14 pm
4:14 pm
and the source server is too slow to tar -z all these files without having the tar process killed (and the thought of waiting several hours to trickle 50,000 files down the pipe is too much)…
rsync is your friend!
With compression, efficiency, and resume-able, it took only several minutes to shrink-send 700MB.
Background: a website running on a dual-core Atom server all the way over in the US needs to be migrated over to a faster host elsewhere. My several attempts at compressing the files with tar -zcf failed with ‘Process killed’ – presumably too much processing time was being allocated to this one task. Rsync, as well as being a synchronising superstar, is fantastic at transferring large number of files. I also use rsync to pull manual updates over to live sites (leaving bazaar for the test site).
Caveat: both sides need access to the rsync command with SSH access (or a running rsync daemon). The more files needed, the more free RAM needed – approximately 100MB for every million files 
19th October 2010 – 2:48 am
2:48 am
I’ve taken the liberty to rewrite the greasemonkey script to handle the new iPlayer layout. I’ve taken a different approach to this by injecting a stylesheet inline and toggling it on. Various videos did not have the ‘Pop-out’ player option, so I’ve added a button to enable/disable this feature in the top-right TV favourites panel. I’m sure most of you will find this works well enough to not use the pop-out option!
Install/update greasemonkey, install/update the iplayer script, browse to iPlayer, choose a film, toggle it on, and press F11 to set your browser to full screen
I have only tested this in FF3.6 but assuming xPath support is consistant among Firefox versions it should work as long as you have greasemonkey installed.
@See the original post.
8:21 pm
Just discovered this – to connect to subversion over a SSH tunnel that’s not on the usual port 22, you need to save a PuTTY session using the custom port, and refer to the session name in place of the hostsname in TortoiseSVN.
It seems whilst TortoiseSVN accepts the usual svn+ssh://myhost/repository/path URI (and even the svn+ssh://name@myhost/repository/path variation), this assumes that SSH is running on the usual port 22. I have tried (using port 333 as an example) svn+ssh://myhost:333/repository/path and svn+ssh+333://myhost/repository/path, however these will cause a host not found error.
It turns out that TortoiseSVN accepts a session name in place of ‘myhost‘, and the session name can include characters such as “:” so this would be one way of making the innocent looking svn+ssh://myhost:333/ work!
i.e. create a PuTTY session named ‘new-sess:ion2′ using the SSH protocol connecting to port 333 – and this should work in TortoiseSVN:
svn+ssh://new-sess:ion2/repository/path
– or a session named mysession:333 –
svn+ssh://mysession:333/repository/path
Now thankfully I do not have to be at home to view log information!
Reference: http://svn.haxx.se/tsvnusers/archive-2007-01/0272.shtml
21st January 2010 – 10:04 am
10:04 am
Found this quote in a comment in Engadget:
psmisc Posted Jan 20th 2010 1:39AM
I was in China a few years back, and I was surprised at how well people dressed. In fact, demand for name brand clothes were so high that they cost more in China than in North America, even though a lot of them were made there. It was a cliche for a secretary to spend many months of salary on a designer bag.
I always thought culturally the Chinese are the Italians of Asia. They are picky on clothes and food, like saving faces, and are loud in restaurants. Japanese are the Germans, punctual, precise, and kinky. Koreans are the Russians, melancholic, serious, and dramatic. Indians are the Greeks. Lively, passionate, and along with China, one of the remaining civilizations of the classical era.
Cultural observations are rather intriguing…