Hello :)
Thank you for your fast response. It makes me happy 😊️.
I have another client where $Conf{ClientNameAlias} is also defined as array.
This client is backing
up well.
Anyhow I changed $Conf{ClientNameAlias} to be a string in both.
The other client is working well, as before and devel-w8 isn't as before.
Maybe it is a problem that the client devel-w8 is currently not able to connect
to the server?
The issue isn't important or urgent. I could delete this old windows8 client
and the issue is gone.
Regarding patches - Yes, you are right. I forgot that we have exchanged our
minds. I'll continue
that in a new thread.
br
Matthias
Am Mittwoch, dem 10.06.2026 um 15:38 +0100 schrieb G.W. Haywood:
> Hi there,
>
> On Wed, 10 Jun 2026, Matthias@gmx... wrote:
>
> 1. ------------------------------
>
> > Attached you will find my config.pl, the failing devel-w8.pl as well
> > as the correct working honeypc.pl
>
> The one obvious thing that I can see there is that in the working
> config you have $Conf{ClientNameAlias} set as a string, but in the
> non-working config it's an array. That's supposed to work (at least
> it's supposed to work for non-DHCP hosts), so the first question has
> to be is devel-w8 a DHCP host? If it is not, then this might be the
> result of a failure to cope with an edge case - i.e software fault.
> (I don't like the term 'bug':).
>
> If you look at the first few lines of any XferLOG for devel-w8 you
> should see the full rsync-bpc command. My guess is that it will be
> incomplete in some way and that this is why it's failing. I think
> that the error message is in correct, the result of the failure to
> handle the edge case.
>
> Please try setting the value in the failing config to a string and let
> me know what happens. If it works that way I think some investigation
> will be called for.
>
> 2. ------------------------------
>
> > Yes, I modified BackupPC_dump and BackupPC_restore. I'asked for
> > providing it as a patch on May 4, last year (hxxps://sourceforge...
>
> That pre-dates my taking over as maintainer for BackupPC, but I think
> I recall that we talked about it later in the year. Taking your two
> modified files in reverse order:
>
> > BackupPC_restore:
>
> According to 'gitk' I applied your BackupPC_restore patch to the
> master branch of Backuppc in commit e0f8e3b on 24 October 2025.
>
> > BackupPC_dump:
>
> I vaguely remember that we discussed this and that I said while I was
> happy enough with the _restore patch, the _dump patch is *much* more
> intrusive in that after its application it would affect every backup
> that anyone ever does. I'm not comfortable with making a change that
> affects every user's backups for a single user's convenience. However
> I suggested that there could be an alternative - that would be to add
> another user-defined command, which would be undef for everyone else,
> but that would be defined for you. Your system would use this other
> user-defined command and nobody else would need to know it was there.
> BackupPC_dump would just test for $Conf{Matt-defined-command} at the
> appropriate place. If it's undef, it's a NO-OP. If it's set, then
> BackupPC_dump would try to execute it.
>
> Does that sound like something for which you could submit a patch?
>
> --
> 73,
> Ged.
>
>
> _______________________________________________
> BackupPC-users mailing list
> [email protected]
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
