On 11.04.2019 10:17, Vincent Lefevre wrote:
> On 2019-04-11 04:22:29 +0200, Branko Čibej wrote:
>> I think that svnserve would only use that function to find the current
>> user's home directory, to locate the config files. And that seems wrong
>> because svnserve has no business looking at the cli
On 2019-04-11 04:22:29 +0200, Branko Čibej wrote:
> I think that svnserve would only use that function to find the current
> user's home directory, to locate the config files. And that seems wrong
> because svnserve has no business looking at the client's config area ...
I think that it would be b
On 10.04.2019 11:21, Vincent Lefevre wrote:
> On 2019-04-10 04:06:08 +0200, Branko Čibej wrote:
>> On 10.04.2019 03:29, Vincent Lefevre wrote:
>>> On 2019-04-09 20:09:26 +0200, Branko Čibej wrote:
The only problem with that idea is that svnseve doesn't use unscd at
all, or any kind of LDA
On 2019-04-10 04:06:08 +0200, Branko Čibej wrote:
> On 10.04.2019 03:29, Vincent Lefevre wrote:
> > On 2019-04-09 20:09:26 +0200, Branko Čibej wrote:
> >> The only problem with that idea is that svnseve doesn't use unscd at
> >> all, or any kind of LDAP access.
> > Are you so sure about that? A "st
On 10.04.2019 03:29, Vincent Lefevre wrote:
> On 2019-04-09 20:09:26 +0200, Branko Čibej wrote:
>> The only problem with that idea is that svnseve doesn't use unscd at
>> all, or any kind of LDAP access.
> Are you so sure about that? A "strace svnserve -t"[*] shows it
> reads the /etc/nsswitch.conf
On 2019-04-09 20:09:26 +0200, Branko Čibej wrote:
> The only problem with that idea is that svnseve doesn't use unscd at
> all, or any kind of LDAP access.
Are you so sure about that? A "strace svnserve -t"[*] shows it
reads the /etc/nsswitch.conf file. With "ltrace", I can see that
svn_user_get_n
On 09.04.2019 17:22, Vincent Lefevre wrote:
> I got interesting information from the sysadmin of the server:
> what the logs show is that a cron job reloads the unscd daemon
> every 10 minutes, a multiple of 10.
>
> So, the hanging svnserve was started at about the same time as the
> reload of the
I got interesting information from the sysadmin of the server:
what the logs show is that a cron job reloads the unscd daemon
every 10 minutes, a multiple of 10.
So, the hanging svnserve was started at about the same time as the
reload of the unscd daemon. This was also the case when I had the
pro
On 08.04.2019 18:38, Stefan Sperling wrote:
>> Well, I forgot, there's at least an issue with svnserve. I got that
>> in the past, and could reproduce it: once I kill the svn client
>> with Ctrl-C and kill the SSH master too, the sshd terminates, but
>> svnserve is still running, and now has 1 as i
On 2019-04-08 18:38:46 +0200, Stefan Sperling wrote:
> On Mon, Apr 08, 2019 at 05:05:47PM +0200, Vincent Lefevre wrote:
> > Well, I forgot, there's at least an issue with svnserve. I got that
> > in the past, and could reproduce it: once I kill the svn client
> > with Ctrl-C and kill the SSH master
On Mon, Apr 08, 2019 at 05:05:47PM +0200, Vincent Lefevre wrote:
> On 2019-04-08 16:38:37 +0200, Stefan Sperling wrote:
> > Since you have a way to reproduce the problem, even if unreliably,
> > you're in a position to help.
>
> But it could take weeks...
Perhaps you can find a way to trigger it
On 2019-04-08 16:38:37 +0200, Stefan Sperling wrote:
> Since you have a way to reproduce the problem, even if unreliably,
> you're in a position to help.
But it could take weeks...
> If you don't try, we'll have to wait until someone else figures out where
> the hang occurs or provides a clear an
On Mon, Apr 08, 2019 at 04:21:37PM +0200, Vincent Lefevre wrote:
> On 2019-04-08 15:26:15 +0200, Stefan Sperling wrote:
> > On Mon, Apr 08, 2019 at 02:38:15PM +0200, Vincent Lefevre wrote:
> > > On 2019-04-08 13:57:32 +0200, Stefan Sperling wrote:
> > > > There is insufficient information in your r
On 2019-04-08 15:26:15 +0200, Stefan Sperling wrote:
> On Mon, Apr 08, 2019 at 02:38:15PM +0200, Vincent Lefevre wrote:
> > On 2019-04-08 13:57:32 +0200, Stefan Sperling wrote:
> > > There is insufficient information in your report for anyone to act upon.
> > > Most importantly, it is unclear which
On Mon, Apr 08, 2019 at 02:38:15PM +0200, Vincent Lefevre wrote:
> On 2019-04-08 13:57:32 +0200, Stefan Sperling wrote:
> > There is insufficient information in your report for anyone to act upon.
> > Most importantly, it is unclear which component in the chain is causing
> > the problem. Is it SVN
On 2019-04-08 13:57:32 +0200, Stefan Sperling wrote:
> There is insufficient information in your report for anyone to act upon.
> Most importantly, it is unclear which component in the chain is causing
> the problem. Is it SVN? Is it SSH? Is it TCP?
> Please try to find answers to these questions.
On Mon, Apr 08, 2019 at 01:44:37PM +0200, Vincent Lefevre wrote:
> I've run a "svn diff" with the -c option, and it is hanging.
> The corresponding "svnserve -t" on the server is hanging too.
>
> After one hour, on the client side, the svn command is still running,
> together with
>
> vinc17 19
I've run a "svn diff" with the -c option, and it is hanging.
The corresponding "svnserve -t" on the server is hanging too.
After one hour, on the client side, the svn command is still running,
together with
vinc17 19550 19549 0 12:40 pts/11 00:00:00 zsh /home/vinc17/scripts/ssh
gforge svnse
18 matches
Mail list logo
