From owner-freebsd-cvsweb@FreeBSD.ORG Tue May 20 16:18:41 2003 Return-Path: Delivered-To: freebsd-cvsweb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B88EB37B405; Tue, 20 May 2003 16:18:41 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com [66.187.233.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id D770743FCB; Tue, 20 May 2003 16:18:40 -0700 (PDT) (envelope-from bgroh@redhat.com) Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h4KNIeH14342; Tue, 20 May 2003 19:18:40 -0400 Received: from hypatia.brisbane.redhat.com (IDENT:root@hypatia.brisbane.redhat.com [172.16.5.3])h4KNIcI00945; Tue, 20 May 2003 19:18:38 -0400 Received: from redhat.com (bernd.brisbane.redhat.com [172.16.5.91]) h4KNIZj02275; Wed, 21 May 2003 09:18:36 +1000 Message-ID: <3ECAB9B5.6060005@redhat.com> Date: Wed, 21 May 2003 09:26:45 +1000 From: Bernd Groh User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2.1) Gecko/20030225 X-Accept-Language: de-at, de, en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ville_Skytt=E4?= References: <3ECAA87C.7090406@softtek.com> <1053469908.22989.53.camel@bobcat.ods.org> In-Reply-To: <1053469908.22989.53.camel@bobcat.ods.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-cvsweb@freebsd.org Subject: Re: Error: Failed to spawn GNU rlog X-BeenThere: freebsd-cvsweb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS Web maintenance mailing list [restricted posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2003 23:18:42 -0000 Ville, >To get the real errors, you can comment out the line(s) like: > > open(STDERR, '>/dev/null'); # rlog may complain ... > >...around line 2130 (assuming you're using FreeBSD-CVSweb 2.0.6) in >cvsweb.cgi and watch your web server error log while clicking the >problematic dir link. > I actually ran into the same problem last week, made a fix to the script and submitted it to the list. But, I did this BEFORE I was a member of this list, as such, I only got the response that it awaits confirmation of the list-owner, and I had no response yet. Shall I re-submit the fix? It's very simple, it only checks whether you've got write-permissions to all the files you want to spawn rlog on, and if you don't, then it doesn't spawn rlog on that particular file (as a result, rlog seems to not complain anymore either). You can actually, given you can see the files, check for read-permissions and output an according error-message, this wouldn't require manual fixes in the script later on in order to determine whether you've got the right permissions. Cheers, Bernd -- Disclaimer: http://apac.redhat.com/disclaimer