expert
- Giza baliabideak eta segurtasuna
- es perito
- eu peritu
- fr expert
expert
Ez dago emaitzarik
Bilatutako terminoa ez dago hiztegian.
- ^ "Expect FAQ: Our company policy requires a license to use Expect. Where can we get a license?". 2006-10-11.
- ^ Nemeth, Evi; Snyder, Garth; Seebass, Scott; Hein, Trent (2000-08-29). UNIX System Administration Handbook. Pearson Education. ISBN 978-0-13-700291-7.
- ^ Mckay, David (May 24, 2021) [May 24, 2021]. "Automate Inputs to Linux Scripts With the expect Command". category/Linux. Retrieved Nov 28, 2023.
{{cite web}}
: CS1 maint: date and year (link)
- ^ Carling, M.; Degler, Stephen; Dennis, James (2000). Linux System Administration. Sams Publishing. ISBN 978-1-56205-934-7.
- ^ "Tcl/Tk in the Development of User-Extensible Graphical User Interfaces". www.usenix.org. Retrieved 2022-08-11.
Wikipediako bilaketara joan
SARRERA DESBERDINA:
Expect
Expect is an extension to the Tcl scripting language written by Don Libes.[2] The program automates interactions with programs that expose a text terminal interface. Expect, originally written in 1990 for the Unix platform, has since become available for Microsoft Windows and other systems.
Expect is used to automate control of interactive applications such as Telnet, FTP, passwd, fsck, rlogin, tip, SSH, and others.[3] Expect uses pseudo terminals (Unix) or emulates a console (Windows), starts the target program, and then communicates with it, just as a human would, via the terminal or console interface.[4] Tk, another Tcl extension, can be used to provide a GUI.[5]
Expect serves as a "glue" to link existing utilities together. The general idea is to figure out how to make Expect use the system's existing tools rather than figure out how to solve a problem inside of Expect.
A key usage of Expect involves commercial software products. Many of these products provide some type of command-line interface, but these usually lack the power needed to write scripts. They were built to service the users administering the product, but the company often does not spend the resources to fully implement a robust scripting language. An Expect script can spawn a shell, look up environmental variables, perform some Unix commands to retrieve more information, and then enter into the product's command-line interface armed with the necessary information to achieve the user's goal. After retrieving information by interacting with the product via its command-line interface, the script can make intelligent decisions about what action to take, if any.
Every time an Expect operation is completed, the results are stored in a local variable called $expect_out. This allows the script to harvest information to feedback to the user, and it also allows conditional behavior of what to send next based on the circumstances.
A common use of Expect is to set up a testing suite for programs, utilities or embedded systems. DejaGnu is a testing suite written using Expect for use in testing. It has been used for testing GCC and remote targets such as embedded development.
Expect script can be automated using a tool called 'autoexpect'. This tool observes your actions and generates an Expect script using heuristics. Though generated code may be large and somewhat cryptic, one can always tweak the generated script to get the exact code.
Another example is a script that automates FTP:
Below is an example that automates SFTP (with a password):
Using passwords as command-line arguments, like in this example, is a huge security hole, as any other user on the machine can read this password by running "ps". You can, however, add code that will prompt you for your password rather than giving your password as an argument. This should be more secure. See the example below.
Another example of automated SSH login to a user machine:
Various projects implement Expect-like functionality in other languages, such as C#, Java, Scala, Groovy, Perl, Python, Ruby, Shell and Go. These are generally not exact clones of the original Expect, but the concepts tend to be very similar.