Ubuntu 9 server cron jobs (cron.daily, cron.weekly etc)

I have some backup scripts that live in my home directory and are symlinked into the /etc/cron.daily and cron.weekly etc dirs. Apparently run-parts will not run scripts that have a ‘.’ in the filename, so the symlink to the .sh files has to be named minus the file extension.

Also, testing the scripts with ‘sudo runparts /etc/crond.daily’ gave errors like this:

<code>run-parts: failed to exec /etc/cron.daily/update_apache_logs: Exec format error</code>

To fix this, I added this to the top of each of the scripts:

<code>#!/bin/sh</code>

JavaOne day 1 summary

There always seems to be an common theme to each JavaOne conference, and this year although I only got to attend the CommunityOne day and then the first day of JavaOne, it appears there is a continued focus on the community and building social networking tools and sites, and a continued push for JavaFX.

It seems the last couple of years pushing specific technologies has taken a backseat instead to focus on what you can do with the technology. There was the mobile push for a while, then social networking, community building and open source, and for the last 2 years, JavaFX to build engaging client-side apps.

I admit this year JavaFX curiosity got the better of me. Two years ago (?) JavaFX was announced with lots of smoke and mirror demos. Last year it was released. This year they’re stil pushing it hard with plenty of sessions, so I decided to attend a few of the sessions to find out what it’s all about. I’m impressed with the goals and aims of the FXScript language. It got me really interested to see a domain specific language like this and how much of the plumbing and technical details can be abstracted away. My main interest coming away from the sessions was not how can I use JavaFX, but how and when will the main Java language evolve to provide domain specific abstractions so we think less about the technologies – JSP pages, Servlets, EJBs, data access etc, and think about build business systems declaratively – will this ever happen?

McNealy and Ellison on stage together – the past and the future of Java

This morning’s keynote at day 1 of JavaOne 2009 had an interesting surprise – Scott McNealy came on stage and introduced the new owner of Sun Microsystems, Larry Ellison. I think this was the first time that Ellison had appeared in public to discuss the Oracle buy out of Sun. It was an interesting dynamic on the stage. Scott led up to the introduction of Ellison with a number of jokes about advertising Java on the America’s Cup yacht etc, so it was pretty light hearted, but there was some awkward moments where it was obvious seeing the two side by side – Ellison was full of energy and enthusiasm like a young boy with a new toy, and McNealy seems somewhat down and reserved… as I think you would be if you were talking to the person who had just swooped in and bought out the company you co-founded.

Ellison was surprisingly enthusiastic about JavaFX, and made comments that he’d like to see the Sun Open Office team continue and enhance Open Office using JavaFX – both surprising statements since Open Office and JavaFX were suggested by some to be high on the list of products/technologies that Oracle may ditch.

It was an interesting point in history where Sun Microsystems as we know it comes to an end, and Java continues into the future under the new stewardship of Oracle.

JavaOne 2009 – the last JavaOne?

I was interviewed by a magazine reporter this morning at the CommunityOne/JavaOne conference, and some of his questions got me thinking – will life after Sun with Oracle in the Java driving seat mean no more JavaOne conferences? Will Oracle do a combined OracleWorld/JavaOne conference, or will they continue to run JavaOne in the future? The first keynote is tomorrow morning, so while it will be surprising if anyone from Sun or Oracle have anything to say about the buy out (since the deal is still going through), or course we’re all wondering at the same time if they will talk about any changes coming up in the future as a result.