1·The process writes whatever data it can until the end of the buffer, and the remaining data is copied to start overwriting the previous log entry.
该进程写入数据，一直到达缓冲区的末尾，然后将剩余的数据复制到缓冲区的开始位置，覆盖以前的日志条目。
2·In this strategy, once the last primary log file is filled in the log directory, new transactions will be written to the first log file thereby overwriting existing log data.
在此策略中，一旦日志目录中最后一个主日志文件被写满了，就会将新的事务写到第一个日志文件中，从而覆盖现有的日志数据。
3·You must ensure, for example, that you are appending, not overwriting, information to the log file (see Listing 6).
例如，您必须确保是将信息追加(而不是覆盖)到日志文件中(请参见清单6)。
4·Normally for an FTP, this would mean resubmitting the job and overwriting the original transfer.
对于FTP来说，这通常意味着要重新提交作业并覆盖原来的传输。
5·During upgrades, RPM will attempt to avoid overwriting a user's carefully modified configuration with an RPM-packaged default configuration file.
在升级期间，RPM将尝试避免使用RPM打包的默认配置文件覆盖用户小心修改的配置。
1·Similarly, all accesses to arrays and strings are checked at run-time to ensure that they are in bounds, eliminating the possibility of overwriting memory and corrupting data.
类似地，所有对字符串和数组的访问在运行时被检查来确保他们没有越界，消除越界导致的内存重写和数据损坏的问题。
2·Now let's talk about how a given process's execution flow can be changed by overwriting a local variable in 64-bit mode.
现在让我们讨论一下，如何通过在64位模式下重写局部变量更改给定进程的执行流程。
3·Preserving a slot's original value before overwriting enables the live object set to be preserved and processed.
在重写启用活对象设置保护和处理之前保留槽的原始值。
4·By default, the Web services wizard will replace your previous skeleton class and any business logic in it with a fresh skeleton (provided you have enabled file overwriting).
默认情况下，服务向导将会用最新的框架(倘若您已经激活了文件的重写)来取代您先前的框架类和它里面的任何业务逻辑。
5·For this scenario, you also want to merge the new SQL with the existing configured PDQXML file without overwriting the Settings already configured for PDQXML.
对于此场景，您需要在不重写已经为pd qx ml设置好的配置的情况下，将新的SQL合并到已配置的pd qxml文件中。