From: Rahul <rah...@gm...> - 2007-04-30 08:53:31
|
Dear Craig, Our server is set in a production environment and it will be difficult to upgrade the tar version. We want to continue using backup PC, so please can you set another option which will solve this issue without updating the existing GNU tar version. regards, Rahul On 4/27/07, Craig Barratt <cba...@us...> wrote: > > Rahul writes: > > > We are using GNU tar version >= 1.13.7. > > That's an old version. Can you upgrade to something > more recent, eg: 1.15.x or 1.16.x? > > Craig > |
From: Holger P. <wb...@pa...> - 2007-04-30 11:00:32
|
Hi, Rahul wrote on 30.04.2007 at 14:23:33 [Re: [BackupPC-users] Transfer and error log messages]: > On 4/27/07, Craig Barratt <cba...@us...> wrote: > > > >Rahul writes: > > > >> We are using GNU tar version >= 1.13.7. > > > >That's an old version. Can you upgrade to something > >more recent, eg: 1.15.x or 1.16.x? > > Our server is set in a production environment and it will be > difficult to upgrade the tar version. > We want to continue using backup PC, so please can you set another option > which will solve this issue without updating the existing GNU tar version. install a modern tar version somewhere only BackupPC will use it. I was going to suggest BackupPC's bin directory, but that doesn't make sense, as we're talking about the clients to be backed up, not the BackupPC server, aren't we? FHS would probably suggest /usr/local/bin, but that might be in your $PATH somewhere and lead to confusion. Of course, you could call the new tar binary 'tar-1.16' instead of plain 'tar'. You'll just have to make sure $Conf {TarClientPath} is set correctly for the hosts in question. Regards, Holger |