Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I have SVN clients that use multiple username/password combinations for different tasks against the same repo.
I'd like to have the client cache one username/password pair (a shared read-only account) and not cache other username/password pairs (individual accounts with write access).
I know how to turn it on and off globally. That's not what we want.
Authentication is LDAP (Active Directory) + APACHE + WebDAV SVN
ADDITION AS AT 13:21
After doing a bit of research and implementing your case in my lab, I came to the following conclusion.
The first time the svn command-line client is executed, it creates a per-user configuration area. On Linux systems, this area appears as a directory named '.subversion' in the user's home directory.
In your case all users who have logged in till now have their passwords cached here. So now to have those "SPECIFIC USERS CREDENTIALS" still cahced in this file - edit the file and remove unwanted user credentials from it.
Now you will want to remove specific credentials from the disk cache.
To do this, you need to navigate to svn.simple directory and manually delete the appropriate cache file.
Credentials are cached in individual files; if you look inside each file, you will see keys and values.
The svn:realmstring key describes the particular server realm that the file is associated with:
***sample svn.simple file output***
$ ls ~/.subversion/auth/svn.simple/