From owner-freebsd-current Sun Apr 14 8:47:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CEC1B37B416 for ; Sun, 14 Apr 2002 08:47:12 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 94C705309; Sun, 14 Apr 2002 17:47:07 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "David W. Chapman Jr." Cc: current@freebsd.org Subject: Re: PAM error messages References: <20020414035312.GA31222@leviathan.inethouston.net> From: Dag-Erling Smorgrav Date: 14 Apr 2002 17:47:06 +0200 In-Reply-To: <20020414035312.GA31222@leviathan.inethouston.net> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "David W. Chapman Jr." writes: > I'm seeing this a lot on a recent 4.5-STABLE to -current upgrade, is > this a problem or something I did wrong? > > dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_close_session() > dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_open_session() Neither. The PAM policy for login(1) includes pam_unix in the session management chain, but pam_unix does not provide session management services, so you get a warning. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message