RE: Re: [viewvc-users] OSError: [Errno 13] Permission denied

Matt Schemmer <[email protected]> Tue, 30 Apr 2013 07:20:39 -0700 (PDT)
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Message-ID <2066022009.1777.1367331639121.JavaMail.httpd__37593.6742210344$1367331648$gmane$org@localhost>
> I couldn't find anything else on Google that was this specific, so I was looking to revive this. I'm having the exact same error when going to http://myserver/viewvc on a RANCID setup. I tried to follow the guide linked by Shrubbery for Redhat/Centos. I'm using Centos 6.3.
> 
> I'm far from a Linux admin, so it might be something simple. In the viewvc.conf, I get this error when trying to set root_parents to /home/rancid/var/CVS: cvs. If I comment out this line, and go to the ViewVC URL, it loads, but the repository list is of course blank. I'm not sure where the "default" repository directory is (if there is one.
> 
> I figured this was a directory permissions issue, so I even tried chmod 777 on this dir just to test, but no luck. I'm not sure what accounts are really being used, or why this directory would in anyway be inaccessible with rwx applied to anonymous users. Any help would be GREATLY appreciated, as I'm not sure what to troubleshoot at this point. Thanks!

Oh just to add to this as I worked on this a bit yesterday and tried to improve my understanding of viewvc. When commenting out root_parents, I put this line in the config for cvs roots:

cvs_roots = cvs: /home/rancid/var/CVS/networking

Which had the myserver/viewwc page load, but with no info. Also, despite naming it 'cvs,' the webpage just shows '/' in the top left, where from my understanding it should say 'cvs.' Additionally, even when changing that directory to one that doesn't exist, the page loads the exact same way. It seems like it's not even looking at it, despite having root_parents commented out. Thanks!

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=3054653

To unsubscribe from this discussion, e-mail: [[email protected]].