v2 logging
 

Just upgraded to v2 and I like it alot. However, I wonder where is the logfile stored now? I use Console to check logs and it seems that SD is no longer storing the log file in any of the default places. Where is the logfile? Is it possible to force SD to log in ~/Library/logs?

Press Cmd-l and you'll see the log, dudeX. It's not possible to force it to log in ~/Library/Logs for now -- we've bundled the log with the settings to make it easier for users to manage their logfiles, and to send in what they need to support should the occasion arise.

Ok, found the logviewer. I quess this makes it easier for some of the users to view the logs. For me this was a step back, as I don´t like that log files are so tightly coupled to the originating application. I like my logs in standard system locations in pure text format.

Luckily Mac is blessed with unix goodness and Automator, so it wasn't that hard to set up things the way I prefer them to be.

Feature suggestion: let the users choose where and in what format they want the log file to be. Would also be nice if there was a choice after finished backup to send the daily log to a spesified address using some account from Mail.app.

Keep up the good work!

Well, we wanted to be able to highlight problems for users, and that meant using RTF. It's a standard, non-exclusive format, though... so it shouldn't be difficult to deal with.

Thanks for the suggestions. We likely won't allow them to be relocated unless there's a lot of demand for it -- there are too many advantages to having them where they are -- but we'll see what people say. Notification options are planned for the future...

Here, here ...
 

here's my vote. While SD! does an absolutely bestest job of KISS, you have taken away a great amount of user preference here. I want to get to my logs and do so in a normal manner. Surely setting it up as some kind of option can make both sides happy.

Thanks for the vote, Macfeller. We'll have to see how the whole user base reacts to this, but I understand your concerns.

What, exactly, did you do with the logs you were getting in a normal manner? Were you scripting them?

Ha!
 

No, no scripting - as I don't have a clue how I would incorporate that. I have modified a copy script or two, but that's another story.

No, it is just that on more than one occasion I have had cause to wonder about something and looking at some of the logs has answered my question. No big thing; just basic user friendliness - as Apple so designed, perhaps. Nevertheless, as I have just seen, the present logging just gives the one last run. Perhaps that works for your needs but I would always want to compare a couple. Rooting around I have found them, but what a pain! i just don't think it would be all that hard to give us some options here (granted I have never done any coding in my life!). Ha! Actually, back in 1978, as part of a graduate course, I wrote a BASIC program full of if/then statements for plant care.

And, as we are seeing ...
 

majority rule is not always the best. (I'm speaking here about the US electorate in the last election - not so much to be political but to demonstrate that there not be a great clamoring for more user-friendly logging in no way negates the benefits of same.)

Oh, understood. I run a benevolent dictatorship here -- we've got some plans in this area. It's not going to be put back the old way, but that doesn't mean the log viewer won't be -- and wasn't planned to be -- enhanced to show the other available logs at some point... just not in 2.0.x. :)

Plans, huh?
 

Might those be along the logging lines or the despotic?! (just kidding)

As ever: thanks for the great work.

Mwah-ha-ha! :D

Would be nice to show the logfiles in the morning , after the scheduled backup ran during the night.
I like to see what SD did last night with my data ;)
Maybe for the majority such an option is enough?

If you leave SuperDuper! open, with the Scheduled Copies window up, you should see what happened in the list...