[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new window
Re: new window
Thu, 2 Dec 2004 10:38:49 -0800 (PST)
As someone else mentioned, expect(1) is probably the
right answer for you. It comes as part of Tcl/Tk, IIRC.
Here's a snippet of manpage for you:
expect - programmed dialogue with interactive programs
expect [ -dDinN ] [ -c cmds ] [ -[f|b] ] cmdfile ] [
Expect is a program that "talks" to other interactive
programs according to a script. Following the script,
Expect knows what can be expected from a program and
what the correct response should be. An interpreted
language provides branching and high-level control
structures to direct the dialogue. In addition, the
user can take control and interact directly when
desired, afterward returning control to the script.
Thus, it can even be used to "script" otherwise
"unscriptable" programs. A real basic use would be
autologin. I'll leave more advanced uses to your
imagination. It's outside the scope of 'screen' though.
--- Buddy Burden <address@hidden> wrote:
> > You could use ssh key pairs and keychain
> > http://www-106.ibm.com/developerworks/library/l-keyc2/
> for no-password
> > logins. And with something like
> > you could let pam spawn the ssh-agent.
> I'll definitely take a look at that--it may solve some of
> my more stubborn
> inter-machine ssh issues--but, as I said, ssh is only one
> example of the
> problem. Other programs that demand passwords (e.g.,
> mysql) have the same
> -- Buddy
> screen-users mailing list
We sell Spatulas, and that's all!
- Re: new window, Buddy Burden, 2004/12/02
- Re: new window,
Joe Zbiciak <=