Re: [rdiff-backup-users] AF_UNIX path too long

[Troels Arvin]

On Mon, 2003-01-13 at 19:02, dean gaudet
<address@hidden> wrote:
> > What could be wrong?
> 
> rdiff-backup is attempting to create a socket in the mirror hierarchy to
> be a place holder for the socket on the primary server.
> 
> AF_UNIX socket filenames are traditionally limited to some pitifully short
> length.  it's whatever can fit in a struct sockaddr_un -- 108 chars in my
> linux headers, shorter on other systems i believe.
> 
> and since your mirror hierarchy has some extra path info at the start of
> the filename you're exceeding this limit.

I have now got the patch at
http://mail.nongnu.org/archive/html/rdiff-backup-users/2002-10/msg00003.html 
applied both at the backup and the backed up server (in my previous mails, I 
only had it applied on the backup server). The error message is now:

Error 'Socket error: (22, 'Invalid argument')' processing
chroot/named/dev/log
Skipping chroot/named/dev/log because of previous error

The resulting socket name on the backup host would be
/home/backup/xxxxxxxxxxxxxxxxxxxx/chroot/named/dev/log, i.e. 55 chars.

Strange.

On freebsd 4.5, the max socket path name seems to be 104 chars
(/usr/include/sys/un.h). In Red Hat Linux 8, the limit seems to be 108
chars, as Dean noted.
Maybe, the socket filename length is not the base of this problem, after
all.

-- 
Greetings from Troels Arvin, Copenhagen, Denmark