On 2012-09-14 13:46, Michael Stowe wrote:
The Linux kernel keeps its own time, generally in UTC. This is
translated
to local time depending on the environment process of the user itself.
Thus, the backuppc user can have a completely different time than, say,
you, or root.
Depending on
On Mon, Sep 17, 2012 at 8:38 AM, Michael Stowe
mst...@chicago.us.mensa.org wrote:
That's absolutely true -- it's this line:
Running: /usr/bin/smbclient ts-1\\Users -c tarmode\ full -TcN
/var/lib/BackupPC//pc/ts-1/timeStamp.level0 -
That leads me to believe that the error is caused by
, September 13, 2012 5:45 PM
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Getting files newer than error
I usually use Debian. I switched a server to CentOS 6 and installed
BackupPC from EPEL, version 3.2.1 and CentOS 6 is using smbclient 3.5.
I took
My linux time is: Fri Sep 14 08:10:33 EDT 2012
BackupPC error: Last error is Getting files newer than Thu Sep 13
20:05:12 2012
Server Getting backed up time: Fri Sep 14 08:10:46 EDT 2012
There's something funny about the phrase my Linux time that makes me
believe I was not understood.
The
I usually use Debian. I switched a server to CentOS 6 and installed BackupPC
from EPEL, version 3.2.1 and CentOS 6 is using smbclient 3.5. I took out the
-N switch and it now backups up. It only backs up using the full method. If I
try to do an incremental backup it fails with this.
I usually use Debian. I switched a server to CentOS 6 and installed
BackupPC from EPEL, version 3.2.1 and CentOS 6 is using smbclient 3.5. I
took out the -N switch and it now backups up. It only backs up using the
full method. If I try to do an incremental backup it fails with this.
