Jeff Bailey <[EMAIL PROTECTED]> writes:
> It looks good for me - One thing:
Good to hear.
> [jbailey@cr499794-a .lsh]$ lsh_keygen -l 8 |lsh_writekey
>
> lsh_writekey doesn't overwrite existing key files.
> If you *really* want to do that, you should delete
> the existing files "FOO" and "FOO.pub" first
> (where "FOO" usually is "~/.lsh/identity").
> Broken pipe
> [jbailey@cr499794-a .lsh]$
>
> There is a long pause then the broken pipe. It might be nice if instead
> of breaking the pipe it send a control character through to cancel or
> something.
I'm afraid it's difficult to do anything about that. THe shell starts
two processes:
1. lsh_writekey, which writes the error messages and then dies.
2. lsh_keygen, which thinks silently for quite a while, then tries to
write the answer (a new private key), and only then it dies of
EPIPE.
Most likely, the pause is the shell waiting for process 2 to die.
/Niels
