前言
最近項目中遇到一個用于監控日志文件的Python包pyinotify，結合自己的項目經驗和網上的一些資料總結一下，總的原理是利用pyinotify模塊監控日志文件夾，當日志到來的情況下，觸發相應的函數進行處理，處理完畢后刪除日志文件的過程，下面就著重介紹下pyinotify
pyinotify
Pyinotify是一個Python模塊，用來監測文件系統的變化。 Pyinotify依賴于Linux內核的功能—inotify（內核2.6.13合并）。 inotify的是一個事件驅動的通知器，其通知接口通過三個系統調用從內核空間到用戶空間。pyinotify結合這些系統調用，并提供一個頂級的抽象和一個通用的方式來處理這些功能。
Inotify 可以監視的文件系統事件包括：
| Event Name | Is an Event | Description |
| IN_ACCESS | Yes | file was accessed. |
| IN_ATTRIB | Yes | metadata changed. |
| IN_CLOSE_NOWRITE | Yes | unwrittable file was closed. |
| IN_CLOSE_WRITE | Yes | writtable file was closed. |
| IN_CREATE | Yes | file/dir was created in watched directory. |
| IN_DELETE | Yes | file/dir was deleted in watched directory. |
| IN_DELETE_SELF | Yes | 自刪除，即一個可執行文件在執行時刪除自己 |
| IN_DONT_FOLLOW | No | don't follow a symlink (lk 2.6.15). |
| IN_IGNORED | Yes | raised on watched item removing. Probably useless for you, prefer instead IN_DELETE*. |
| IN_ISDIR | No | event occurred against directory. It is always piggybacked to an event. The Event structure automatically provide this information (via .is_dir) |
| IN_MASK_ADD | No | to update a mask without overwriting the previous value (lk 2.6.14). Useful when updating a watch. |
| IN_MODIFY | Yes | file was modified. |
| IN_MOVE_SELF | Yes | 自移動，即一個可執行文件在執行時移動自己 |
| IN_MOVED_FROM | Yes | file/dir in a watched dir was moved from X. Can trace the full move of an item when IN_MOVED_TO is available too, in this case if the moved item is itself watched, its path will be updated (see IN_MOVE_SELF). |
| IN_MOVED_TO | Yes | file/dir was moved to Y in a watched dir (see IN_MOVE_FROM). |
| IN_ONLYDIR | No | only watch the path if it is a directory (lk 2.6.15). Usable when calling .add_watch. |
| IN_OPEN | Yes | file was opened. |
| IN_Q_OVERFLOW | Yes | event queued overflowed. This event doesn't belongs to any particular watch. |
| IN_UNMOUNT | Yes | 宿主文件系統被 umount |
新聞熱點
疑難解答
