Date: Wed, 21 May 2003 09:26:45 +1000 From: Bernd Groh <bgroh@redhat.com> To: =?ISO-8859-1?Q?Ville_Skytt=E4?= <scop@freebsd.org> Cc: freebsd-cvsweb@freebsd.org Subject: Re: Error: Failed to spawn GNU rlog Message-ID: <3ECAB9B5.6060005@redhat.com> In-Reply-To: <1053469908.22989.53.camel@bobcat.ods.org> References: <3ECAA87C.7090406@softtek.com> <1053469908.22989.53.camel@bobcat.ods.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ECAB9B5.6060005>