Configure user name?
Does subversion provide a way for the user to configure his username, thus avoiding having to pass the --username flag everytime he has to commit something? Thanks Zé
Re: Access SVN slowly at first time login
On Thu, Apr 17, 2014 at 11:41 AM, 蛋蛋/nv 419965...@qq.com wrote: Dear: I have a question when using SVN. Could you please help me on this? We run two SVN virtual machines(with Windows Server 2003 system installed Subversion Edge ) on the same physical machine.We set LDAP authentication both on the two virtual machines.When we log in SVN at the first time, it behaves slowly, and after I closed SVN log-in widows mandatory, and log in SVN again, it behaves normally. Looking forward to your reply! The problem might be related to the LDAP module performing the authentication. I'm not an expert in the LDAP-related httpd directives, but that's the direction I'd look first. Maybe as a first test you can try taking LDAP completely out of the picture, by using some other authentication module (plain user/pwd database) or even anonymous? Just as an experiment to rule out various possibilities. Another thing to try is: are you using the latest version of Edge -- if not maybe first try the latest? -- Johan
Re: Access SVN slowly at first time login
On Thu, Apr 17, 2014 at 5:41 AM, 蛋蛋/nv 419965...@qq.com wrote: Dear: I have a question when using SVN. Could you please help me on this? We run two SVN virtual machines(with Windows Server 2003 system installed Subversion Edge ) on the same physical machine.We set LDAP authentication both on the two virtual machines.When we log in SVN at the first time, it behaves slowly, and after I closed SVN log-in widows mandatory, and log in SVN again, it behaves normally. Looking forward to your reply! Keep in mind, LDAP *is not usually doing authentication*. It's normally doing account management. With Active Directory and most setups, *Kerberos* is doing authentication. So, for example, the first connection to a Kerberos service is sensitive to slow reverse DNS lookups and time skew between your client machine and the LDAP server. Also, for both LDAP and Kerberos, there are often multiple servers configured to run the service, and one of them may be having problems. I'd reach out to your LDAP manager and ask if they've noticed erratic behavior. Also, see if you can repeat the problem. If the SVN server itself was very busy with some bulky svnsync operation, or just system backups, you might have seen a temporarily slow load.
RE: 10 seconds timeout before each operation involving network connection
I posted this already on the TortoiseSVN mailing list and it was suggested to report it to the Subversion Users mailing list: We are using TortoiseSVN (1.8.x) and the subversion command-line client (1.8.8) on Windows7 clients together with a VisualSVN (2.5.x) Server inside our company network. On some clients, there was a timeout of about ten seconds before each operation which involved contacting the server, e.g. commiting, updating, repo-browsing, etc. We analyzed this behavior using WireShark and SysInternals procmon. In the end, we found out that the problem exists only on clients with network adapters showing Unidentified Network such as virtual machine host adapters when no VM is running or network adapters with wrong IP settings. When all these adapters are set to disabled, the problem doesn't exist anymore and the transaction begins within a second. Adapters, either physical or virtual, with unplugged cables are no issue. As a workaround, we tried to set the priority of the network adapter connected to the company LAN to the highest value, but without any success. The problem also exists with the command-line client delivered with TortoiseSVN. Can someone reproduce this behavior? Interesting. We are seeing an initial delay when doing commits recently also using Tortoise. However, I'm 99% sure it started when I upgraded the server from 1.7.x to 1.8.x. So, I can't see this being a client side issue. However, I'd like to check. Where do you see Unidentified Network I did an ipconfig /all and don't see that term at all even on the VMWare adapters.
RE: Configure user name?
Does subversion provide a way for the user to configure his username, thus avoiding having to pass the --username flag everytime he has to commit something? Thanks Zé The credentials should be cached. If they are not being cached check in ~/.subversion/config, you probably have store-passwords = no. Change it to yes (or just comment it out because it defaults to yes), and the next time you give subversion your password it should save it.
Default user on commit
I have two local working copies, both on my local user account. I am managing commits for another user, so he sends me files and I check them in. It’s weird but we have our reasons for this. So I go into his working copy, replace the file in question with his copy, then do `svn ci --username other` and it works fine. But next time I go into my working copy, if I commit using `svn ci` without specifying username, it “remembers” the alternate username. Is there a way to keep these from “sticking? Or a way to specify a default username? Otherwise I’ll probably just specify each time, but it’s not ideal as it’s too easy to forget to specify it. I had hoped that omitting the --username argument would always default to the user’s local user account name, but that’s not the case. And yes, I know I could create a second local user account to make sure they stay separate. I’d rather not, though, if there’s another way to do it.
Re: Default user on commit
On 18.04.2014 18:15, Justin Mrkva wrote: I have two local working copies, both on my local user account. I am managing commits for another user, so he sends me files and I check them in. It’s weird but we have our reasons for this. So I go into his working copy, replace the file in question with his copy, then do `svn ci --username other` and it works fine. But next time I go into my working copy, if I commit using `svn ci` without specifying username, it “remembers” the alternate username. Is there a way to keep these from “sticking? Username settings (and credentials storage in general) are not specific to the working copy; they're global settings and only depend on the repository. So, no, there's no way to do this with Subversion. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
RE: Default user on commit
-Original Message- From: Justin Mrkva [mailto:m...@justinmrkva.com] Sent: vrijdag 18 april 2014 18:16 To: Subversion Users Subject: Default user on commit I have two local working copies, both on my local user account. I am managing commits for another user, so he sends me files and I check them in. It's weird but we have our reasons for this. So I go into his working copy, replace the file in question with his copy, then do `svn ci --username other` and it works fine. But next time I go into my working copy, if I commit using `svn ci` without specifying username, it remembers the alternate username. Is there a way to keep these from sticking? Or a way to specify a default username? Otherwise I'll probably just specify each time, but it's not ideal as it's too easy to forget to specify it. I had hoped that omitting the --username argument would always default to the user's local user account name, but that's not the case. You can pass --no-auth-cache with --username to avoid storing the new credentials. Bert And yes, I know I could create a second local user account to make sure they stay separate. I'd rather not, though, if there's another way to do it.
Re: Default user on commit
On Fri, Apr 18, 2014 at 1:53 PM, Branko Čibej br...@wandisco.com wrote: On 18.04.2014 18:15, Justin Mrkva wrote: I have two local working copies, both on my local user account. I am managing commits for another user, so he sends me files and I check them in. It’s weird but we have our reasons for this. So I go into his working copy, replace the file in question with his copy, then do `svn ci --username other` and it works fine. But next time I go into my working copy, if I commit using `svn ci` without specifying username, it “remembers” the alternate username. Is there a way to keep these from “sticking? sudo to another username when working with the other repository?
