I copied my entire filesystem of PUTER1 over to another hd, PUTER2
I had installed lsh-1.4.2 on the system before I copied it.
On PUTER2, I installed lsh-1.5.5 over it and:
$ rm ~/.lsh/yarrow-seed-file $ lsh-make-seed # rm /var/spool/lsh/yarrow-seed-file # lsh-make-seed --server # lsh-keygen --server | lsh-writekey --server # rm /etc/lsh_host_key # rm /etc/lsh_host_key.pub # lsh-keygen --server | lsh-writekey --server
Now, when I try to connect from PUTER1 to PUTER2, I get:
lsh: lshd: Could not bind any address. lsh: Connection reset by peer, (errno = 104)
Anyone got any idea?
Esben Stien executiv@online.no writes:
Now, when I try to connect from PUTER1 to PUTER2, I get:
lsh: lshd: Could not bind any address. lsh: Connection reset by peer, (errno = 104)
The "Could not bind any address." message is from lshd. A little odd that it shows up that way, though.
What command line do you use to start lshd?
One change between lsh-1.5.5 and the 1.4.x series is that the order of -p and --interface options is significant. (This change was introduced in 1.5.2, see the NEWS entry for that version).
Regards, /Niels
nisse@lysator.liu.se (Niels Möller) writes:
What command line do you use to start lshd?
I tried running lshd directly from the shell and it worked
I was trying running lshd from xinetd-2.3.10.
No need to cc me; I'm on the list
Esben Stien executiv@online.no writes:
nisse@lysator.liu.se (Niels Möller) writes:
What command line do you use to start lshd?
I tried running lshd directly from the shell and it worked
I was trying running lshd from xinetd-2.3.10.
Sorry, starting lshd from inetd is not currently supported. It's supposed to fail with a "lshd: spawning from inetd not yet supported." error message, but appearantly that didn't work for you.
See http://bugzilla.lysator.liu.se/show_bug.cgi?id=1145 for a little more information.
No need to cc me; I'm on the list
Since you seem to be using Gnus, I'd recommend that you set nnmail-treat-duplicates to a suitable value, and/or add a "Mail-copies-to: never" header when posting to mailinglists that you are subscribed to. I could try to remember who's on the list and who isn't, but that's not going to be very reliable.
Best regards, /Niels
-
Esben Stien -
nisse＠lysator.liu.se