在键入信息时，确保信息像上文介绍的那样准确。可以包含自己选择的错误文件。
When typing in the information, make certain you type it exactly as it appears above. You can include the error documents of your choice.
在这种情况下，如果你想在错误文件改变的关键是正确的盐，你可以点击这里，复制和粘贴它回到它应该。
In this particular case, if you want to just correct that salt key changed in the wrong file, you can check it here, copy and paste it back where it should be.
如果这个文件不包含任何错误消息，就说明集成是成功的。
If the file does not contain any error messages, your integration was successful.
我们需要明确的错误消息和选择文件的便利方法。
We need clear error messages and a convenient way to select the files.
错误消息处理需要此日志文件。
所有程序都不可避免地会生成错误——找不到文件、内存不足等等。
All programs inevitably generate errors — files not found, running out of memory, etc.
将显示关于缺少映射文件的错误消息。
CVS也没有这样的命令，但在CVS中，您完全有可能在不毁掉存储库的情况下手动删除错误提交的文件。
CVS doesn't have an obliterate command either; but in CVS, it is possible to manually delete mistakenly committed files without damaging the repository.
如果找不到合适的过滤器，尝试打印文件就会产生错误消息。
If a suitable filter cannot be found, your attempt to print a file will result in an error message.
任何策略文件错误定义或采用快捷方式都是一个不容易发现的漏洞。
Any policy file definition mistakes made or short cuts taken leaves open vulnerabilities that can not be easily identified.
如果用户试图添加或创建超出该限制的文件，那么将返回一个错误(超出文件系统空间)。
If a user tries to add or create a file that goes beyond that level, an error is returned (out of file system space).
因此，很难捕获和改正包含的模板文件中的错误。
As a result, it can be difficult to catch and correct errors in included template files.
IO错误、网络错误和其他系统错误都会记录到这个文件中。
Errors with IO, networking, and other general system errors are reported in this file.
DB 2实例可能由于各种原因而不可用：文件许可错误变更，文件删除，或者文件系统不可用。
A DB2 instance may become unavailable for a number of reasons: file permissions mistakenly changed, files deleted, or file systems being unavailable.
然而，它的确会发生，大部分原因经常是硬件出错和操作错误(比如日志文件被删)。
It can happen, however, most often due to faulty hardware or operational mistakes (like deleting a transaction log file).
使用GRUB，如果配置文件配置错误，则只是默认转到GRUB命令行界面。
With GRUB, if the configuration file is configured incorrectly, it will simply default to the GRUB command-line interface.
如果该文件受到损坏，您将看到错误摘要，后面是文件已经恢复的通知。
If the file is corrupted, you will see a summary of the errors followed by a note that the file has been restored.
如果没有其他错误，mailerror. log文件将为空，并将发送包含错误信息的电子邮件。
If there were no other errors, the mailerror.log file will be empty, and email is sent with the error information.
先采用0值，然后逐渐增加它，直到出现文件错误，再降低它。
Start with a value of 0 and increase it slowly until file errors occur and then bring it back down
ApplicationServer系统、错误和ffdc文件。
查找和更正完错误之后，保存文件并运行dw - transform . vbs以再次验证。
After you have located and corrected your error, save the file and run dw-transform.vbs again to recheck it.
查找和更正完错误之后，保存文件并运行dw -transform . vbs以再次验证。
After you have located and corrected your error, save the file and rerun the dw-transform.sh script to recheck your file.
使用ODC_DEFAULT将设置错误日志文件位置的缺省值。
Using ODC_DEFAULT sets the default value of the error log file location. The following syntax is used to set the property.
在此之前，我们想在出现错误404(文件未找到)时，会显示一个好看的页面；我们使用Plack：Middleware：ErrorDocument来完成这项任务。
On top of this we want to have a nice looking page when there is a 404 (file not found); for this we will use Plack: : Middleware: : ErrorDocument.
一个segfault，当特定的日志文件出现错误授权时出现。
A segfault that resulted when a specific logfile had wrong permissions.
大部分Web开发人员都会检查错误的文件引用，但是这里仍然需要说明一下。
Most Web developers check bad file references, but it's worth mentioning.
如果存在任何错误，那么这个概要文件被保存，但是不会创建一个概要文件版本。
If there are any errors found, then the profile is saved, but a profile version is not created.
如果创建了核心文件，错误日志记录进程应该会记录一个错误日志项，这个进程常常在发生第一个软件故障时启动。
If a core file has been created, there should be an error log entry logged by the error-logging process, which is usually started when the first software failure occurs.
如果创建了核心文件，错误日志记录进程应该会记录一个错误日志项，这个进程常常在发生第一个软件故障时启动。
If a core file has been created, there should be an error log entry logged by the error-logging process, which is usually started when the first software failure occurs.
应用推荐