rinetd fills your syslog with errors

I recently made some changes to the rinetd configuration on the linux development server here. Everything seemed to work fine, but a few days later I noticed the follow wharrgarbl in my syslog:

Jul 27 14:28:11 easserv rinetd[14712]: accept(0): Socket operation on non-socket
Jul 27 14:28:42 easserv last message repeated 546042 times
Jul 27 14:29:43 easserv last message repeated 1077719 times
Jul 27 14:30:21 easserv last message repeated 680478 times

After searching around, it turns out I had made a typo in one of my rules. Instead of using the currentl 10.10.10.254 address, I had this new entry:

0.0.0.0 38254 10.10.10.255 80

So having an invalid IP address in those rules, causes rinetd to have a fit. Changing the 255 to a 254 and restarting rinetd solved my problem.

Adobe Lightroom 3 hangs on Import with JungleDisk

I've been playing around with the new Adobe Lightroom 3 for Windows, now that it's released. So far, it looks pretty good!

One thing I noticed right away was that its Import functionality (which is completely redesigned for LR3) appeared to hang indefinitely on my system. After quite a bit of research, I found this Adobe Forums thread that helped me solve the problem: JungleDisk drive mapping presents itself as a Removable Drive, which LR3 automatically attempts to scan.

Because the mounted JungleDisk drive connects to the Amazon S3 storage service, it is a slower WAN connection and Lightroom will probably sit there for minutes or hours trying to scan the entire drive. The solution is to configure JungleDisk to present its mounted drive as a Network Share instead:

• Go into Jungle Disk Desktop Monitor
• Click on Configure
• Select Network Drive::Local Drive Mapping
• Make sure "Show Advanced Options" is checked at the lower-left
• Change the "Drive Type for all Online Disks" option to "Network share"

Once you do that, the Lightroom Import dialog should be much smoother.