Well, part of the problem there is that the folder is /var/tmp, not /vat/tmp. The script is not being run as you, but rather authenticated as root.

I'm not sure I would bother with this, Herbert. The 322 is likely to change (since it's probably a random number of sorts), and if it's just a matter of emptying your trash every so often, it seems unnecessary.

If I run the following little applescript after the SuperDuper!, the problem goes away.

set osx_path to (path to temporary items folder as string)
set unix_path to POSIX path of osx_path
do shell script (("cd " & quoted form of unix_path & " && rm -rf *") as text)

Um, that could easily remove things that other applications are depending on...

Yes, but this is the last thing that I do just before the shutting down the system. :)

OK, but just so others don't do this without thinking about it carefully-- it might be better to just empty your trash every so often.

Agree, it's easier than running a script. :)

For whatever it may be worth ...
 

I'm getting them files, too, after every SmartUpdate.

Yes; everyone will...

Does it just pertain to Smart Updates with 2.1?

I am only seeing the issue on 10.4.5 but not on 10.3.9 (but I don't use Smart Update on the Panther system...)

-Timmy

10.3.9 doesn't "clean up" the /tmp folder the same way, so you wouldn't see the issue there. The problem is a combination of the eSellerate "Embedded Web Store" engine installing itself when we run (and not cleaning up its temporary files), and Tiger's behavior that moves folders in the user's /tmp folder to "Recovered Files" in the trash.

Again, this isn't a huge deal (although it's annoying); you need only empty your trash normally -- when you do so, these files will be removed.

There's a similar discussion in the Flip4Mac forums. That discussion centers on conflicts between the version of eSellerate used by different apps. User "MyBFDoesTheHousework" appears to have a larger problem than files piling up in her trash, but that must be rare.

Perhaps the developers of SuperDuper! and Flip4Mac should compare notes.

Link: http://www.flip4mac.com/fusetalk/for...&enterthread=y

We're pretty sure we know what's going on, but unfortunately can't fix it directly -- we can only work around the problem (which we're doing), at least until eSellerate releases a fix in their code.

Isn't it a valid reason to stop installing this framework? I don't want this on my system because:

• you never told me about it, fortunately the Trash spilled the beans! :D
• AFAIK it's completely useless, I don't need a framework to buy your software :eek:
• if it's an annoyance to users it could make you look bad :o

Actually, it's listed in the "What does SuperDuper! install" FAQ.

The next version of SuperDuper! will only install the framework if you click "Buy Now!" inside the application.

Note, though -- having a framework present does *nothing* to destabilize the system or do anything else untoward. We're not replacing a system framework -- it's just that eSellerate is used by a lot of different programs, and thus they install to /Library so that all applications that use the eSellerate Web Store can share the same code.

This is really a non-issue. Mac OS 10.4 puts leftover temporary files in the trash upon startup, from time to time, even on systems where SuperDuper is not installed. It's normal behavior for the OS. See for instance,

http://docs.info.apple.com/article.html?artnum=301913

and

http://www.macfixitforums.com/php/sh...7&o=31&fpart=1

Apple's recommendation (see above Knowledge Base article) is "Don't worry," these files can be "safely deleted."

People with a lot of time on their hands can write scripts and the like for this. For me, the File => Empty Trash command seems about as easy as it gets. If this is what folks have to post about in this forum, well then I'd say that reflects pretty highly on Tiger's and SuperDuper's reliability that this is all that's left to complain about.