how to use --disable-openpty to fix no shell after login

[Iztok Marjanovic]

Hello,

I have the same problem as described by a previous post by Stefan (see
below).  Stefan fixed his problem by using a --disable-openpty configuration
parameter.  I do not know where to specify the --disable-openpty.   Is this
specified in a dropbear config file somwhere?

I'm using Dropbear sshd v0.50.

Thanks,
Iztok

Hi,

d'uh. couldn't find any errors in the logs, but running it with error
reporting to stderr unveiled the problem:

[26079] Mar 27 23:32:05 pty_allocate: openpty: No such file or directory
[26079] Mar 27 23:32:05 no pty was allocated, couldn't execute

so.. configure with --disable-openpty helped and it works perfectly now.
Just in case someone else runs into this again.

  Best regards,
     Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20080331/155d1a5e/attachment.htm