How to get Transfer-Counts during backup?

Matthias Meyer <[email protected]>
Newsgroups gmane.comp.sysutils.backup.backuppc.devel
Message-ID <[email protected]>
Hi,

I would like to get actual transfercounts from BackupPC_dump during an 
active running backup.
I establish a signal handler in BackupPC_dump:

$SIG{IO} = \&write_status;
sub write_status
{
    my $sigName = shift;
    my $client = shift;
    my $newStat = $xfer->getStats;

    print( STDERR "Signal IO catched. $newStat->{fileCnt}" );
    return;
}
and run the process with:
sux backuppc perl -d:ptkdb /usr/share/backuppc/bin/BackupPC_dump -f athlux

At the moment I have two problems:

1) $newStat->{byteCnt} as well as $newStat->{fileCnt} are 0 each time I 
enter the signal handler

2) Sometimes the process died with:
XIO:  fatal IO error 11 (Ressource not available) on X server 
"localhost:10.0"
      after 4555 requests (4362 known processed) with 0 events remaining.
dump failed: Child exited prematurely

X Error of failed request:  BadIDChoice (invalid resource ID chosen for this 
connection)
  Major opcode of failed request:  53 (X_CreatePixmap)
  Resource id in failed request:  0x5c00158
  Serial number of failed request:  7559
  Current serial number in output stream:  7729


Any Idea/hint from one of the expert perl programmers?

Thanks in advance
Matthias
-- 
Don't Panic


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
BackupPC-devel mailing list
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.