Package: rdiff-backup
Version: 1.1.9-2
Severity: normal

Here is output from a cron job:

Wed Apr 18 13:00:01 IST 2007
umount: /dev/r1vg/homesnap: not found
unmounted already
  Logical volume "homesnap" created
--------------[ Session statistics ]--------------
StartTime 1176881414.00 (Wed Apr 18 07:30:14 2007)
EndTime 1176907242.10 (Wed Apr 18 14:40:42 2007)
ElapsedTime 25828.10 (7 hours 10 minutes 28.10 seconds)
[...snip...]

And here is the shell script which generated the output:

echo "rdiff-backup"
date

host=leghorn
snapname=/dev/r1vg/homesnap

remove_snapshot() {
  umount $snapname || echo 'unmounted already'
  if lvs $snapname > /dev/null 2>&1 ; then
    lvremove -f $snapname
  fi
}

if  ping -q -c 3 $host > /dev/null; then
  remove_snapshot
  lvcreate -L 2G --snapshot --name homesnap /dev/r1vg/home
  mount $snapname /mnt/home_ro
  ssh $host mount -t ext3 /dev/b1/rdbackup /mnt/rdbackup || echo 'already 
mounted'
  rdiff-backup --print-statistics /mnt/home_ro $host::/mnt/rdbackup/home
[...snip...]

As you can see, the actual start time is Apr 18 13:00:01, not what
rdiff-backup reported Apr 18 07:30:14. This is confusing.

-- System Information:
Debian Release: 3.1
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.6-b1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages rdiff-backup depends on:
ii  libc6                         2.3.6-7    GNU C Library: Shared libraries
ii  librsync1                     0.9.7-1    Library which implements the rsync
ii  python                        2.4.3-11   An interactive high-level object-o
ii  python-support                0.5.4      automated rebuilding support for p

Versions of packages rdiff-backup recommends:
pn  python-pylibacl               <none>     (no description available)
pn  python-pyxattr                <none>     (no description available)

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to