Hi Niels,
I just had some time to investigate the problem a little bit further. It seems that lshd tries to open a pty, an strace contains this:
----------8<---------- [...] select(7, [5 6], [6], [], {5368, 119868}) = 2 (in [6], out [6], left {5368, 120000}) read(6, "S\225\360\t/V\v\0325\362hd\351\2\324\223\343\214p>\230"..., 16384) = 368 open("/dev/ptya0", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or directory) open("/dev/ptya1", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or directory) open("/dev/ptya2", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or directory) open("/dev/ptya3", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or directory) open("/dev/ptya4", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or directory) open("/dev/ptya5", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or directory) [...] ----------8<----------
The system is based on devfs which has the ptys in /dev/pty/; The device nodes itself are called m0..m99.
I also see this:
----------8<---------- fork() = 83 close(7lshd: unix_user: exec failed (errno = 2): No such file or directory ) = 0 --- SIGCHLD (Child exited) --- ----------8<----------
Which device nodes does lsh expect? Can I simply link the existing ones to the correct paths, and if yes, which ones are the equivalents to the /dev/ptyxx and /dev/ttyxx entries?
Robert