Re: error restoring Unix socket ... path too long to be stored properly

On 03/05/2021 20:16, imschmeg wrote:
> On Mon, 3 May 2021 19:35:58 +0200
> Denis Corbin <[email protected]> wrote:
> 

[...]

> As long as this is just a problem with sockets, it is manageable.
> Another likely source of sockets in the homedir is in .gnupg, which I
> found in another user's homedir that I have not tested yet.  I suspect
> that gnupg won't mind if they are deleted at logout, but at least I
> have the EA-tagging technique if I need it.

yes, you can even run the find command from dar just before entering a
particular each home directory using the something like this:

dar -c backup -R / --backup-hook-include "home/*" --backup-hook-execute
"find %p -type s -exec setfattr... \;" ...other options to dar...

Well, I would not invoke "find" directly but through a small script that
would leverage the %c macro that comes with --backup-hook-execute option.

The interest of doing so appears if the time to backup is long and you
have a heavy user activity:
- it is more probable to flag all newly created sockets for the backup,
than what you get when running find first, then dar,
- the find command does not put much stress too much the disk I/O as it
concerns just an single user home directory at a time, and while this
user's file's metadata is still in cache, dar does not lead the extra
I/O to read and eventually backup these metadata.

> 
> Even if the sockets do need to be recreated on extraction, I can always
> back them up separately to a flat text file along side running dar with
> the EA-tagging.  The same find -s that adds the EA tag can write their
> encrypted pathnames and attributess to a text file.
> 
> Thanks again Denis, and thanks to Mihai as well.


You are very welcome,
Cheers,
Denis

> 
> 
> 
>