回复 5# sjtusonic
没注意过这个。不过synopsys的Solvnet上有一些相关信息:Question:When I open a Milkyway library in IC Compiler or Astro, I notice that a .lock file is created in the Unix library directory. What is the purpose of this file? Answer: When you open a Milkyway library with IC Compiler or Astro, the tool creates a .lock file for the library in its Unix directory. This .lock file does not prevent other users from opening the same library. A library can be opened by multiple users or processes for read and write. The purpose of the .lock file is to ensure that the library can be modified only by one process at one time. The .lock file is used as a handle for library synchronization among multiple IC Compiler executables (or any other Milkyway-based executables, such as Astro or Milkyway Environment) when multiple processes or users try to modify the library at the same time. The .lock file is not removed from the Unix library directory after the library is closed. The implementation requires the .lock file to be present in the library directory at all times, even after the library has been closed.
Question: My disk usage is being increased by the following files inside the Milkyway database created by IC Compiler: /my/path/to/design/DESIGN/CEL/my_cell:1@nnnMMMHow are these files created and used by IC Compiler, and can I manually remove them? Answer: These files are temporary files created by IC Compiler during the execution of certain commands. After these commands complete, IC Compiler removes these temporary files. If for some reason IC Compiler does not successfully complete the command, either through a user 'kill' sequence or a tool fatal, these temporary files might remain inside the database. These files might also appear if you copy a Milkyway database while a cell is open and commands are actively being run on it. The naming convention for these files is DESIGN_LIB/CEL/CEL_NAME:version@process_idMachineNameIt is safe to remove these temporary files as long as the corresponding design cell is not open. The safest way to do this is to check for .lock files that match the following pattern: CEL_NAME:version.lock. If there is no lock file, it is safe to remove these @ temporary files. If there is a .lock file, you should check with the owner of the lock file before removing these @ files.
Question:
When I try to open a library, Astro fails with the following messages:INFO: Could not lock the library for write, locked by another user. Trying again...INFO: Could not lock the library for write, locked by another user. Trying again......INFO: Could not lock the library for write, giving up.Error: cannot open library bali for write. (MW-006)Fail to execute commandAnswer:
Often this is caused when there is a network problem or Astro terminated abnormally, leaving an idle process ID.First check for the presence of any .lock files or any *.lock cells in your Milkyway design library. If there are any present, delete them using the UNIXdelete command "rm".If Astro still issues the failed messages, as a workaround, set the followingto turn off library locking:dbSetNewLibLockMode #f |