[Pkg-ltsp-devel] Bug#490897: tcsh logins

[Vagrant Cascadian]

found 490897 2:2.0.11-1
thanks

On Wed, Aug 13, 2008 at 09:34:03PM +0200, Daniel Nilsson wrote:
> On Fri, Aug 08, 2008 at 02:59:57PM -0700, Vagrant Cascadian wrote:
> --- ldm-2.0.9.orig/src/ldm.c
> +++ ldm-2.0.9/src/ldm.c
> @@ -268,7 +268,7 @@
>       * FIXME: ditch the kill -1 and use ssh -o exit on the control socket
>       */
>      command = g_strjoin(" ", "ssh", "-Y", "-t", "-S", ldm.control_socket,
> -            "-l", ldm.username, ldm.server, client_env,
> +            "-l", ldm.username, ldm.server, "env" ,client_env,
>              lang ? lang : "", display ? display : "", sound ? sound : "",
>              ldm.session, localdev ? localdev : "",
>              "; kill -1 $PPID", NULL);
> 
> But you are saying that you were able to login using ldm-2.0.9 without
> the above patch? 

i set a user's default shell to tcsh and was able to log in using ldm
2.0.9-1. today, i'm not able to do so using 2.0.11-1. *sigh* i don't
know what happened.

i'll test your patch and if it works well, will get it upstream and
hopefully into the version of ldm in lenny, as it seems simple.

> This issue seems clear to me (and can be seen in the
> ldm.log file as well), ldm issues a command of the form
> LTSP_CLIENT=192.168.1.1 DISPLAY=192.168.1.5 /etc/X11/Xsession to the
> LTSP server as the user who is trying to login in. This is fine for
> bash, but will fail on tcsh.

in previous ldm versions, the initial login was done with LANG=C so we
could scrape the login text. we stopped doing that in 2.0.9+, and i
thought the next call was actually done with "bash -c 'LTSP_CLIENT=
...'" explicitly, but that doesn't appear to be the case.

live well,
  vagrant