From: "Ludovic Courtès" <ludo@gnu.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
61744@debbugs.gnu.org, Bruno Victal <mirai@makinata.eu>
Subject: [bug#61744] [PATCH] services: base: Deprecate 'pam-limits-service' procedure.
Date: Thu, 30 Mar 2023 22:53:54 +0200 [thread overview]
Message-ID: <87jzyyhsf1.fsf_-_@gnu.org> (raw)
In-Reply-To: <CAFHYt57dM1xAHnaZC3vmhcAp0fZ+hER-bqgNjjoG-id5UV8DLQ@mail.gmail.com> (Felix Lechner's message of "Mon, 20 Mar 2023 10:49:10 -0700")
Hi Felix,
Felix Lechner <felix.lechner@lease-up.com> skribis:
> Can we refer to the limits.conf file in the store, please? I do not
> believe we need a copy in /etc/security, and should not keep one
> there.
I’m generally in favor of not populating /etc and instead referring to
store file names.
In some cases (maybe this one), this can be a problem though, in
particular for upgrades (the module keeps referring to the old config
file in the store). So I don’t know, but this needs to be taken into
account.
Ludo’.
next prev parent reply other threads:[~2023-03-30 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 0:12 [bug#61744] [PATCH] services: base: Deprecate 'pam-limits-service' procedure Bruno Victal
2023-03-04 21:17 ` [bug#61744] [PATCH v2 1/2] " Bruno Victal
2023-03-04 21:17 ` [bug#61744] [PATCH v2 2/2] services: pam-limits-service-type: Deprecate file-like object support in favour for lists as service value Bruno Victal
2023-03-10 17:52 ` [bug#61744] [PATCH v2 1/2] services: base: Deprecate 'pam-limits-service' procedure Ricardo Wurmus
2023-03-11 11:25 ` Bruno Victal
2023-03-30 21:08 ` bug#61744: [PATCH] " Ludovic Courtès
2023-03-20 17:49 ` [bug#61744] " Felix Lechner via Guix-patches via
2023-03-30 20:53 ` Ludovic Courtès [this message]
2023-03-30 21:19 ` Felix Lechner via Guix-patches via
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=87jzyyhsf1.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=61744@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=mirai@makinata.eu \
--cc=rekado@elephly.net \
/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).