From owner-freebsd-questions@freebsd.org Wed Nov 15 09:03:10 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C72DDD5FD0 for ; Wed, 15 Nov 2017 09:03:10 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 234213DB9 for ; Wed, 15 Nov 2017 09:03:09 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [192.168.1.183] (host81-134-87-65.range81-130.btcentralplus.com [81.134.87.65]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id vAF934B3084243 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Nov 2017 09:03:05 GMT (envelope-from frank2@fjl.co.uk) User-Agent: K-9 Mail for Android In-Reply-To: References: <6D5CB8A0-F31D-4899-BBF0-4208CDC34624@fjl.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: portsnap fails if not root From: "Frank Leonhardt (m)" Date: Wed, 15 Nov 2017 09:02:57 +0000 To: "freebsd-questions@freebsd.org" Message-ID: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 09:03:10 -0000 On 14 November 2017 15:49:52 GMT+00:00, "Frank Leonhardt (m)" wrote: > > >On 14 November 2017 15:24:32 GMT+00:00, Frank Leonhardt > wrote: >>Is there any reason why portsnap has to run as root? If you specify >>alternative ports dir and db dir using -p and - d, it should download >>and unpack stuff in home directory. >> >>Trouble us that it gets the tag, and starts fetching Metadata, but >>terminates with no message before it prints ..done. Not even a /n. >> >>Anyone know why before I start digging? For the sake of anyone with the same problem searching the archive... portsnap is very hit-and-miss at checking diagnostic returns when it runs something. In the case of the tag/metadata it can fails but still say it has completed as return is not checked. On the second one that fails there is a lazy bailout which drops you back to the prompt mid-line. In order to preserve the mystery as long as possible, it directs stderr to the bit bucket. In my case, the user account had insufficient file access to do the fetch. If you edit the macro to make stderr redirect to, er, stderr you will see a lot more of what is going on. I may do an error checking version one day if no one else does first... Regards, Frank. -- Sent from my Cray X/MP with small fiddling keyboard.