all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: muradm <mail@muradm.net>
To: 49771@debbugs.gnu.org
Subject: bug#49771: conflicting pam-limits-service and pam-mount-service-type
Date: Thu, 29 Jul 2021 19:13:34 +0300	[thread overview]
Message-ID: <87v94tcd3l.fsf@muradm.net> (raw)


pam-limits-service and pam-mount-service-type are working when 
used only one of them. When both are present in list of (services, 
conflict hapens when guix system reconfigure is invoked. Digging 
the problem led to use of etc-service-type.

pam-limits-service defines /etc/security/limits.conf in 
gnu/services/base.scm:

(define pam-limits-service-type
  (let ((security-limits
         ;; Create /etc/security containing the provided 
         "limits.conf" file.
         (lambda (limits-file)
           `(("security"
              ,(computed-file
                "security"
                #~(begin
                    (mkdir #$output)
                    (stat #$limits-file)
                    (symlink #$limits-file
                             (string-append #$output "/limits.conf"))))))))
        (pam-extension
         (lambda (pam)

Basically, it says to etc-service-type i need "security" under 
"/etc" and uses mkdir to create it.

pam-mount-service-type asks "security/pam_mount.conf.xml" from 
etc-service-type.

(define (pam-mount-etc-service config)
  `(("security/pam_mount.conf.xml"
     ,(make-pam-mount-configuration-file config))))

When both pam-mount-service-type and pam-limits-service are 
defined in (services ...), if pam-mount-service-type is before 
pam-limits, guix system reconfigure fails with "Permission 
denied", if pam-limits is before then it is "File exists".

I would suggest to fix gnu/services/base.scm so that 
pam-limits-services-type ask for "security/limits.conf" just like 
pam-mount-services-type does in order to avoid conflict.

Currently, both pam-limits-service and pam-mount-service-type are 
not usable at the same time.




                 reply	other threads:[~2021-07-30  4:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87v94tcd3l.fsf@muradm.net \
    --to=mail@muradm.net \
    --cc=49771@debbugs.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.