NetBSD Problem Report #52279

From  Wed Jun  7 00:20:48 2017
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 F11CF7A1FE
	for <>; Wed,  7 Jun 2017 00:20:47 +0000 (UTC)
Message-Id: <>
Date: Tue, 6 Jun 2017 23:06:53 GMT
Subject: Boot hangs with recent -current and security/cyrus-saslauthd
X-Send-Pr-Version: 3.95

>Number:         52279
>Category:       pkg
>Synopsis:       NetBSD cannot go multiuser with saslauthd launched from rc.conf
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 07 00:25:00 +0000 2017
>Release:        NetBSD 7.99.75


System: NetBSD 7.99.75 NetBSD 7.99.75 (GENERIC) #0: Wed May 31 05:05:38 UTC 2017 amd64
Architecture: x86_64
Machine: amd64

I've noticed now on a few machines, both amd64 and evbarm, that updating
to -current within the last week or so has resulted in a system which
boots but which hangs before getty launches, meaning no console login and
no ssh login even though sshd is already running.

I didn't have time to really diagnose the issue, but I did narrow it down
to saslauthd. It was getting launched from /etc/rc.conf with:

saslauthd_flags="-a getpwent"

Setting it to NO lets the system get all the way to multiuser.

I don't know if this is related to -current or to the update to
cyrus-saslauthd at the end of April, 2017.


Install pkgsrc/security/cyrus-saslauthd with PKG_RCD_SCRIPTS=YES
echo 'saslauthd=YES' >> /etc/rc.conf
echo 'saslauthd_flags="-a getpwent"' >> /etc/rc.conf

None known besides not starting saslauthd via rc.conf.


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.