From owner-freebsd-isp Mon Nov 16 06:10:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13755 for freebsd-isp-outgoing; Mon, 16 Nov 1998 06:10:39 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from user1.channel1.com (user1.channel1.com [199.1.13.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13746 for ; Mon, 16 Nov 1998 06:10:36 -0800 (PST) (envelope-from admin@channel1.com) Received: from ntadmin (ntadmin.channel1.com [204.96.33.24]) by user1.channel1.com (8.9.1/8.9.1) with SMTP id JAA03219 for ; Mon, 16 Nov 1998 09:10:02 -0500 (EST) Message-Id: <3.0.5.32.19981116090958.00f70a80@pop.channel1.com> X-Sender: deepblue@pop.channel1.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 16 Nov 1998 09:09:58 -0500 To: freebsd-isp@FreeBSD.ORG From: Mail Handler Subject: APOP with qpopper.2.53 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All -- I've been trying to add APOP support to a qpopper 2.53 installation. I've followed the instrucions in INSTALL as to ownership, permissions and suid. With both GDBM and NDBM I get error setting ownership of POP authorization or unable to lock POP authorization DB I searched DejaNews and found two references to these error messages: one recommended hacking #define HAVE_FLOCK out of config.h and another patching popauth.c: "Popauth explicitly locks the database with open/flock before doing a write. This works with dbm. But the linux gdbm does it's own locking, and when gdbm tries to open the file for writing, it sees that the file is already locked, and refuses to open it. The fix is simple, don't do the explicit locking if using gdbm." Neither of these solutions seem to work for me. Has anyone been down this road before? Thanks, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message