From: Attila Lendvai <attila@lendvai.name>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54215@debbugs.gnu.org
Subject: [bug#54215] [PATCH Shepherd] service: Add #:rlimits parameter to 'exec-command' & co.
Date: Tue, 01 Mar 2022 18:35:47 +0000 [thread overview]
Message-ID: <ZOcTGAkar68OcuV6P3Mo-h9KAM5drKW7GlswHK9EPoVlse-MbWIp0IdmwQ41BDxi8yLY9SdNrY0qeoPpP14fe8ALj5PnVRnExsqUYXwBmDE=@lendvai.name> (raw)
In-Reply-To: <48526d32a684a531940b59edcfb016ab81c7d3bb.camel@telenet.be>
> I think it would be better to verify if rlimits is well-formed
> before forking, to let exception reporting work better. WYDT?
now that i have a reaconable edit-build-test cycle for shepherd, i'm planning to
clean up shepherd error reporting and logging, so that when an error occur then
there's a proper backtrace in the shepherd logs.
i'd rather work on that instead. does that sound reasonable?
but feel free to tailor this as you see fit!
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Don’t be a slave to your own ignorance. Know where your opinions, especially the strongly held ones, came from and be brave enough to question them.”
— Dean van Drasek
next prev parent reply other threads:[~2022-03-01 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 18:12 [bug#54215] [PATCH Shepherd] service: Add #:rlimits parameter to 'exec-command' & co Attila Lendvai
2022-03-01 18:26 ` Maxime Devos
2022-03-01 18:32 ` Maxime Devos
2022-03-01 18:35 ` Attila Lendvai [this message]
2022-03-01 18:38 ` Maxime Devos
2022-03-01 19:17 ` Attila Lendvai
2022-03-01 19:46 ` Maxime Devos
2022-03-04 8:29 ` Attila Lendvai
2022-03-21 12:48 ` bug#54215: " 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
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='ZOcTGAkar68OcuV6P3Mo-h9KAM5drKW7GlswHK9EPoVlse-MbWIp0IdmwQ41BDxi8yLY9SdNrY0qeoPpP14fe8ALj5PnVRnExsqUYXwBmDE=@lendvai.name' \
--to=attila@lendvai.name \
--cc=54215@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).