原文答案：http://unix.stackexchange.com/questions/12815/what-are-pid-and-lock-files-for

創(chuàng)新互聯(lián)公司專注于洛川網(wǎng)站建設(shè)服務(wù)及定制，我們擁有豐富的企業(yè)做網(wǎng)站經(jīng)驗。 熱誠為您提供洛川營銷型網(wǎng)站建設(shè)，洛川網(wǎng)站制作、洛川網(wǎng)頁設(shè)計、洛川網(wǎng)站官網(wǎng)定制、微信小程序開發(fā)服務(wù)，打造洛川網(wǎng)絡(luò)公司原創(chuàng)品牌,更為您提供洛川網(wǎng)站排名全網(wǎng)營銷落地服務(wù)。

大意翻譯如下：

pidfile 是用戶程序正在開始運行期間，將進(jìn)程ID寫進(jìn)pidfile文件，主要目的有三個：

    1.為其他程序或操作系統(tǒng)標(biāo)識本程序正在運行，或至少啟動成功了。

    2.如果計劃要用kill命令終止進(jìn)行，它允許一個可寫腳本非常容易地檢測程序運行狀態(tài)。

    3.有pidfile后，可以用非常少的代價去獲取前一個運行實例因何沒有退出成功

僅僅存在pidfile并不能保證進(jìn)程id是否正在運行，這個方法不是100%簡單，但對大多數(shù)程序來說是足夠好的，檢測進(jìn)程id是否在進(jìn)程表這個方式并不能跨平臺使用，除非使用 ps工具。

lockfile 通常用來保證同一程序的兩個實例不能同時運行，使用完后別忘記刪除這個文件

pid files are written by some programs to record their process ID while they are starting. This has multiple purposes:

• It's a signal to other processes and users of the system that that particular program is running, or at least started successfully.

• It allows one to write a script really easy to check if it's running and issue a plain kill command if one wants to end it.

• It's a cheap way for a program to see if a previous running instance of it did not exit successfully.

Mere presence of a pid file doesn't guarantee that that particular process id is running, of course, so this method isn't 100% foolproof but "good enough" in a lot of instances. Checking if a particular PID exists in the process table isn't totally portable across UNIX-like operating systems unless you want to depend on the ps utility, which may not be desirable to call in all instances (and I believe some UNIX-like operating systems implement ps differently anyway).

Lock files are used by programs to ensure two (well-behaved) separate instances of a program, which may be running concurrently on one system, don't access something else at the same time. The idea is before the program accesses its resource, it checks for presence of a lock file, and if the lock file exists, either error out or wait for it to go away. When it doesn't exist, the program wanting to "acquire" the resource creates the file, and then other instances that might come across later will wait for this process to be done with it. Of course, this assumes the program "acquiring" the lock does in fact release it and doesn't forget to delete the lock file.

This works because the filesystem under all UNIX-like operating systems enforces serialization, which means only one change to the filesystem actually happens at any given time. Sort of like locks with databases and such.