将状态栏历史写入日志文件的能力。
将任何构建时错误写入日志输出文件。
各罐质量必须写入日志文件，以便审计。
Each jar's mass must be written to a log file for auditing purposes.
下面的代码列出了将写入日志的最后输出。
The resulting output that would be written to the log is listed following the code.
一旦写入数据块，元数据将随后写入日志。
Once they are written, the metadata changes are then written to the journal.
可以采取多种方式进行写入日志文件的工作。
Writing out to a log file can be handled in a number of different ways.
随意将自变量列表写入日志中。
警告可以忽略或写入日志。
traceLevel是写入日志文件的跟踪级别。
最简单的方式就是把信息定期地写入日志文件。
The easiest way is to write the information to a log file periodically.
可能对脚本最简单的改进就是将脚本的输出写入日志文件。
Probably the simplest improvement you can make to your scripts is to write the output from your script to a log file.
在日志记录被写入日志文件之前，它们首先会被写到缓冲区。
Before log files are written to the log files, they are first written into buffers.
记住，写入日志文件是按顺序进行的，正是这一点提高了性能。
Remember that writes to the log files are sequential, which is where we get our performance win.
所有新数据首先写入日志，然后再写入它的最终位置。
All new data is written to the journal first, and then to its final location.
每五秒钟查询一个可用物理内存并将结果写入日志文件。
Every five seconds, query the available physical memory and write the result to the log file.
想一下该中介如何将关于消息的会话和上下文数据简单地写入日志。
You will recall that this mediation simply wrote session and context data about the message to the log.
此外，一些错误消息只在执行历史中可见，并且不会写入日志。
Additionally, some error messages will be visible only within the execution history, and will not be logged.
第二种机制在命令行参数输出的指令控制下，把自己标准输入中的行写入日志文件。
It writes lines from its standard input to log files under the control of instructions you enter as command-line arguments.
建立指定的源名称作为向本地计算机上的日志中写入日志项的有效事件源。
Establishes the specified source name as a valid event source for writing entries to a log on the local computer.
在该脚本中，您将学习如何导入特定函数的模块，如何使用文件，以及如何写入日志文件。
In this script, you're going to learn how to import modules for specific functions, how to work with files, and how to write to a log file.
提高日志级别会导致性能降级，因为需要协调额外的I/O操作，以便将它们写入日志文件。
Increasing the level of logging will cause performance to degrade because of the additional I/O operations that need to be coordinated to write to the log files.
错误页面可以显示一个友好的信息给用户，然后可以将相关的异常信息写入日志以供管理员日后查看。
The error page can then display a friendly error message to the user, and then perhaps log the relevant exception information for the system administrator to review at a later time.
这个结果与写入日志文件的信息是相同的，并且你会发现在每一个项目的左边都有一个复选框。
This result and information of writing into daily record file are the same, and you will find that there is a final election frame on the left of every project.
您可以创建自定义日志记录文件并向其中写入日志消息，但是为什么不使用已经提供给您的工具呢？
You could create a custom logging file and write log messages to it, but why not use the tools that have already been provided for you?
首先写入日志，然后再写入数据库，这样做的最大好处在于，所有日志文件写入操作本质上都是按顺序进行的。
The biggest benefit of writing to the log first, then writing to the database is that all writes to log files are sequential in nature.
例如，安装了正确的Ant扩展任务后，可以触发ftp传输，可以写入日志文件或执行另一个操作系统进程。
For instance, with the right Ant extension tasks installed, an FTP transfer could be triggered, a log file could be written, or another operating system process could be executed.
一旦整个事务内容被写入日志文件中，会写一个“commitblock"到日志文件，以表明日志文件中的事务日志写操作完成。
Once the entire transaction log has been written to the journal, then a “commit block” is written indicating that the transaction log in the journal is complete.
最后提交包含该insert的事务，如果这时日志缓冲区中的记录还没有被写入日志文件的话，则将这些记录写到日志文件中。
The transaction containing the insert is (eventually) committed, at which point the log buffer record(s) are written to the log disk if they haven't already been.
向数据库中写入日志比向文本文件中写入日志要慢一点，尤其是在忙碌的站点上，而且数据库会变得很大以至于维护成为一个问题。
Logging to a database is somewhat slower than logging to text files, especially at busy sites, and the size of the database can become large so that maintenance becomes an issue.
如果由于某种原因该记录不能把这些写入日志，最后结果会是Rollback(在本文实例中使用了presumedabort)。
If this record fails to make it to the log for any reason, the ultimate outcome will be to Rollback (we are using presumed abort in this example).
应用推荐