NetBSD Problem Report #50622

From  Tue Jan  5 00:58:27 2016
Return-Path: <>
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "", Issuer "Postmaster" (verified OK))
	by (Postfix) with ESMTPS id B4AC67ABF3
	for <>; Tue,  5 Jan 2016 00:58:27 +0000 (UTC)
Message-Id: <>
Date: Tue,  5 Jan 2016 00:58:26 +0000 (UTC)
Subject: x11/xscreensaver's MESSAGE file potentially misleading
X-Send-Pr-Version: www-1.0

>Number:         50622
>Category:       pkg
>Synopsis:       x11/xscreensaver's MESSAGE file potentially misleading
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 05 01:00:00 +0000 2016
>Originator:     David H. Gutteridge
>Release:        current
The MESSAGE file provided by x11/xscreensaver can be a bit misleading.
It makes reference to a sample file meant for pam(8) at the location
"${EGDIR}/pam.d/xscreensaver-NetBSD". But in fact, dictates
that on NetBSD security/pam-pwauth_suid must be used, which installs
its own sample file at a different location,
${PREFIX}/share/examples/pam-pwauth_suid/xscreensaver. It would be
helpful to clarify there are different configurations that must be used
depending upon the OS when pam(8) is enabled.

I realize that security/pam-pwauth_suid has its own MESSAGE file that
references the location of its sample file, but the two messages
contradict each other, and the user is left with the x11/xscreensaver
version as the last thing they see, which might lead them to follow its
advice and then wonder why they can't unlock their screen.



NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.