[Box Backup] Re: Bug#479145: boxbackup-client: Complaints about «file of unknown type» (socket)

[Chris Wilson]

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---128931150-435962140-1213984069=:29128
Content-Type: TEXT/PLAIN; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi Reinhard,

On Tue, 20 May 2008, Reinhard Tartler wrote:

> Tollef Fog Heen <tfheen@err.no> writes:
> > Hi,
> >
> > it seems like boxbackup-client doesn't know how to ignore sockets and=
=20
> > so I get lines in daemon log like:
> >
> > May  2 23:07:44 xoog Box Backup (bbackupd)[3512]: WARNING: Ignoring fil=
e of unknown type: /var/run/postgresql/.s.PGSQL.5432
> > May  2 23:07:44 xoog Box Backup (bbackupd)[3512]: WARNING: Ignoring fil=
e of unknown type: /var/run/postgresql/.s.PGSQL.5433
> >
> > This causes boxbackup-client to send email about =C2=ABfiles not being
> > backed up=C2=BB, which is quite annoying.=20
=2E..
> Now, as a workaround, you could of course add an explicit ignore in your
> boxbackup configuration to work around this issue. I'm not sure if this
> is the 'correct' way to solve this problem. TBH, I'd rather expect
> boxbackup to 'more or less' silently ignore this. I'm therefore inclined
> to change that line of code from BOX_WARNING to BOX_INFO.
>=20
> What do the boxbackup developers think of this?

I'm not sure that it's a good idea to change the warning level. Other=20
files that people might expect to be backed up, such as device nodes in=20
/dev, are also not supported and I think we should warn users about this.

However, I see zero value in backing up sockets, and I'd be quite happy to=
=20
simply ignore them. Any objections?

Cheers, Chris.
--=20
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |
---128931150-435962140-1213984069=:29128--