summaryrefslogtreecommitdiff
path: root/tickets/20bdae3913de49d4afd544d36996ce4b/Maildir/new/1455999012.M515964P17339Q246.exolobe1
blob: 4d380f19bb32998fcfa05cea6f1b1cda46bd81b0 (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
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 526C42D9C2
	for <distix@pieni.net>; Sun, 11 Oct 2015 10:25:29 +0200 (CEST)
Received: from platypus.pepperfish.net (unknown [10.112.100.20])
	by bagpuss.pepperfish.net (Postfix) with ESMTP id BEAE02C4;
	Sun, 11 Oct 2015 09:25:28 +0100 (BST)
Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
	by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
	id 1ZlBwe-0004E4-Lc; Sun, 11 Oct 2015 09:25:28 +0100
Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net)
 by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
 id 1ZlBwd-0004Dx-1M
 for <obnam-dev@obnam.org>; Sun, 11 Oct 2015 09:25:27 +0100
Received: from pieni.net ([95.142.166.37] ident=postfix)
 by mx0.pepperfish.net with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <liw@liw.fi>) id 1ZlBwb-0005ZH-5p
 for obnam-dev@obnam.org; Sun, 11 Oct 2015 09:25:26 +0100
Received: from exolobe1.liw.fi (82-181-8-107.bb.dnainternet.fi [82.181.8.107])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by pieni.net (Postfix) with ESMTPSA id C4BF22D9C2;
 Sun, 11 Oct 2015 10:25:17 +0200 (CEST)
Received: from exolobe1.liw.fi (localhost [127.0.0.1])
 by exolobe1.liw.fi (Postfix) with ESMTPS id 15E774084D;
 Sun, 11 Oct 2015 11:25:17 +0300 (EEST)
Date: Sun, 11 Oct 2015 11:25:16 +0300
From: Lars Wirzenius <liw@liw.fi>
To: Ben Boeckel <mathstuf@gmail.com>
Message-ID: <20151011082515.GM2384@exolobe1.liw.fi>
References: <20150918050247.GA8128@bronto-burt.dev.benboeckel.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20150918050247.GA8128@bronto-burt.dev.benboeckel.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Score: -3.4
X-Spam-Score-int: -33
X-Spam-Bar: ---
X-Scanned-By: pepperfish.net, Sun, 11 Oct 2015 09:25:26 +0100
X-Spam-Report: Content analysis details: (-3.4 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.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
 [score: 0.0000]
X-ACL-Warn: message may be spam
X-Scan-Signature: e606bea56426b7460dd1a96e279d41e5
Cc: obnam-dev@obnam.org
Subject: Re: obnam should take an inhibitor lock during backup
X-BeenThere: obnam-dev@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
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 Fri, Sep 18, 2015 at 01:02:47AM -0400, Ben Boeckel wrote:
> During a backup, it would be nice to have obnam block suspending the
> machine. This can be done via logind's DBus API[1].

To me, this sounds like it'd be more useful to have a generic command
to run a process and prevent the machine from suspending until the
process has ended. Something like:

    nosuspend [options] [--] command [options] [args]...

Example:

    nosuspend obnam backup

This way, there wouldn't be any need for suspend blocking code in
every command line utility.

What do you think?

-- 
Schrödinger's backup hypothesis: the condition of any backup is
undefined until a restore is attempted. -- andrewsh

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