From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: [PATCH] openssh service
Date: Fri, 19 Aug 2016 16:03:35 +0200 [thread overview]
Message-ID: <20160819160335.3ed70813@polymos> (raw)
In-Reply-To: <20160805162049.491063d9@polymos>
On Fri, 5 Aug 2016 16:20:49 +0200
Julien Lepiller <julien@lepiller.eu> wrote:
> On Fri, 05 Aug 2016 15:47:50 +0200
> Andy Wingo <wingo@igalia.com> wrote:
>
> > On Fri 05 Aug 2016 14:18, Julien Lepiller <julien@lepiller.eu>
> > writes:
> > > here is a patch that adds a service definition for openssh.
> >
> > Very nice!
> >
> > > + (let ((pid (primitive-fork)))
> > > + (case pid
> > > + ((0)
> > > + (execl (string-append #$openssh "/bin/ssh-keygen")
> > > + "ssh-keygen" "-A")
> > > + (else
> > > + (zero? (cdr (waitpid pid)))))))
> >
> > I guess you could system* this one instead; would be easier I think.
> > Dunno.
>
> I modified my patch, so you can choose whichever feels better.
>
> >
> > Other than that looks all good to me. Would need an addition to the
> > manual eventually though.
>
> >
> > Andy
>
Hi,
It's been a bit of time since I posted the patch, but didn't hear any
news about it. What's wrong with it? Is it that I misunderstood the
"Would need an addition to the manual eventually though"? Does that
mean I need to add an entry to the manual myself (if so, could you
tell me what file to edit?)
next prev parent reply other threads:[~2016-08-19 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 12:18 [PATCH] openssh service Julien Lepiller
2016-08-05 13:47 ` Andy Wingo
2016-08-05 14:20 ` Julien Lepiller
2016-08-19 14:03 ` Julien Lepiller [this message]
2016-08-19 14:15 ` Vincent Legoll
2016-08-19 14:31 ` Julien Lepiller
2016-08-26 10:51 ` Andy Wingo
2016-09-26 16:42 ` Julien Lepiller
2016-09-29 21:15 ` Ludovic Courtès
2016-10-02 22:42 ` Ludovic Courtès
2016-10-03 16:01 ` Ludovic Courtès
2016-08-29 15:06 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160819160335.3ed70813@polymos \
--to=julien@lepiller.eu \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.