Re: stop hdup

[On 28 Mar, @ 01:19, WebAppz wrote in "[hdup-user] stop hdup ..."]
> Beste Miek,
> 
> First of all both thumbs up for you man.
> You did a swell job with the tiny, spiffy tool.
> 
> I was looking my ass off for a nice and hufter-proof backuptool and
> finally my eye fell on a link on linux-backup.net.
> 
> Thnx
> 
> Now I've got two questions if ya don't mind.
> First.. how do I stop it when i need to.

If it runs from cron you need to kill it with. Allthough I'm not quite
sure how hdup deals with those signals. This give me an idea for 2.0.8
though: fix all the signal handling in hdup (which I think might also
fix the problem that the lock file is not cleaned up if you kill a ssh
tranfer... but that is a different story). 

If you run it from the cmdline you can just ^C it.

> Sec. If the cronjobs I've created are touching each other, does that
> resolve a error.
> Like weekly runs on a monday at 1.11am and the daily backup runs
> everyday at 3.33am, with a full backup starting at 1.11am it will still
> be doing its cronjob at 3.33am when the daily backup starts.

In all hdup version before 2.0.7 there was a race in the locking
mechanism, from 2.0.7 on no 2 hdup instances should be running at the
same time. The newer hdup process would break off, with "could not
create LOCK".

If the two instances _do_ run at the same time, you've got a problem -
and you get weird results. If upgrading to 2.0.7 does not help contact
me personally.

--
grtz,
  - Miek

http://www.miek.nl                   http://www.nlnetlabs.nl