Circuitous path back to Lightroom

Over the last few years I have been through a number of Digital Asset Management (DAM) solutions. When my photo library first outgrew iPhoto I used iView Multimedia to manage everything. This became Microsoft Expression Media (and Windows only) so that route was closed. 

Next stop was with the new kid on the block Adobe Lightroom, which I was happily using for a few years. In those days it was a competent program but had limitations that became irritating. The biggest of these was it only really worked properly with RAW images leaving JPEGs with very limited support and video was a red headed stepchild at best. Not bad at the time I was shooting mostly raw, but then came better compacts, and the iPhone meaning more JPEGs

When I changed my Mac it was finally capable of running Apple’s Aperture and I gave it a go to see if it was better than Lightroom. It fitted my thinking well and while still focused on RAW processing gave more for JPEGs, and handled Video. I moved the whole catalogue over.

Since the Apple announcements along with Yosemite that both Aperture and iPhoto were being put out to pasture I was in a dilemma. There are still no firm details of what will and won’t be in Photos but best guess will be that it’s more than iPhoto but not quite Aperture

With all the uncertainty I finally decided to make a move when I noticed Adobe’s Creative Cloud Photographer Offering. For under £10 a month (even after the promo period ends) I can get the current Lightroom and as a bonus Photoshop CC. Seemed like a no brainer so here I am heading back to Lightroom again.

I’m going to miss some of the features of Aperture like the beautiful slideshow themes, face recognition, and a lot of the power searching but so far Lightroom seems to have matured and taken off a lot of the rough edges that irritated me before. 

The big job now is to migrate my catalog over with as little collateral damage to the metadata as possible, and then work out which of the many Photostream import solutions to try to implement

ASL Syslog Rotation

I have been having a fun time moving all my home services from a noisy self build linux host to a sleek quiet Mac Mini. In the transition I have been learning a lot about the differences managing MacOS X Server vs Ubuntu Server.

My latest foray made me think it might be worth blogging it. 
I have fail2ban installed to protect various services from the denizens of the internet, and I have been noticing that just after midnight it would regularly complain that the syslog file it was monitoring was missing. It would try a couple more times then fail and mark the jail idle leaving services unprotected.

Much reading round the subject and it would seem that syslog writing and rotation is managed by ASL on MacOS X. This dutifully rotates the syslog at midnight just like logrotate would, but with one important difference. It doesn’t bother to create an empty file. That happens the next time a log message arrives. Fail2ban does not appreciate the missing file when running on MacOs as it is using a poller backend rather than being notified of filesystem changes.

Now I don’t want to have to manually reload the fail2ban Jails daily, so I did a little hack. At midnight why not log something to make sure the file is created. Enter launchctl and one small config plist later I have a service that triggers at midnight raising a syslog which causes a message to be written to the system log.

I’ll report back when this has been running for a while

Update: Seems like updating at midnight isn’t quick enough as launchd starts me shortly after midnight and fail2ban has already noticed the log gone. Next try running a fail2ban-client command to mark the jail as not this at 0001