summaryrefslogtreecommitdiff
path: root/tickets/20bdae3913de49d4afd544d36996ce4b/Maildir/new/1456001178.M44641P8737Q19.hrun
blob: e260e3ebc6085b6250dc62efaf5600d66773c159 (plain)
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
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 1383B2B7AA
	for <distix@pieni.net>; Mon, 21 Dec 2015 16:22:43 +0100 (CET)
Received: from platypus.pepperfish.net (unknown [10.112.100.20])
	by bagpuss.pepperfish.net (Postfix) with ESMTP id 9B00AB9F;
	Mon, 21 Dec 2015 15:22:42 +0000 (GMT)
Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
	by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
	id 1aB2IM-0000Jv-H6; Mon, 21 Dec 2015 15:22:42 +0000
Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net)
 by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
 id 1aB2IK-0000Jp-NP
 for <obnam-dev@obnam.org>; Mon, 21 Dec 2015 15:22:40 +0000
Received: from mail-io0-f179.google.com ([209.85.223.179])
 by mx0.pepperfish.net with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128)
 (Exim 4.80) (envelope-from <mathstuf@gmail.com>) id 1aB2II-0003La-UF
 for obnam-dev@obnam.org; Mon, 21 Dec 2015 15:22:40 +0000
Received: by mail-io0-f179.google.com with SMTP id q126so157234801iof.2
 for <obnam-dev@obnam.org>; Mon, 21 Dec 2015 07:22:33 -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=+FtE6gdbIMxEr+TFbcSoG/6lVHi8CvkW8sCMOepZKtQ=;
 b=HCnwYJJsry369EK5+fuo45fiLCVsI3GeDbKgQjKfT1sh8XoHQUjt5p0wezk2BSx0gQ
 5BbXC2JGteWFYIa4W4Qf9ojMEfh+CFqqj+lYQZfW1180SVnaxRadB+h8hy5PUU79/BB9
 1ZvSJobjMKdoixwS+VZ0SSXdR49gSrttN9pQ0358fevEQpAvHtbTs8YgaKW3J/br9DGa
 If59pmU9dWwZgaHXzfXWXqsqo7q6z3/0yKOirlR73TjeLgXcbTBqvVmCUKebvELzA1Vj
 cV+WZK0ZUeSPzkFFaQqAJX2p5GmOu2cGGj0Gp55mNADU1Tw2FSX31h1Vlqc6cv1UB7CB
 sx8w==
X-Received: by 10.107.27.6 with SMTP id b6mr20166383iob.163.1450711346636;
 Mon, 21 Dec 2015 07:22:26 -0800 (PST)
Received: from megas (tripoint.kitware.com. [66.194.253.20])
 by smtp.gmail.com with ESMTPSA id i195sm10429478ioe.19.2015.12.21.07.22.24
 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Mon, 21 Dec 2015 07:22:25 -0800 (PST)
Date: Mon, 21 Dec 2015 10:22:24 -0500
From: Ben Boeckel <mathstuf@gmail.com>
To: Lars Wirzenius <liw@liw.fi>
Message-ID: <20151221152224.GA21839@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20151220141633.GE2511@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, Mon, 21 Dec 2015 15:22:40 +0000
X-Spam-Report: Content analysis details: (-2.0 points)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -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
 -0.7 RCVD_IN_DNSWL_LOW      RBL: Sender listed at http://www.dnswl.org/, low
 trust [209.85.223.179 listed in list.dnswl.org]
X-ACL-Warn: message may be spam
X-Scan-Signature: 414f5f03ee092b3fac588a5aec0a9d93
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 Sun, Dec 20, 2015 at 15:16:33 +0100, Lars Wirzenius wrote:
> I'm not entirely sure I'm comfortable adding this kind of code to
> Obnam. I think it'd be better off as a separate utility, kind of like
> the flock utility. It could be used like this:
> 
>     inhibit-suspend obnam backup
> 
> Such a utility would be more generic than code specifically in Obnam.

This tool already exists as `systemd-inhibit`. The problem is that it
needs numerous arguments to be useful (the name of the program, the
locks to take, a reason for taking the lock, etc.). I don't see this as
any different than video players taking the XSS lock to inhibit
screensavers: it's just expected behavior that the screen doesn't lock
when a video is playing just as suspending in the middle of a backup is
not something I think anyone would expect (or want barring power-down
due to low battery or a failing UPS).

--Ben

_______________________________________________
obnam-dev mailing list
obnam-dev@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org