Re: svn 1.8.3 on windows often crashes
"Fully supported" does not mean that anyone gets to dictate when we make a release. It means that we will fix bugs, and this bug has been fixed and will be in the next release. If you can't wait, you can always build your own binaries, or ask (or pay) someone else to do it. The sources are free; and this project does not create binaries anyway. If you're expecting commercial support, you will not find it on this list; but there are many companies that do offer it. -- Brane Hello Brane, OK. So please tell me whether this fix (r152289) for issue #4425 is already merged to branch 1.8.x?!( Regards, KarolSzk
Re: svn 1.8.3 on windows often crashes
On 18.10.2013 11:33, Karol Szkudlarek wrote: > > "Fully supported" does not mean that anyone gets to dictate when we make > a release. It means that we will fix bugs, and this bug has been fixed > and will be in the next release. If you can't wait, you can always build > your own binaries, or ask (or pay) someone else to do it. The sources > are free; and this project does not create binaries anyway. > > If you're expecting commercial support, you will not find it on this > list; but there are many companies that do offer it. > > -- Brane > > > Hello Brane, > > OK. So please tell me whether this fix (r152289) for issue > #4425 is already merged to branch 1.8.x?!( Ivan answered that question in this thread two weeks ago. And it really is not polite to shout at people. Do go easy on the exclamation marks. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
Re: svn 1.8.3 on windows often crashes
Ivan answered that question in this thread two weeks ago.
And it really is not polite to shout at people. Do go easy on the
exclamation marks.
-- Brane
Hello Brane,
And If you don't know what I'm asking please don't write.
I'm asked about:
/"//OK. So please tell me whether this fix (r152289) for issue //
> #4425 is already merged to branch 1.8.x?!("
/Ivan's answer is not enough for me. Ivan wrote:
"Well, I checked logs more carefully and it seems like issue #4425 [1]
which is fixed in r1522892 and proposed for backport to Subversion
1.8.4. "
I don't know whether r1522892 is in trunk (I suppose this) or in
destination branch 1.8.x.
And Brane, please do not take this personally. I'm asking only for
Subversion program.
Regards,
KarolSzk
Re: svn 1.8.3 on windows often crashes
On 18 October 2013 18:06, Karol Szkudlarek wrote:
>
> I'm asked about:
>
> " OK. So please tell me whether this fix (r152289) for issue
>> #4425 is already merged to branch 1.8.x?!("
>
> Ivan's answer is not enough for me. Ivan wrote:
>
> "Well, I checked logs more carefully and it seems like issue #4425 [1]
> which is fixed in r1522892 and proposed for backport to Subversion
> 1.8.4. "
>
> I don't know whether r1522892 is in trunk (I suppose this) or in destination
> branch 1.8.x.
>
Yes, r1522892 was merged to 1.8.x branch and other user tested 1.8.x
command line binaries (from TortoiseSVN) and confirmed that issue
fixed:
http://svn.haxx.se/users/archive-2013-10/0110.shtml
--
Ivan Zhakov
CTO | VisualSVN | http://www.visualsvn.com
Re: svn 1.8.3 on windows often crashes
W dniu 2013-10-18 16:22, Ivan Zhakov pisze:
On 18 October 2013 18:06, Karol Szkudlarek wrote:
I'm asked about:
" OK. So please tell me whether this fix (r152289) for issue
#4425 is already merged to branch 1.8.x?!("
Ivan's answer is not enough for me. Ivan wrote:
"Well, I checked logs more carefully and it seems like issue #4425 [1]
which is fixed in r1522892 and proposed for backport to Subversion
1.8.4. "
I don't know whether r1522892 is in trunk (I suppose this) or in destination
branch 1.8.x.
Yes, r1522892 was merged to 1.8.x branch and other user tested 1.8.x
command line binaries (from TortoiseSVN) and confirmed that issue
fixed:
http://svn.haxx.se/users/archive-2013-10/0110.shtml
Thanks Ivan! :)
--
Karol Szkudlarek
Head Of Software Development
DCIO
Mikronika, HQ Poznan
Please consider your environmental responsibility.
Before printing this e-mail message, ask yourself
whether you really need a hard copy.
AuthType Basic (with ext LDAP)
Hi, There is a simple setup for svn users authentication on the server using LDAP. DAV svn SVNListParentPath on SVNParentPath /path_to_data SVNListParentPath on AuthzSVNAccessFile /path_to_accessfile/accfile AuthzLDAPAuthoritative off AuthType Basic AuthBasicProvider ldap AuthName "your login pls" AuthLDAPBindDN "blah-blah" AuthLDAPBindPassword "somepass" AuthLDAPURL "ldap://URL+DC?sub?(objectClass=*)" AuthzForceUsernameCase Lower Require valid-user CheckSpelling On What I noticed is that svn server making a request for each svn URI or operation, which neither LDAP server likes nor users that could be waiting for their turn to be authenticated and see delays in svn server response. Could somebody point me where the problem is? I'd expect only one authentication request from the server when user presents himself first time (or after cache expires). --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen.
Re: AuthType Basic (with ext LDAP)
On 10/18/13 10:01 AM, Naumenko, Roman wrote: > What I noticed is that svn server making a request for each svn URI or > operation, which neither LDAP server likes nor users that could be > waiting for their turn to be authenticated and see delays in svn server > response. > > Could somebody point me where the problem is? > I'd expect only one authentication request from the server when user > presents himself first time (or after cache expires). This is a feature. It allows you to use Apache authentication setups that are path based like mod_authz_svn is. In your case (and most users case) the only authentication handler that cares about the path is mod_authz_svn, in which case you can use the mod_dav_svn configuration directive "SVNPathAuthz short_circuit" which will prevent subrequests from being generated for additional paths that a request touches other than the path in the request URI and instead simply ask mod_authz_svn to process the path directly. This will speed up your server by quite a bit since subrequests are slow as well as resolving your problem with LDAP.
Re: AuthType Basic (with ext LDAP)
On 2013/10/18 1:51 PM, Ben Reser wrote: > On 10/18/13 10:01 AM, Naumenko, Roman wrote: >> What I noticed is that svn server making a request for each svn URI or >> operation, which neither LDAP server likes nor users that could be >> waiting for their turn to be authenticated and see delays in svn server >> response. >> >> Could somebody point me where the problem is? >> I'd expect only one authentication request from the server when user >> presents himself first time (or after cache expires). > This is a feature. It allows you to use Apache authentication setups that are > path based like mod_authz_svn is. In your case (and most users case) the only > authentication handler that cares about the path is mod_authz_svn, in which > case you can use the mod_dav_svn configuration directive "SVNPathAuthz > short_circuit" which will prevent subrequests from being generated for > additional paths that a request touches other than the path in the request URI > and instead simply ask mod_authz_svn to process the path directly. This will > speed up your server by quite a bit since subrequests are slow as well as > resolving your problem with LDAP. Ben, thank you. When short_circuit is enabled, then LDAP requests are not recorded any more in the debug log (except for initial request), so that what I was looking for. Great. But there are still checks (or maybe this is just info log) against access-file for each path in repository. Is it something expected or enabled somewhere by default? [Fri Oct 18 15:35:52 2013] [info] [client 10.11.11.18] Access granted: 'user1' REPORT /trunk/very_long_path/Data.manifest [Fri Oct 18 15:35:52 2013] [debug] subversion/mod_authz_svn/mod_authz_svn.c(195): [client 10.11.11.18] Path to authz file is /path_to_access_file/svn_acc I mean if a user has access to a repository, why checking all paths under? Or its just info log about mod_authz_svn processing path directly, as you said? --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen.
Re: AuthType Basic (with ext LDAP)
On 10/18/13 12:46 PM, Naumenko, Roman wrote: > But there are still checks (or maybe this is just info log) against > access-file for each path in repository. > Is it something expected or enabled somewhere by default? > > [Fri Oct 18 15:35:52 2013] [info] [client 10.11.11.18] Access granted: > 'user1' REPORT /trunk/very_long_path/Data.manifest > [Fri Oct 18 15:35:52 2013] [debug] > subversion/mod_authz_svn/mod_authz_svn.c(195): [client 10.11.11.18] Path > to authz file is /path_to_access_file/svn_acc > > I mean if a user has access to a repository, why checking all paths > under? Or its just info log about mod_authz_svn processing path > directly, as you said? The authz access file is only read once per connection. But the checks will be run for each path accessed by the request. Some of the requests over HTTP actually access multiple paths in the repository. For instance a REPORT request might be doing what's referred to as a bulk update, in which case it's asking for details on all the paths under a given path. The update REPORT in this case will include file content for paths under the path. Only the top level path will be in the URI. If you want to disallow access to some paths under that root path of the request it is necessary to check all the paths. Some other operations like COPY and MOVE also touch paths other than the one in the URI for the request since the action requires two paths. So what you're seeing is perfectly normal operation for the short_circuit configuration. You can entirely disable the additional checks mentioned above by setting "SVNPathAuthz off". However, I would not recommend that as it will make some authz rules ineffective. The whole created by this in the update report case can be closed by also setting "SVNAllowBulkUpdate off" but that doesn't help the COPY or MOVE cases. So in general, there's really not a great reason to use the off setting.
