Jakob Unterwurzacher wrote:
in bash:
#!/bin/bash
for i in `seq 1 $((RANDOM%100))`; do /bin/true; done
But you should make sure that $RANDOM assumes different values after a
reboot (same for perl's rand(100), which is likely more advanced and
less likely to suffer from that problem).
Jakob
Steven Willoughby schrieb:
> #!/usr/bin/perl
> `/bin/true` for 0..int(rand(100));
>
> This will increase the pid and should stop your job from failing
> continuously.
>
> Steven
Exactly.
Same thing in bash:
#!/bin/bash
for i in `seq 1 $((RANDOM%100))`; do /bin/true; done
But you should make
Dean Cording wrote:
I've come across an issue with the way that rdiff-backup ensures that only one
server is accessing a backup dataset.
...
Recently I had a backup fail, probably because of a network outage. All
subsequent backups refuse to run because rdiff-backup believes the failed rdiff-
I've come across an issue with the way that rdiff-backup ensures that only one
server is accessing a backup dataset.
When rdiff-backup starts it checks the metadata to see if another instance of
rdiff-backup is performing a backup. If it finds one then it checks the PID to
see if the other ins
