我们已经分析了如何正确地创建锁文件及其替代者。
We've examined how to create lock files correctly and alternatives.
如果锁文件存在，应该在重新启动服务器之前删除它。
If the lock file is present, delete it before restarting the server.
确保只有您可以信任的程序才能添加或者删除锁文件！
Make sure that only programs you can trust can add and remove these lock files.
最大的好处就是当JVM挂了锁文件可以正常的移除。
The primary benefit of NativeFSLockFactory is that lock files will be properly removed (by the OS) if the JVM has an abnormal exit.
排他锁。除加锁进程外其他进程没有对已加锁文件读写访问权限。
LOCK_EX an exclusive lock. This denies all other processes both read and write access to the file.
在手动删除数据库锁文件之前，请务必确认在数据库机器上没有JVM在运行。
Be sure to verify that no JVMs are running on the database machine before manually removing a database lock file.
追加的文件名称，其中包括索引和锁文件，都是从这里计算的获得的。
The names for supplemental files, including index and lock files, will be computed from this.
如果一个点锁文件已存在，等待再次尝试创建一个点锁文件的秒数(默认：5)。
Number of seconds to wait to try again to create a dot-lock file, if one already exists (default: 5).
当数据库没有被正确关闭(例如，崩溃或中止)时，就会留下一个“孤立的”数据库锁文件。
When a database is not properly shutdown (for example, a crash or an abort) an 'orphan' database lock file will be left.
根据同样的思路，您应该将设备锁文件之类的锁文件放置在 /var/lock 中。
In a similar vein, you should place lock files for things like device lock files in /var/lock.
主存储文件的路径名。追加的文件名称，其中包括索引和锁文件，都是从这里计算的获得的。
Path name to the main storage file. the names for supplemental files, including index and lock files, will be computed from this.
问题是，root总是可以这样创建文件，即便锁文件已经存在，这意味着该锁不能为root正常工作。
The problem is that root can always create files this way, even if the lock file already exists — which means that the lock won't work correctly for root.
如果发生系统突然关机或panic,MUI可能在启动时很难打开，因为系统崩溃时MUI没有适当的时间来清除剩余的锁文件。
In the event of a sudden system shutdown or panic, the MUI may have trouble starting when booting up because the MUI doesn't have the proper time to clean up leftover lock files when a system fails.
他打开盒子的锁，在文件里分类拣选。
为了保密，这些文件都加了锁。
最后，所有现有语句和CL命令在整个文件上需要一个互斥型锁。
Lastly, all the existing statements and cl commands required an exclusive lock on the entire file.
根据创建数据库所使用的数据定义语言 (DDL)模式文件，可以确定正在使用的锁类型。
You can determine the types of locks being used from the Data Definition Language (DDL) schema files used to create the database.
基表上不需要额外的锁，因为复制只分析日志文件，而不是分析基表。
No extra locking is required on the base tables as replication only analyzes the log files and not the base tables.
如前所述，之前所有用于修改媒介首选项的方法都要求对整个文件使用互斥型锁。
As mentioned earlier, all previous mechanisms of changing the media preference required an exclusive lock on the entire file.
使用单独的文件来表示锁是一个非常古老的方法。
Using a separate file to indicate a lock is an old way of doing things.
FD列中的大写W表示该应用程序具有对整个文件的写锁。
The capital W in the FD column indicates that the application has a write lock on the whole file.
有些提供了文件锁来防止多个用户的并行访问。
例如，清单7中的接口定义用于配置应用程序的文件锁的字段。
For example, the interface in Listing 7 defines fields for configuring an application's file locks.
本文中将学习如何使用Boostipc库实现共享内存对象、消息队列和同步文件锁。
In this article, you learn how to use the Boost IPC library to implement Shared memory objects, message queues, and synchronized file locking.
这是因为JFS2在实现时使用了写独占(write - exclusive)索引节点锁，允许多个用户同时读取相同的文件。
This is due to the way in which JFS2 is implemented with a write-exclusive inode lock, allowing multiples users to read the same file simultaneously.
您此时可能想到使用文件锁或其他特定于操作系统的技巧，以在分布式环境中同步对文件的访问。
You might have some ideas about using file locking or other operating system-specific tricks to synchronize access to a file in a distributed environment.
文件锁定支持的重构让服务器可以用基于租约的模型来保持文件的锁状态。
The restructuring of file locking support allows the server to maintain the lock state of files using a lease-based model.
写操作完成之后，它刷新文件缓冲区并解除文件锁。
On completion of the writing, it flushes the file buffers and unlocks the file.
ENOLCK：没有可用的锁；您已达到系统对文件锁或记录锁的限制范围。
ENOLCK — No locks are available; you've reached a system-wide limit on file or record locks.
应用推荐