From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH] package/linux-pam: adjust login pam file for lastlog
Date: Tue, 29 Oct 2024 22:35:10 +0100 [thread overview]
Message-ID: <20241029223510.3aa46a4c@windsurf> (raw)
In-Reply-To: <20241001092057.612830-1-buildroot@heine.tech>
On Tue, 1 Oct 2024 11:20:55 +0200
Michael Nosthoff via buildroot <buildroot@buildroot.org> wrote:
> when pam_lastlog.so is not installed login issues an error
> that it is not able to load it.
>
> Hence only enable the entry when pam_lastlog.so is installed.
>
> Fixes:
> login[649]: PAM unable to dlopen(/lib/security/pam_lastlog.so): /lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
> login[649]: PAM adding faulty module: /lib/security/pam_lastlog.so
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> ---
> package/linux-pam/linux-pam.mk | 5 +++++
> package/linux-pam/login.pam | 2 +-
> 2 files changed, 6 insertions(+), 1 deletion(-)
Applied to master, thanks. It would be really good to have runtime
tests to test this kind of packages, with its different
features/options.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-29 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 9:20 [Buildroot] [PATCH] package/linux-pam: adjust login pam file for lastlog Michael Nosthoff via buildroot
2024-10-29 21:35 ` Thomas Petazzoni via buildroot [this message]
2024-11-20 20:45 ` Peter Korsgaard
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=20241029223510.3aa46a4c@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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 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.