From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: (Exposing?) config files and non-start/stop operations
Date: Tue, 22 Nov 2016 23:59:23 +0100
Message-ID: <87lgwb86k4.fsf@gnu.org>
References: <87a8cuaszg.fsf@dustycloud.org> <878tsdbx2d.fsf@dustycloud.org>
	<87polpo2k4.fsf@gmail.com> <877f7wbyc7.fsf@dustycloud.org>
	<874m30bwpv.fsf@dustycloud.org> <87k2bwxibv.fsf@gmail.com>
	<87r363a0rx.fsf@dustycloud.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59497)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1c9K2D-00078h-Hn
	for guix-devel@gnu.org; Tue, 22 Nov 2016 17:59:30 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1c9K2A-0006w6-CZ
	for guix-devel@gnu.org; Tue, 22 Nov 2016 17:59:29 -0500
In-Reply-To: <87r363a0rx.fsf@dustycloud.org> (Christopher Allan Webber's
	message of "Tue, 22 Nov 2016 11:21:22 -0600")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org

Christopher Allan Webber <cwebber@dustycloud.org> skribis:

> Anyway, I think exposing the `actions' slot in shepherd is the way to
> go.  We could already use it for some things other than the theoretical
> examples I've given.  Last night I wanted to do something like:
>
>   sudo mcron --schedule=3D10
>
> ... which would, according to the mcron docs, show me the next ten
> upcoming tasks that are scheduled!  I wanted to verify that I was
> writing my mcron procedures right.  Likewise, my shepherd configuration
> seems obscured (well sort of, I can figure it out by looking at
> `ps auwwwx' but I don't want to do that).  It would be nice if I could
> do:
>
>   sudo herd list-schedule mcron 10
>
> Anyway, hopefully I've made my case! :)

Definitely!  :-)  This one is a good example, too.

Ludo=E2=80=99.