Received: by 10.42.62.69 with SMTP id x5mr968798ich.24.1352223510778;
        Tue, 06 Nov 2012 09:38:30 -0800 (PST)
X-BeenThere: bup-list@googlegroups.com
Received: by 10.42.84.2 with SMTP id j2ls1609919icl.0.gmail; Tue, 06 Nov 2012
 09:38:29 -0800 (PST)
Received: by 10.42.152.201 with SMTP id j9mr952676icw.12.1352223509160;
        Tue, 06 Nov 2012 09:38:29 -0800 (PST)
Received: by 10.42.152.201 with SMTP id j9mr952675icw.12.1352223509147;
        Tue, 06 Nov 2012 09:38:29 -0800 (PST)
Return-Path: <stefan.bul...@gmail.com>
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174])
        by gmr-mx.google.com with ESMTPS id d5si1648427iga.1.2012.11.06.09.38.29
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 06 Nov 2012 09:38:29 -0800 (PST)
Received-SPF: pass (google.com: domain of stefan.bul...@gmail.com designates 209.85.214.174 as permitted sender) client-ip=209.85.214.174;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of stefan.bul...@gmail.com designates 209.85.214.174 as permitted sender) smtp.mail=stefan.bul...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ob0-f174.google.com with SMTP id uo13so801609obb.5
        for <bup-list@googlegroups.com>; Tue, 06 Nov 2012 09:38:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=rjgjGJiwKIuhnT1IrSFfnYkYdSMddUDy2s7jnnZwAWQ=;
        b=AzkArlS086HU7tR6lZVG3SEI8IfQPPVQlAZJtixSMJfBJMtJweeKUOHqTNc6wTxmSY
         xelSI1l1Nm5ukBGFBqi+9SzKzHQs+vMSAK7Z6bOAKWmTiAWjomcZbB2o4re5bSyFYuID
         kaJyZwQzAbkHBImqpuILF7oKC8r80r8SPwAHp8BaUmZmrP65g6KxsbLjqnqyiXdHHayz
         sU3SVjnsH4+8Wpf4uytTSs/QxhHM0LtnsTbYw8RU9xVTCKvlzn4wIRqsck8AZSIWFRzW
         WcY6pDcw5ZWZ28e18azFaOafQr6vg3dqknawN4pREqUfC3/JqAfusYufKJVSLJ9AEXOA
         6UaA==
Received: by 10.60.19.202 with SMTP id h10mr1406472oee.99.1352223508913; Tue,
 06 Nov 2012 09:38:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.71.36 with HTTP; Tue, 6 Nov 2012 09:38:08 -0800 (PST)
From: Stefan Buller <stefan.bul...@gmail.com>
Date: Tue, 6 Nov 2012 11:38:08 -0600
Message-ID: <CABvFyRuUjGSSKLhp2snMiP0UA1m5wcRrxVF4UWOPzdOv3TK...@mail.gmail.com>
Subject: FUSE reload
To: bup-list@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8ff1c620e7df3904cdd7110e

--e89a8ff1c620e7df3904cdd7110e
Content-Type: text/plain; charset=UTF-8

bup fuse currently ignores new commits once it's started. I'm serving up my
bup fuse with samba, and as a result need to manually restart fuse whenever
I make a commit. This is complicated by processes holding the fs open. I'm
planning to deal with this with a 'fuser -mk $MOUNTPOINT'. I'm not terribly
worried about data loss here, but there is a race condition.

There are a few solutions that could help here:
1. Have bup fuse watch for new commits, reloading when necessary
2. Have bup fuse register itself in the BUP_DIR, and have bup save force a
reload
3. Provide a means (-HUP) to manually force a reload.

All of this requires code for reloading or attaching new commits in the
fuse layer of bup. I, unfortunately, don't feel prepared to tackle this
myself. I feel that this is beyond my understanding of the code, and am
working on other projects at the moment.

-- 
Stefan Buller

--e89a8ff1c620e7df3904cdd7110e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

bup fuse currently ignores new commits once it&#39;s started. I&#39;m servi=
ng up my bup fuse with samba, and as a result need to manually restart fuse=
 whenever I make a commit. This is complicated by processes holding the fs =
open. I&#39;m planning to deal with this with a &#39;fuser -mk $MOUNTPOINT&=
#39;. I&#39;m not terribly worried about data loss here, but there is a rac=
e condition.<div>

<br></div><div>There are a few solutions that could help here:</div><div>1.=
 Have bup fuse watch for new commits, reloading when necessary</div><div>2.=
 Have bup fuse register itself in the BUP_DIR, and have bup save force a re=
load</div>

<div>3. Provide a means (-HUP) to manually force a reload.</div><div><br></=
div><div>All of this requires code for reloading or attaching new commits i=
n the fuse layer of bup. I, unfortunately, don&#39;t feel prepared to tackl=
e this myself. I feel that this is beyond my understanding of the code, and=
 am working on other projects at the moment.<br clear=3D"all">

<div><br></div>-- <br>Stefan Buller<br>
</div>

--e89a8ff1c620e7df3904cdd7110e--