Re: [viewvc-users] 500 server error when accessing some areas of the repo
"C. Michael Pilato" <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.user |
|---|---|
| Organization | CollabNet, Inc. |
| Message-ID | <[email protected]> |
ViewVC (and Subversion itself, for that matter) heavily optimizes for the case when the user has global read access to the repository. The addition of even a single rule which denies read access to a part of the repository flips ViewVC into a mode where it now has to check every path it considers displaying for access rights, and sometimes the costs of those checks are great. Generally, I find that the bottleneck in these situations is not so much the sheer number of items in a directory, but whether those items were last modified in revisions in which a vast number of paths were changed. You can try increasing your server timeout (using the Timeout httpd.conf directive), but I'm not sure that that really improves anything. Who wants to sit for 10 minutes waiting for a directory listing to appear? You might also investigate the dir_pagesize and log_pagesize options, which cause ViewVC to split up long directory and log revision displays into multiple pages. On 09/28/2011 09:29 AM, Millsap, James wrote: > Similar in composition to the rest of the repo. More dirs, with > associated projects. If I give myself [/] read access, I can browse > through it. Even though I have rw access to many dirs. under /trunk/raw, > I cannot browse through it without global read access. > > -----Original Message----- From: C. Michael Pilato > [mailto:[email protected]] Sent: Wednesday, September 28, 2011 8:19 AM > To: Millsap, James Cc: [email protected] Subject: Re: > [viewvc-users] 500 server error when accessing some areas of the repo > > On 09/27/2011 12:25 PM, Millsap, James wrote: >> Hello, >> >> I guess first I should explain the implementation a bit. I have >> viewvc setup with an svn repository. Using a scriptalias in apache, >> and svnauthz. Authentication and permissions work fine, except the >> /trunk/raw dir. Unless I have read access for the entire repo that dir >> will timeout and give a 500 error. > > So ... what's in the /trunk/raw directory? ------------------------------------------------------ http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2848298 To unsubscribe from this discussion, e-mail: [[email protected]].
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk6F1rYACgkQokEGqRcG/W5crQCgsaKd7jB07YJsZfh9wzAdRpxK r80AnRawpseg9JfdvUwu8PXpyROxINn7 =Z4ZA -----END PGP SIGNATURE-----