Once upon a time, Enrico Weigelt said: > ssh <hostname> mutt > > It always spits out: > > stdin: is not a tty > No recipients specified > > When I ssh to the destination host and enter "mutt\n" manually, > it works really good. > > What the hell happens here ?! When you run a command directly with ssh (ssh <hostname> mutt) it doesn't allocate a pseudo-tty whereas if you log in and then run mutt a pseudo-tty is allocated -- keeping mutt happy. Taken from the ssh manual: -t Force pseudo‐tty allocation. This can be used to execute arbi‐ trary screen‐based programs on a remote machine, which can be very useful, e.g., when implementing menu services. Multiple -t options force tty allocation, even if ssh has no local tty. So, try ssh -t <hostname> mutt. HTH Joe -- Procrastination means never having to say you're sorry.
Attachment:
signature.asc
Description: Digital signature