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

On Sun, 2 May 2021 22:51:14 +0200
Denis Corbin <[email protected]> wrote:

> On 02/05/2021 20:01, imschmeg wrote:
> > I am getting this error during extraction of an archive of an
> > encrypted file system (each file and its filename are encrypted
> > separately, that's why the long jibberish filenames). The source
> > and destination are the same f2fs file system on Debian stable
> > 10.9.  The original socket name works, so why can't dar extract
> > that same name?  Is this a problem specific to sockets?  Is it a
> > problem with dar's understanding of the f2fs filesystem?  There are
> > many other much longer pathnames in this backup that were extracted
> > without issue, but this was the only socket.  
> 
> this messages is issued by dar because the filename exceed the system
> constant UNIX_PATH_MAX defined by your operating system.
> 
> The problem here is portability, not all system define such constant
> and when it is not defined, libdar uses a somehow very restrictive
> value that was known to work for every system.

Is there any way to override the value dar uses in place of
UNIX_PATH_MAX? It seems that it isn't defined in Debian.

This is just in case I hit this issue again with backups of this kind
of encrypted file system, where I have no control over pathname length.

Thanks!