To fix this problem, run
sudo update-alternatives --config javaws
and choose the java 7 version
All current Tomcat-based projects have now been moved to Peach, with the help of RE, who has re-pointed all the relevant domains. The IALLTJournal project has been retired, since it's no longer in use, as has the old version of Francotoile, which was built on eXist 1.4. This was a fairly slow and careful migration over a couple of days, and we expect no problems, but Pear will continue to run for a little while just in case.
After a system update, rsync stopped working over ssh on Rutabaga. We eventually discovered that users rsyncing over ssh require the ssh service to be turned on (Control panel/Terminal/SSH service). This was apparently not necessary in previous builds, or perhaps it was turned off by the update for some reason.
Putting this on the blog because I keep forgetting it:
Type Control+Shift+U, then release and type the hex of the character, then return.
A change in the user agent string for Firefox 17 has triggered an error message in HotPot and Quandary exercises. An update to the applications will be required, which we'll do at home, but in the meantime all the existing exercises we provide to departments needed to be updated, including Greek, Latin, Spanish, XSLT (DHSI), Hulquminum and Arabic. Those have all now been updated.
This is basically what I did:
([\t ]*alert\('Your browser may not be able to handle this page.'\);) //$1
rsync --verbose --progress --stats --recursive --include '*/' --include '*.htm' --exclude '*' arabic/ firstname.lastname@example.org:/u/lancenrd/www/arabic/
Some notes on how to configure Gnome 3, in preparation for trying to roll it out to the lab machines:
email@example.com firstname.lastname@example.org email@example.com RecentItems@bananenfisch.net force-quit@xtranophilist Shut_Down_Menu@rmy.pobox.com firstname.lastname@example.org email@example.com firstname.lastname@example.orgThese are in ~.local/share/gnome-shell/extensions.
gsettings set org.gnome.shell.clock show-date true
This is my documentation of recent changes to the way the TEI Jenkins Continuous Integration Server VMs are configured.
The new VM whose machine name is teijenkins1204 is now running Jenkins on port 8080, and also Apache proxying Jenkins on port 80. JA (sysadmin) has pointed the DNS entry for teijenkins.hcmc.uvic.ca at this machine, so the Jenkins instance is accessible on port 80 and 8080 there. The dual access allows for normal access to Jenkins on port 80 (convenient), but also for a situation in which we might want to put up a temporary warning page on port 80 while solving a problem with Jenkins accessed through 8080, then restore the proxy setup. I followed these instructions to set up proxying.
That machine is also running denyhosts.
The old machine hostname has been changed to teijenkinsdev, and JA has pointed teijenkinsdev.hcmc.uvic.ca at it. The Jenkins service has been disabled on this machine using sysv-rc-conf. When I ran that tool, it showed X characters for the jenkins service on run levels 2, 3, 4 and 5. I removed all of them; to re-enable the service, run it again and replace them. In the meantime, you can run Jenkins manually using
sudo /etc/init.d/jenkins start. The plan is to reprovision that machine with more RAM and disk space, and then build it up with Ubuntu 12.10 to test and tweak the build script; doing this for every Ubuntu release will make it less messy to migrate to the next LTS when it comes out.
Spent some time with GN trying to get builds working on Plum. We found a couple of bugs in the code, which were reported and fixed, and I also added some new false positives to the log-parse file. Now we're back to apparently-working builds (although with warnings) for three out of the four builds OK, and the last one in process. I need to start testing recent builds with MoEML next week if I have a chance. We've commented out the svn module because that was causing problems.
This seems to work:
roma --xsl=/home/mholmes/WorkData/tei/sf_repo/trunk/Stylesheets --localsource=/home/mholmes/WorkData/tei/sf_repo/trunk/P5/Source/guidelines-en.xml --isoschematron london_all.odd
:: Next Page >>
This blog is the location for all work involving software and hardware maintenance, updates, installs, etc., both routine and urgent, in the server room, the labs and the R&D rooms.
|<< <||> >>|