Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Yes=the system is on the domain and authenticates users against the domain for logins and SMB.
httpd version= 2.0.52
subversion = 1.1-4.2
(I neglected to provide the versions)
I'm configuring this on a RHEL4 system and the subversion configuration is being configured in /etc/httpd/conf.d/subversion.conf.
I reviewed your svn config and noted that there were a few items that I did not have in the configuration file. The URL and a few and the following lines:
Options Indexes FollowSymLinks
allow from all
I'll add those suggestions and try again. As a side note we have another system using the same setup and it works without any problems. (The httpd version is the same, but the Subversion is 1.1-2.1.
# Example configuration to enable HTTP access for a directory
# containing Subversion repositories, "/var/www/svn". Each repository
# must be readable and writable by the 'apache' user. Note that if
# SELinux is enabled, the repositories must be labelled with a context
# which httpd can write to; this will happen by default for
# directories created in /var/www. Use "restorecon -R /var/www/svn"
# to label the repositories if upgrading from a previous release.
# To create a new repository "http://localhost/repos/stuff" using
# this configuration, run as root:
# # cd /var/www/svn
# # svnadmin create stuff
# # chown -R apache.apache stuff
allow from all
# Limit write permission to list of valid users.
<LimitExcept GET PROPFIND OPTIONS REPORT>
1. confirm that apache is the owner/user recursively throughout the repo:
in your case: chown -R apache:apache /work10/svn/
2. Try and commit
3. If you are still getting that error let's try this:
A. Add this line of code to config file
B. mkdir /var/svn/conf (if you don't have one already)
c. vim or nano /var/svn/conf/svnpolicy
d. Example File: