Hi,

A n00b here, I hope somebody can help me..

My akregator was running in background when I accidentally deleted the akregator folder in ~/.kde4/share/apps/akregator It was a quite big archive ( >100 Mb ) with tags etc.. so I really don't wanna lose it..

But i haven't closed the akregator, everything is still normal: I can browse my archive, tags are still there etc.. But I'm afraid that if i close it, all will be gone

The akregator complained it couldn't write feeds.opml, so i recreate the akregator folder and it's default sub folders: Archive and data, so it can write the opml file. The program wrote the opml file into the data folder I recreated. But the Archive folder is still empty now.

My questions:

- If i close the akregator now, will I lose my archive forever? Or will it automatically recreate the archive? Because everything is still "there" now, I can read my feeds etc so it must be "somewhere"

- Where do akregator read these feeds I'm browsing now from? Are they in a temporary folder or memory? Is there anyway to copy that "temporary" data?

Thanks for your help..

You say you are a newbie, so if you don't understand anything, do ask.

Take a look at ~/.kde/share/apps/akregator/Archive - if you see plenty of entries there you have not lost your archives. I would expect that all will be re-created when next you open akregator. However, just in case I'm wrong - it is always better to make safeguards. If you can see those archives, before you close akregator, copy that folder and rename it to Archive.sav. When you are certain that all is well you can delete the .sav folder.

I always recommend saving backups in this way before doing anything that could possibly be destructive. They are rarely needed, but occasionally can save your life

You might like to make a backup of /.kde/share/config/akregatorrc, as well.

Hi, thx 4 d quick answer

> Take a look at ~/.kde/share/apps/akregator/Archive - if you see plenty of entries there you have not lost your archives

Well, that's exactly what my problem is: I stupidly deleted the folder

But akregator is still running now and i can still browse my "archive" (wherever that may be).. Maybe it's still in memory or in a temporary folder, I don't know.. So there might still be a chance to recover to deleted archive if I know where to look, that's what I'm asking here..

Anyway thx 4 d suggestion, i make sure i do that in the future

edit:
BTW wouldn't it be nice if we have "Backup Archive" or something like that in akregator? Another plus if we can choose which feed(s) or folder(s) to backup..

I found out that when I closed akregator, all my archives are gone for good. So I think my archive was in RAM. If only akregator had a backup tool so we can dump the archive from RAM...

I know this rarely happens but I think the backup tool will be handy for some other purposes. I love akregator and I hope it will become better. Kudos to the developers & all of the contributors

If you can "recieve" some new items, then it is possible that Akregator will write out the entire archive for you again.

It does receive new feeds every 30 minutes, but i think it only loads them into RAM because the Archive folder is still empty. But it does write a new feeds.opml into the data folder.

I think there should be a mechanism in Akregator that tests the integrity of the archive every 30 minutes or everytime it fetches new feeds, with a dialog asking to rebuild the archive had it failed the test. And of course we should be able to do it manually too.

Thank you.

This is probably a feature of UNIX, where Akregator still has the "handle" for the archive folder open, and it is not aware the file has been deleted. Thanks to the magic of /proc you can still recover your archive file, as long as you have not closed Akregator yet.

See http://www.linux.com/archive/articles/58142

WOW thank you very much bcooksley!! I managed to recover ALL of my deleted feeds by following the guide! I just wished I knew some bash scripting so I didn't have to manually copy all 72 feeds one-by-one
Thank you very much!

No problem, topic marked as Solved.