[S]I use "keep" for backups; and it runs EVERY time I start adept. How to stop?

[gameforge]

When I say it "runs", I mean it starts backing up my stuff - I can 'ps ax' and see rdiff-backup running.

I have my backups set to run daily, but I can start Adept Manager (or the updater, or even KPackage) 100 times in a day and it will concurrently start backing up every single time.

This is aggravating... perhaps it thinks it's backing up my system in case I install something that makes it unstable, but I'm not even backing up anything Linux specific - it's just my media and my documents.

Maybe you guys have seen the copy-file window that shows up right after you finish installing stuff in Adept Manager... that doesn't go away until the backup completes - meaning I either have to cancel it, kill the backup, or I can't install more stuff/close Adept until it finishes (depending on what's happened since the last backup, that can take a long time).

If nobody else knows how to make it stop, I'll start digging through code and post what I find here... but if someone else knows a more direct way I'd really appreciate it. I've tried Googling it, and this doesn't seem to be documented in the places I'm looking for it at least.

[gameforge]

Re: I use "keep" for backups; and it runs EVERY time I start adept. How to stop

Finally figured this out.

When I first ran keep some time ago and set up my backups, I ran it with kdesudo - I think I did that because I was backing up tens of thousands of files, and a few isolated ones somehow didn't have read permissions or weren't owned by my user account.

Huge mistake.

Keep's daemon runs as a KDE service. What I didn't even think of was that the root account has its own KDE session starting up every time you run a KDE program as root, whether it be with kdesudo, sudo or otherwise. At least this seems to be the case.

What fooled me was "administrator mode" button in the control center's KDE services module. I would have thought that KDE has one set of services for an installation, and they stay the same and keep their configuration regardless of who you're logged in as; not true, each user has his/her own set of KDE's services. This makes much more sense from a design standpoint obviously; it probably would have dawned on me right away if I shared KDE with other users. Oh well.

So in my case, the only time I'd ever use kdesudo was when using Adept; and each time, root would start some minimal KDE session (including his services)... and this meant his keep daemon. Then my backups would all run. This, of course, means that my backups weren't running on schedule this whole time, but rather whenever I'd download updates or whatnot.

The solution was to remove all of my backups from the superuser's keep, then start it instead as my normal user and reconfigure them again.

Lesson: for system backups, use rdiff-backup and the cron daemon. For user backups, run keep as your user.