Custom Query (230 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (7 - 9 of 230)

1 2 3 4 5 6 7 8 9 10 11 12 13
Ticket Resolution Summary Owner Reporter
#6 fixed avoid network sound on slow links Antoine Martin Antoine Martin
Description

When connecting to distant servers over a slow connection, just don't bother trying to tunnel the sound with PA, it will not work.

#7 fixed SMB support: must tell client or server what/how to mount stuff Antoine Martin Antoine Martin
Description

Windows clients can't mount a remote tunneled server since we can't tell them what port to use (sigh). So maybe we should always do a reverse mount? (server mounts shares from the client)
We need to find out the list of shares (pysamba?) and allow the user to configure what is mounted (read-only, password,...)

The actual mounting is the easy part:

mount.cifs //127.0.0.1/public ./guest -o port=21062 -o guest


But we have to make sure we always unmount stuff when the server goes down... Problem is that some files might still be open!

We should also deal with non-tunneled setups nicely: simply connect to SMB on client or server directly. This weighs in favour of supporting client-mounts-server option.


We can figure out what shares are available with (needs a bit of magic parsing... sigh):

smbclient -U guest -N -L localhost

or

smbclient -A /path/to/auth-file -L localhost

pysamba does not seem to help here, unless I am missing something.

See bug #91 for the next step.

#9 fixed Putty does not exit when remote command terminates Antoine Martin Antoine Martin
Description

In ssh-mode, we launch a remote X command and putty is still running when the command terminates.
This causes the session to remain "active" on the client despite the fact that it is really finished...

This happens with all the clients we can use: TortoisePlink.exe, Plink.exe as well as openssh (via cygwin). Looks like the clients refuse to shutdown whilst there is still a tunnel (the X display connection) so we may have to use a trick on the server and run the command via a wrapper which will take care of killing the ssh process when the command terminates.

1 2 3 4 5 6 7 8 9 10 11 12 13
Note: See TracQuery for help on using queries.