From: David Craven <david@craven.ch>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 8/8] services: Add spice vdagent service.
Date: Sat, 30 Jul 2016 12:29:34 +0200 [thread overview]
Message-ID: <CAL1_imm7_cWoRpAL8tJErgOjV6ph3TT1JQYXd+GqS8_b1Oia-w@mail.gmail.com> (raw)
In-Reply-To: <CAL1_imkg7eiJ-CS802pP9s9Jnw8Tm4vQbtEunrPEdbiMoBw66A@mail.gmail.com>
> If spice-vdagend produces a PID file, make sure to use #:pid-file here
> (there are several examples in the tree), which often provides more
> reliable startup notification.
I'm passing the -x flag which prevents spice-vdagentd from
daemonizing. I thought that make-forkexec-constructor took care of
setting the correct stdout stderr stdin user process-parent and pid
file automatically. Is that not the way it's intended to be used?
Because otherwise a (system*) call would be enough wouldn't it?
next prev parent reply other threads:[~2016-07-30 10:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 8:23 [PATCH 1/8] gnu: qt: Update to 5.6.1-1 David Craven
2016-07-29 8:23 ` [PATCH 2/8] gnu: Use define-public to export packages David Craven
2016-07-29 15:35 ` Ludovic Courtès
2016-07-29 8:23 ` [PATCH 3/8] gnu: Remove trailing periods from synopsis David Craven
2016-07-29 15:38 ` Ludovic Courtès
2016-07-29 8:23 ` [PATCH 4/8] gnu: freedesktop: Add libinput-minimal David Craven
2016-07-29 11:25 ` Vincent Legoll
2016-07-29 12:53 ` David Craven
2016-07-29 13:13 ` Vincent Legoll
2016-07-29 15:40 ` Ludovic Courtès
2016-07-29 8:23 ` [PATCH 5/8] gnu: xorg: Add xf86-video-qxl David Craven
2016-07-29 15:42 ` Ludovic Courtès
2016-07-29 8:23 ` [PATCH 6/8] gnu: Order module imports in (gnu packages qemu) alphabetically David Craven
2016-07-29 15:44 ` Ludovic Courtès
2016-07-29 16:26 ` David Craven
2016-07-29 8:23 ` [PATCH 7/8] gnu: qemu: Enable spice support David Craven
2016-07-29 19:10 ` Ludovic Courtès
2016-07-29 19:12 ` David Craven
2016-07-30 12:47 ` Ludovic Courtès
2016-07-29 8:23 ` [PATCH 8/8] services: Add spice vdagent service David Craven
2016-07-29 19:16 ` Ludovic Courtès
2016-07-29 19:20 ` David Craven
2016-07-30 10:29 ` David Craven [this message]
2016-07-30 22:41 ` Ludovic Courtès
2016-07-31 18:14 ` David Craven
2016-08-01 12:01 ` Ludovic Courtès
2016-07-29 19:20 ` [PATCH 1/8] gnu: qt: Update to 5.6.1-1 Ludovic Courtès
2016-07-29 19:23 ` David Craven
2016-07-30 8:57 ` Andreas Enge
2016-07-30 22:44 ` Code formatting Ludovic Courtès
2016-07-31 10:34 ` Danny Milosavljevic
2016-07-31 10:37 ` Andreas Enge
2016-07-31 10:59 ` Ludovic Courtès
2016-09-11 16:35 ` Andreas Enge
[not found] ` <20160729101510.GA30683@solar>
[not found] ` <CAL1_im=qJ3=0P=c6OhL9wW2rz4wJY3cFubute0dHWyr5ymjhsA@mail.gmail.com>
[not found] ` <CAL1_im=EbMqBufpsW2eMxYZdLWVDtmq4TD1HDKvAQ_u_RpdjXw@mail.gmail.com>
[not found] ` <20160729180053.GA1301@solar>
2016-07-30 8:53 ` [PATCH 1/8] gnu: qt: Update to 5.6.1-1 Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL1_imm7_cWoRpAL8tJErgOjV6ph3TT1JQYXd+GqS8_b1Oia-w@mail.gmail.com \
--to=david@craven.ch \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).