From: Maxime Devos <maximedevos@telenet.be>
To: Jacob Hrbek <kreyren@rixotstudio.cz>, guile-user@gnu.org
Subject: Re: How to capture pid of (system process?
Date: Fri, 17 Dec 2021 06:45:16 +0000 [thread overview]
Message-ID: <65c741f569c6a5150278f0fe3725cf21c1cf7153.camel@telenet.be> (raw)
In-Reply-To: <45d70782-ec32-355d-9ecd-44e0dc8de4e8@rixotstudio.cz>
Jacob Hrbek schreef op vr 17-12-2021 om 01:32 [+0000]:
> Can you elaborate? (I am a noob in guile atm)
These procedures are documented in the manual of Guile,
you could look in the source code of Shepherd and Guix
for examples. Most of these procedures are based on POSIX
functions, so you could look at the documentation of the
corresponding POSIX functions for the general concept.
Greetings,
Maxime
next prev parent reply other threads:[~2021-12-17 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 21:01 How to capture pid of (system process? Jacob Hrbek
2021-12-14 13:05 ` Tim Van den Langenbergh
2021-12-14 13:25 ` Maxime Devos
2021-12-17 1:32 ` Jacob Hrbek
2021-12-17 6:45 ` Maxime Devos [this message]
2021-12-17 16:24 ` Timothy Sample
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65c741f569c6a5150278f0fe3725cf21c1cf7153.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-user@gnu.org \
--cc=kreyren@rixotstudio.cz \
/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.
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).