From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: (Exposing?) config files and non-start/stop operations Date: Tue, 22 Nov 2016 21:28:13 -0800 Message-ID: <878tsau5n6.fsf@gmail.com> 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: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54847) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9Q6U-0001yr-3L for guix-devel@gnu.org; Wed, 23 Nov 2016 00:28:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9Q6T-0003J2-Ae for guix-devel@gnu.org; Wed, 23 Nov 2016 00:28:18 -0500 Received: from mail-pg0-x231.google.com ([2607:f8b0:400e:c05::231]:33225) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c9Q6T-0003IQ-2m for guix-devel@gnu.org; Wed, 23 Nov 2016 00:28:17 -0500 Received: by mail-pg0-x231.google.com with SMTP id 3so1812267pgd.0 for ; Tue, 22 Nov 2016 21:28:16 -0800 (PST) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Christopher Allan Webber Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Chris, Thank you for taking the time to clarify the motivation! It helped a lot. Christopher Allan Webber writes: > The command you *want* to run is something like: > > `foo-db dumpdb --config=3D/path/to/foodb.cfg' > > Now... your GuixSD system has, somewhere buried in it, a config file > that it passes in when shepherd starts/stops the daemon. It's somewhere > in /gnu/store/ ... but you don't know where it is! This is the information I was missing. If your service/daemon/tool requires that information to be supplied on the command line, then I can see why it would be convenient to model the task as a Shepherd action. I think that would be useful. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYNSjtAAoJEN1AmhXYIkadRGUQAKepvW6w38iNaFUwn6zqcVmg 9/A4TRGcIuu9YshxvKVZkP444NAlTGxY4AdgAnDv+UBxw8JjoETRPDzvi+vZffSz stnYnmPg4Op3q0IoTyHT94zTlwTOWNmLWV8UVko+nWIIo5qlYh7wVkphlFf8VabW 4rLiuGEdfPDxB1R85Vr1yEaHkEoyGORM7MWtYjD59JlUwBebEpkrwpk4hHTMyylu 6QN40lOa1nfPAWfuZ0yVHEMbnWUo1DghG4uRkYACsdVYomtb4Glp/X5In/rDbbDz aGFjXQQmcM6XOwWxxyprveWKQVabMy066ggUvROj8d6NEytp4p8vrNLC2LAGPHXF b33aVdwsbanudSKn3gHH9ZrbTyfv8Bru2ak66CBru018GDfH0vg4nXx/1vj9qxb+ PYLiH0K0oqOgF+2SGwvdRSqnyDhNyELKPKbOvaVnUZLE/EcZczRIRKdS3R7gGapa OKTKyhSI7m3p+jpFU3T4klUMK+zBySOZjoPZX8HcFKYHXOQSI2vv24RXhOzD6z8A b0lminX8WqGF3oBsowga4lwNu3SMpOxiSVwGKYBJdEq2p8RTrv+hyCyTru8z62av d2nsRhamzkRD7HlhcAnRMuHJU7jzNNZAb2h2keG+ljxJEYehu66InPU5zjFrd5mE 5jsEugV463aeDP6C56eH =kLeT -----END PGP SIGNATURE----- --=-=-=--