From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] pam: Update to 1.2.1
Date: Sun, 15 Nov 2015 13:07:57 +0100 [thread overview]
Message-ID: <5648759D.50505@ipfire.org> (raw)
In-Reply-To: <1447094272.2699.74.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On 09.11.2015 19:37, Michael Tremer wrote:
> I wonder if you have tested this on a clean installation. Because of
> the many so-bumps, the new libraries would probably not be used in an
> upgraded system and that won't find us the bugs
Hi Michael,
You're probably right - sorry if I was a bit too fast with pushing this
update! I'm having a tough time with a lot of work. "So much to do, but
not much time for it..." ;-)
In in the meantime I ran a few tests, maybe this helps:
1. Installed on testmachine (an old(!) Core 92), no noticeable problems
during/after reboot:
Deleted old pam-libraries, restarted, no noticeable problems either:
***SNIP***
...
[root(a)ipfiretest ~]# ps ax|grep pam
1527 ? Ss 0:00 /usr/sbin/saslauthd -n 2 -a pam
1528 ? S 0:00 /usr/sbin/saslauthd -n 2 -a pam
2463 pts/0 R+ 0:00 grep pam
...
***SNAP***
Started / stopped / restarted various services without problems.
2. Clean install on testmachine: (Core 96, "Development Build:
pam/eeb83132-dirty", compiled 15.11.2015, with pam 1.2.1), no
eye-catching events.
What else could I test?
Best,
Matthias
next prev parent reply other threads:[~2015-11-15 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 16:50 Matthias Fischer
2015-11-09 18:37 ` Michael Tremer
2015-11-15 12:07 ` Matthias Fischer [this message]
2015-11-18 12:36 ` Michael Tremer
2015-11-19 17:33 ` Matthias Fischer
2015-12-01 23:10 ` Michael Tremer
2015-12-02 18:50 ` Matthias Fischer
2015-12-06 10:27 ` Matthias Fischer
2015-12-11 18:50 ` Michael Tremer
2015-12-11 21:46 ` Matthias Fischer
2016-03-13 10:29 [PATCH] pam: update " Marcel Lorenz
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=5648759D.50505@ipfire.org \
--to=matthias.fischer@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