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: Thu, 24 Nov 2016 14:31:58 +0100 Message-ID: <87shqh57ht.fsf@gnu.org> References: <87a8cuaszg.fsf@dustycloud.org> <878tsdbx2d.fsf@dustycloud.org> <87polpo2k4.fsf@gmail.com> <877f7wbyc7.fsf@dustycloud.org> <87poln86mx.fsf@gnu.org> <87mvgpj1kq.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9u8F-0000OD-Da for guix-devel@gnu.org; Thu, 24 Nov 2016 08:32:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9u8A-0002IA-GG for guix-devel@gnu.org; Thu, 24 Nov 2016 08:32:07 -0500 In-Reply-To: <87mvgpj1kq.fsf@dustycloud.org> (Christopher Allan Webber's message of "Wed, 23 Nov 2016 16:03:49 -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 Howdy! Christopher Allan Webber skribis: > Ludovic Court=C3=A8s writes: [...] >> It=E2=80=99s also a situation where adding the config file to /etc would= be >> reasonable (until Shepherd actions can actually be added :-)). > > True. Though we still run, potentially, into problems where multiple > instances of some service are provided, eg multiple mediagoblin servers > or mail daemons or etc. Sure, definitely. All I meant was that populating /etc can be done as a quick stop-gap measure when it makes sense, but it=E2=80=99s not a great solution, notably because of the multiple-instance problem you describe. > Note: I'm interested still in exploring the shepherd actions stuff > still... though I did realize this morning that it wouldn't help in the > rare commands that have interactive input... there's no way to send > input/output in that way through the herd afaict! Oh well, that's > probably pretty rare. > > Speaking of I/O from commands, I wonder how you'd give any kind of > output back through an action to the herd? Afaict the protocol supports > it and allows sending back "messages" that will be displayed, but > nothing uses it yet. There's a record type that afaict > nothing uses at all. is used for every reply sent by the daemon, in (shepherd). However, this hasn=E2=80=99t been thought to provide interactive commands a= nd such things; I=E2=80=99m not sure it would be a great idea to support interactive commands, dunno. The protocol currently is just: you connect, you send a request, you get a reply, and you disconnect. Actions are expected to be non-blocking. Ludo=E2=80=99.