2017-03-08 78 views
0

我遇到了一个问题,通过pyinotify及其线程持续存在日志文件写入流。我正在使用pyinotify来监视CLOSE_WRITE文件事件的目录。之前我初始化pyinotify我使用内置的logging模块,像这样创建一个日志流:Python持久化PyInotify日志文件流

import os, logging 
from logging import handlers 
from logging.config import dictConfig 


log_dir = './var/log' 
name = 'com.sadmicrowave.tesseract' 
LOG_SETTINGS = { 'version' : 1 
       ,'handlers': { 'core': { 
            # make the logger a rotating file handler so the file automatically gets archived and a new one gets created, preventing files from becoming too large they are unmaintainable. 
            'class'  : 'logging.handlers.RotatingFileHandler' 
            # by setting our logger to the DEBUG level (lowest level) we will include all other levels by default 
            ,'level'  : 'DEBUG' 
            # this references the 'core' handler located in the 'formatters' dict element below 
            ,'formatter' : 'core' 
            # the path and file name of the output log file 
            ,'filename'  : os.path.join(log_dir, "%s.log" % name) 
            ,'mode'   : 'a' 
            # the max size we want to log file to reach before it gets archived and a new file gets created 
            ,'maxBytes'  : 100000 
            # the max number of files we want to keep in archive 
            ,'backupCount' : 5 } 
          } 
          # create the formatters which are referenced in the handlers section above 
          ,'formatters': {'core': {'format': '%(levelname)s %(asctime)s %(module)s|%(funcName)s %(lineno)d: %(message)s' 
              } 
          } 
          ,'loggers' : {'root': { 
                 'level'  : 'DEBUG' # The most granular level of logging available in the log module 
                 ,'handlers' : ['core'] 
              } 
          } 
         } 

# use the built-in logger dict configuration tool to convert the dict to a logger config 
dictConfig(LOG_SETTINGS) 

# get the logger created in the config and named root in the 'loggers' section of the config 
__log = logging.getLogger('root') 

于是,经过我的__log变量初始化得到它的工作原理,立即允许日志写入。我想下次启动pyinotify实例,并希望使用下面的类定义传递__log

import asyncore, pyinotify 

class Notify (object): 
    def __init__ (self, log=None, verbose=True): 
     wm = pyinotify.WatchManager() 
     wm.add_watch('/path/to/folder/to/monitor/', pyinotify.IN_CLOSE_WRITE, proc_fun=processEvent(log, verbose)) 

     notifier = pyinotify.AsyncNotifier(wm, None) 
     asyncore.loop() 

class processEvent (pyinotify.ProcessEvent): 
    def __init__ (self, log=None, verbose=True): 
     log.info('logging some cool stuff') 

     self.__log    = log 
     self.__verbose   = verbose 

    def process_IN_CLOSE_WRITE (self, event): 
     print event 

在上面的实现,我process_IN_CLOSE_WRITE方法被触发正是从pyinotify.AsyncNotifier预期;但是,logging some cool stuff的日志行从不写入日志文件。

我觉得它与通过pyinotify线程过程持续文件流有关;不过,我不知道如何解决这个问题。

任何想法?

回答

0

我可能找到了一个似乎可行的解决方案。不知道这是否是最好的方法,所以我现在将OP打开以查看是否发布了其他想法。

我想我是在处理我的pyinotify.AsyncNotifier设置错误。我改变了实施:现在

class Notify (object): 
    def __init__ (self, log=None, verbose=True): 
     notifiers = [] 
     descriptors = [] 
     wm = pyinotify.WatchManager() 
     notifiers.append (pyinotify.AsyncNotifier(wm, processEvent(log, verbose))) 
     descriptors.append(wm.add_watch('/path/to/folder/to/monitor/', pyinotify.IN_CLOSE_WRITE, proc_fun=processEvent(log, verbose), auto_add=True) 

     asyncore.loop() 

,当我的包装类processEvents被触发听者的实例,当一个事件从CLOSE_WRITE事件触发,log对象保持并适当地过去了,可接收写事件。

+0

不幸的是,一旦我使用'python-daemon'和'files_preserve'添加了demonization组件,我的日志流再次消失,我的pyinotify事件无法登录到它 – sadmicrowave