svn status gets 'killed'

Hi all,

I recently set up an svn server, and to experiment, I imported a copy
of the Linux 2.4.19 kernel source. On my 'client' system, I run:

        svn co http://server/svn/linux-2.4.19 linux-2.4.19

and everything goes quite well. However, if I try to do an
'svn status', it just sits there for quite a while, and eventually
just dies with a message 'Killed':

        ll@tater:/usr/local/src/linux-2.4.19$ svn status -u -v .
        Killed
        pll@tater:/usr/local/src/linux-2.4.19$

An 'strace svn status -u -v' results in:

        pll@tater:~$ strace -p 17537
        .
        .
        .
        +++ killed by SIGKILL +++
        pll@tater:~$

Is something broken, or am I doing something wrong?

(Oh, an an 'svn status -n' results in:

        svn: invalid option character: n
        Type `svn help' for help on Subversion usage.

but 'svn status --nonrecursive' works fine).

I'm using: Subversion Client, version 0.14.1 (r2927)
                   compiled Aug 24 2002, 11:36:34

from the Debian packages 0.14.1-2.

Oh, FWIW, 'svn help' seems to be broken in the newer 0.14.3-2
packages under Debian:

        pll@tater:/usr/local/src/linux-2.4.19$ svn status -u -v --nonrecursive
        Type `svn help' for help on Subversion usage.

        pll@tater:/usr/local/src/linux-2.4.19$ svn help status
        Type `svn help' for help on Subversion usage.

        pll@tater:/usr/local/src/linux-2.4.19$ svn help
        Type `svn help' for help on Subversion usage.
        (err, that's what I did :)

-- 
Seeya,
Paul
--
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.
	 If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org