This sounds like a bug either in libssh2 or in the pecl module, but 
with that sort of behavior, it's pretty much impossible for it to be 
caused by Horde. Sorry...

compiling libssh2 with --enable-debug-all yields in the attached log 
entries.  the last 3 lines with failure event -26 Remote end has 
closed this channel is repeating millions of times. Is this a 
configuraiton problem or is it a bug in libssh2 or is it a bug in the 
pecl module or in HORDE ?



[libssh2] Connection: Exit status 2 received for channel 3/3

[libssh2] Transport: Checking for packet: will not block

[libssh2] Transport: Blocking read: 15 bytes

[libssh2] Transport: Blocking read: 15 bytes actually read

[libssh2] Transport: Processing packet 12 bytes long (with 6 bytes padding)

[libssh2] Transport: Blocking read: 20 bytes

[libssh2] Transport: Blocking read: 20 bytes actually read

[libssh2] Transport: Packet type 96 received, length=5

[libssh2] Connection: EOF received for channel 3/3

[libssh2] Transport: Checking for packet: will not block

[libssh2] Transport: Blocking read: 15 bytes

[libssh2] Transport: Blocking read: 15 bytes actually read

[libssh2] Transport: Processing packet 12 bytes long (with 6 bytes padding)

[libssh2] Transport: Blocking read: 20 bytes

[libssh2] Transport: Blocking read: 20 bytes actually read

[libssh2] Transport: Packet type 97 received, length=5

[libssh2] Connection: Close received for channel 3/3

[libssh2] Transport: Checking for packet: will not block

[libssh2] Failure Event: -26 - Remote end has closed this channel

[libssh2] Connection: Setting blocking mode on channel 3/3 to 1

[libssh2] Connection: Attempting to read 8192 bytes from channel 3/3 stream #0

[libssh2] Transport: Checking for packet: will not block

[libssh2] Failure Event: -26 - Remote end has closed this channel

[libssh2] Connection: Setting blocking mode on channel 3/3 to 1

[libssh2] Connection: Attempting to read 8192 bytes from channel 3/3 stream #0

[libssh2] Transport: Checking for packet: will not block

[libssh2] Failure Event: -26 - Remote end has closed this channel

[libssh2] Connection: Setting blocking mode on channel 3/3 to 1

[libssh2] Connection: Attempting to read 8192 bytes from channel 3/3 stream #0

[libssh2] Transport: Checking for packet: will not block

[libssh2] Failure Event: -26 - Remote end has closed this channel

I spend some more time investigating and set the memory limit off. now 
system begins to swap. It might not be due to the spaces in the path 
but always happens while accessing an smb-Share thru  the ssh2 backend 
connection.

We operate an ssh2 server to provide access to various filesystems 
(nfs/smb) on our university. So i configured gollem to use the ssh2 
backend. It works till there is a space in the pathname.



RHEL 5 - libssh2-0.14 - see attached phpinfo





Possilbly this is a misconfigured gollem ssh2 backend.  Here is the 
gollem/backends.php :



$backends['ssh2'] = array(

     'name' => 'ssh',

     'driver' => 'ssh2',

     'preferred' => 'webmail',

     'hordeauth' => true,

     'params' => array(

         'hostspec' => 'ssh.',

         'port' => 22,

     ),

     'loginparams' => array(

     ),

     'createhome' => false,

      'filter' => '^\..*$',

     'quota' => false,

     'clipboard' => true,

     'attributes' => array('type', 'name', 'edit', 'download', 
'modified', 'size', 'permission', 'owner', 'gro

up')

);