他们的代码不得不这样做，因为需要满足开发者在不同浏览器中运行脚本的需求。
They have to because they fill a need for developers to have their scripts run cross-browser.
另外，因为这个流程已经脚本化了，可以在全面的自动化部署中通过无头流程运行它。
What's more, because it's scripted, it can be run by a headless process as part of a comprehensive automated deployment.
在脚本中定期运行此选项可确保自动清理捕获文件以删除未使用的SQL。
Having this option in a script that runs regularly can ensure automatic cleanup of the capture file to remove unused SQL.
同样，在命令行中运行此脚本后，会看到如清单14所示的输出。
Once again, after I run this script on the command line, I see the output in Listing 14.
在我们的示例中，我们提供了一个简单的ant脚本来运行增强程序。
In our example, we have provided a simple ANT script that runs the enhancer.
在命令行中运行此脚本时，输出如清单12所示。
When I run this script on the command line, I see the output in Listing 12.
务必记住，优秀的实用程序能够设法在shell脚本中作为根(root)用户身份运行。
Keep in mind that a good utility might find its way into a shell script run as root.
在设备中运行的路由脚本从远程Web服务器存储库获取路由规则列表。
The route script running inside the appliance fetches a routing rules list from the remote Web server repository.
接下来，在ApacheWeb服务器中运行input . php脚本。
在命令行中运行此脚本，然后查看输出的.swf文件，效果如图3所示。
When I run this script on the command line, then look at the output.swf file, I see the image shown in Figure 3.
运行清单8 中的SQL脚本，在MySQL数据库中创建一个反馈模式。
Run the SQL script in Listing 8 to create a feedback schema in your MySQL database.
在Lift中创建视图并不需要运行任何脚本。
在命令行中运行J2Cant脚本。
一定要牢记，CLI是建立在Jython2.2.1的基础上的，因此这个级别的Jython所支持的大部分功能都可以用于在CLI环境中运行的脚本。
Keep in mind that the CLI is based on Jython 2.2.1, so most of the functionality supported by this level of Jython is available to scripts that are run within the CLI environment.
在命令行中运行此脚本并在浏览器中查看image . swf，结果如图4所示。
When I run this script on the command line and look at image.swf in my browser, I see something like Figure 4.
在保存该脚本之后，您可以运行它，如清单5中所示。
After you save the script, you run it as shown in Listing 5.
模式：创建能够在不同的平台和目标环境中运行的单一部署脚本。
Pattern: Create a single deployment script capable of running on different platforms and target environments.
在运行了该脚本之后，您可以在NIM服务器中运行下面的脚本，以获取备份镜像。
After running this script, you can run the following script from your NIM server to retrieve the backup image.
这使得可以通过在部署流程中运行不同的脚本来对不同的配置使用相同的映像。
This enables the same image to be used for different configurations just by running different scripts during the deployment process.
还可以避免编辑在主站点和灾难恢复站点上运行的脚本，只需在脚本中添加代码，让脚本能够探测运行它们的位置。
Maybe you can avoid editing scripts to run on the primary versus the disaster recovery site and simply add code to the scripts so that they detect where they are running.
如果服务不在运行中，在启动脚本中，它就会被修复。
If the service is not running and in the startup scripts, it will be fixed.
该命令创建一个脚本，该脚本将自动运行，并存储在发出该命令的目录中。
The command creates a script that is run automatically and stored in the directory from which the command was issued.
在本文中，我们了解了如何在无人参与的脚本中运行命令、捕获输出和监视脚本中不同命令的执行。
In this article, you've looked at how to run commands in an unattended script, captured their output, and monitored the execution of different commands in the script.
在一个现代应用程序部署中，可以在几个嵌套启动脚本中设置选项，应用程序实际运行哪些选项并不总是很清楚。
In a modern application deployment, options can be set in several nested launch scripts, and it's not always clear which options the application is actually being run with.
在代码归档中可以找到此脚本的完整运行版本。
A fully functioning version of this script can be found in the code archive.
在命令行运行该脚本并输出文本配置文件中的内容，能够看到下列输出。
When I run the script on the command line and print the contents of the text configuration file, I see the output shown below.
如同以上的provider_url值，如果您是在不同的机器上安装或您的队列管理器在不同的端口运行，则需要在脚本中修改这些设置。
Like the PROVIDER_URL value used earlier, if your install is running on a different machine or your queue manager is running on a different port, you will need to modify these Settings in your script.
DB 2设置要运行的脚本(在步骤1中或者按本系列第一篇文章中的步骤操作时)，并为DB 2数据库中的帐户组合信息创建目标表。
The DB2 set up script that you ran (either in step 1 or when following the steps in the first article of this series) created a target table for account portfolio information in your DB2 database.
另外，其实很少有人真正意识到究竟是什么原因导致脚本在不同的浏览器中运行时间过长，连我自己都没有深究过。
Still, few web developers truly understand what triggers the long-running script dialog in various browsers, including myself.
scala不支持在直接运行于scala解释器中的脚本里加入包的声明。
Scala does not allow package declarations in scripts that are executed directly with the scala interpreter.
应用推荐