public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] PAM: Delete old lib and symlinks
Date: Sun, 18 Mar 2018 14:00:01 +0100	[thread overview]
Message-ID: <1521378001.10696.2.camel@ipfire.org> (raw)
In-Reply-To: <1521377731-4322-1-git-send-email-erik.kapfer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

Hi,
problem on Core 119 with a not working PAM has been reported in the forum 
which we could solve like described in here 
https://forum.ipfire.org/viewtopic.php?f=22&t=20480

Best,

Erik

Am Sonntag, den 18.03.2018, 13:55 +0100 schrieb Erik Kapfer:
> Core 119 update delivers an updated PAM whereby the libdir has been
> changed from /lib to /usr/lib
> but the old libraries and symlinks are still presant. Since the
> system searches /lib before
> /usr/lib , the old libs and symlinks are used which ends up in an
> `LIBPAM_EXTENSION_1.1' not found.
> 
> Signed-off-by: Erik Kapfer <erik.kapfer(a)ipfire.org>
> ---
>  config/rootfiles/core/120/update.sh | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/config/rootfiles/core/120/update.sh
> b/config/rootfiles/core/120/update.sh
> index 2f1bca0..02f2ad0 100644
> --- a/config/rootfiles/core/120/update.sh
> +++ b/config/rootfiles/core/120/update.sh
> @@ -34,6 +34,11 @@ done
>  # Remove forgotten PHP file
>  rm -f /etc/httpd/conf/conf.d/php5.conf
>  
> +# Delete old PAM libs and symlinks if presant
> +if ls /lib | grep -q 'libpam.*'; then
> +    rm -f /lib/libpam*
> +fi
> +
>  # Stop services
>  
>  # Extract files

  reply	other threads:[~2018-03-18 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 12:55 Erik Kapfer
2018-03-18 13:00 ` ummeegge [this message]
2018-03-18 13:43   ` Michael Tremer
2018-03-18 15:13     ` ummeegge

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=1521378001.10696.2.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox