1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
|
Return-Path: <obnam-dev-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from bagpuss.pepperfish.net (bagpuss.pepperfish.net [148.251.8.16])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pieni.net (Postfix) with ESMTPS id 578BD2B99B
for <distix@pieni.net>; Tue, 22 Dec 2015 15:01:16 +0100 (CET)
Received: from platypus.pepperfish.net (unknown [10.112.100.20])
by bagpuss.pepperfish.net (Postfix) with ESMTP id A38BEB8E;
Tue, 22 Dec 2015 14:01:15 +0000 (GMT)
Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1aBNV5-0000gV-HL; Tue, 22 Dec 2015 14:01:15 +0000
Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1aBNV4-0000gH-Ld
for <obnam-dev@obnam.org>; Tue, 22 Dec 2015 14:01:14 +0000
Received: from mail-ig0-f173.google.com ([209.85.213.173])
by mx0.pepperfish.net with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128)
(Exim 4.80) (envelope-from <mathstuf@gmail.com>) id 1aBNUv-0000fe-H7
for obnam-dev@obnam.org; Tue, 22 Dec 2015 14:01:14 +0000
Received: by mail-ig0-f173.google.com with SMTP id m11so50031060igk.1
for <obnam-dev@obnam.org>; Tue, 22 Dec 2015 06:01:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=date:from:to:cc:subject:message-id:reply-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
bh=miBj3gG1+cGdOfvPqhQ7viKQU49ZtxTsky/Y1FK9LdY=;
b=v2z6DWl4jRcYNJOYPk5xS5SUu9h98MW0R83LZE/ysd78+Vx0JbO3fj7xu6DXrFc8xY
cFmAGwz62FlM/GSf8lCxIRAum9ogBsc3Okuo+bMiJCNGLdhcevPhVUeF+zOVfmG3y5We
2zUEU2+Zze/n1l+WCI4sxLOhKme2Ks9WsfgA3+RN5ji+A/C5qnNn/ecqkZQyb8lF45jq
YP2IiRtxuiBMLcWk3FaPwEK8MbqZIkP5pVtdbONc3EDewLy4rNCozpM3vr9SHYxGyhmP
yYU7mItsy1PJ+3KULLZn3ZHAfBhcjhy2w83DOBbcLickfFNAcR6J3sNzm7NGKxAbjFja
1nkg==
X-Received: by 10.50.12.36 with SMTP id v4mr13616478igb.6.1450792853200;
Tue, 22 Dec 2015 06:00:53 -0800 (PST)
Received: from megas (tripoint.kitware.com. [66.194.253.20])
by smtp.gmail.com with ESMTPSA id 129sm12778045ioo.23.2015.12.22.06.00.51
(version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Tue, 22 Dec 2015 06:00:52 -0800 (PST)
Date: Tue, 22 Dec 2015 09:00:51 -0500
From: Ben Boeckel <mathstuf@gmail.com>
To: Lars Wirzenius <liw@liw.fi>
Message-ID: <20151222140051.GB11335@megas.khq.kitware.com>
References: <20150918050247.GA8128@bronto-burt.dev.benboeckel.net>
<1446094196-14166-1-git-send-email-mathstuf@gmail.com>
<20151029045526.GA13909@bronto-burt.dev.benboeckel.net>
<20151220141633.GE2511@exolobe1.liw.fi>
<20151221152224.GA21839@megas.khq.kitware.com>
<20151221153318.GR2511@exolobe1.liw.fi>
<20151221161706.GD21839@megas.khq.kitware.com>
<20151221165932.GS2511@exolobe1.liw.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20151221165932.GS2511@exolobe1.liw.fi>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Spam-Score: -2.0
X-Spam-Score-int: -19
X-Spam-Bar: --
X-Scanned-By: pepperfish.net, Tue, 22 Dec 2015 14:01:14 +0000
X-Spam-Report: Content analysis details: (-2.0 points)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust [209.85.213.173 listed in list.dnswl.org]
-1.0 PPF_USER_AGENT_MUTT User-Agent: contains Mutt (Mutt isn't a spam
tool) -0.5 PPF_USER_AGENT User-Agent: exists
1.0 PPF_FROM_CONTAINS_MAIL The From header contains 'mail'
1.2 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mathstuf[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-ACL-Warn: message may be spam
X-Scan-Signature: 439c9db7d537d78073733ee67505cfd7
Cc: obnam-dev@obnam.org
Subject: Re: [PATCH] backup: take an inhibitor lock if possible
X-BeenThere: obnam-dev@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mathstuf@gmail.com
List-Id: Obnam development discussions <obnam-dev-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-dev-obnam.org>
List-Post: <mailto:obnam-dev@obnam.org>
List-Help: <mailto:obnam-dev-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=subscribe>
Sender: obnam-dev-bounces@obnam.org
Errors-To: obnam-dev-bounces@obnam.org
On Mon, Dec 21, 2015 at 17:59:32 +0100, Lars Wirzenius wrote:
> On Mon, Dec 21, 2015 at 11:17:06AM -0500, Ben Boeckel wrote:
> > On Mon, Dec 21, 2015 at 16:33:18 +0100, Lars Wirzenius wrote:
> > > That just indicates to me that you should write a simpler program,
> > > perhaps as a wrapper around systemd-inhibit. :)
> >
> > Would this at least be acceptable to include in obnam? obnam-inhibit? It
> > seems silly to have everyone rewrite this thing when it is such an
> > important behavior.
>
> I'd rather it was a separate, generic utility than something named so
> people think it's related to Obnam, sorry. I'd be happy to add
> pointers to it to Obnam documentation, and have the Obnam Debian
> packaging suggest it.
Wait, so let me get this straight:
- adding it to obnam is too specific;
- using systemd-inhibit is too generic (needs enough parameters that
manually typing it is annoying);
- so making something *like* obnam-inhibit is the right way;
- but instead of having obnam provide such a thing, everyone has to
make their own?
Making a full-blown repo for a single script with the content of:
#!/bin/sh
exec systemd-inhibit --who=obnam --why="running a backup" obnam "$@"
seems a little absurd to me.
> There are other forms of composability than pipes. For example, the
> flock(1) utility, which creates a lock file while it runs a command,
> and automatically releases it even if it crashes. That's the same
> pattern as I suggest for the inhibition utility.
>
> That said, I expect Obnam to start reading from stdin some day. And
> produce output to stdout. Both for using in pipelines. Examples:
>
> * Have Obnam read the list of files to back up from stdin, fed by,
> say, find(1).
>
> * Have "obnam export-repository" produce a representation of a backup
> repository that is independent of the backup storage format, and
> "obnam import-repository" read such a representation to create a new
> repository. This would be quite useful for repository conversion.
Well, this one isn't "backup", and for the first one, I'd want the
inhibitor lock as well. And the pipe-in-find is probably better as
--files-from=- (plus the associated -0 flag for using null-delimited
filenames) since a flag to even look at stdin would probably be needed
*anyways*.
--Ben
_______________________________________________
obnam-dev mailing list
obnam-dev@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org
|
