Re: [Duplicity-talk] Backup of socksets

[Alex Jakushev]

Hi all.

There's actually another side of the problem to it. I use duplicity
from cron, and if something gets onto stderr, i get a mail
notification. Every time I run duplicity, it prints "Error initializing ..."
to stderr, and every time I get e-mail, even if everything is OK.

I tried to avoid this problem this way:

1) one of parameters for duplicity was
  --exclude-globbing-filelist somefile,
 where somefile contains one full filename
 per line.
2) This file has many entries, soem of them are
 files, some of them are pipes or sockets.

The problem is that duplicity does not exclude sockets,
specified in this exclude file (normal files are excluded OK). I
understand that backuping sockets is not a good idea,
however, I think that unability to exclude them somehow
is a BUG.

If anyone could help with the issue, it would be great :)

On 5/11/07, Gabriel Ambuehl <address@hidden> wrote:
> On Friday 11 May 2007 19:22:26 Alexander Skwar wrote:
> >
> > Would it be possible to enhance duplicity in such a way, that it
> > backups these files as well?
>
> I don't think you actually can backup sockets very well: they are useless
> without the app that created them (think of them as something very close to
> TCP/IP sockets) and the current state of that app and you
> most certainly can't have duplicity back up runtime apps and their states.
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk


--
Best regards,

Alex J.