Package Products :: Package ZenUtils :: Module configlog :: Class ZenRotatingFileHandler |
[hide private]
[frames] | no frames]

# Class ZenRotatingFileHandler

source code

              object --+
                       |
        logging.Filterer --+
                           |
             logging.Handler --+
                               |
           logging.StreamHandler --+
                                   |
                 logging.FileHandler --+
                                       |
    logging.handlers.BaseRotatingHandler --+
                                           |
        logging.handlers.RotatingFileHandler --+
                                               |
                                              ZenRotatingFileHandler

Like python's RotatingFileHandler but relative to ZENHOME/log/

Instance Methods | [hide private]
__init__(self, filename, mode='a', maxBytes=0, backupCount=0, encoding=None, delay=0) Open the specified file and use it as the stream for logging. | source code
Inherited from `logging.handlers.RotatingFileHandler`: `doRollover`, `shouldRollover` Inherited from `logging.handlers.BaseRotatingHandler`: `emit` Inherited from `logging.FileHandler`: `close` Inherited from `logging.FileHandler` (private): `_open` Inherited from `logging.StreamHandler`: `flush` Inherited from `logging.Handler`: `acquire`, `createLock`, `format`, `get_name`, `handle`, `handleError`, `release`, `setFormatter`, `setLevel`, `set_name` Inherited from `logging.Filterer`: `addFilter`, `filter`, `removeFilter`

Class Variables | [hide private]
Inherited from `logging.Handler`: `name`

Method Details | [hide private]

### __init__(self, filename, mode='a', maxBytes=0, backupCount=0, encoding=None, delay=0) (Constructor) | source code
Open the specified file and use it as the stream for logging. By default, the file grows indefinitely. You can specify particular values of maxBytes and backupCount to allow the file to rollover at a predetermined size. Rollover occurs whenever the current log file is nearly maxBytes in length. If backupCount is >= 1, the system will successively create new files with the same pathname as the base file, but with extensions ".1", ".2" etc. appended to it. For example, with a backupCount of 5 and a base file name of "app.log", you would get "app.log", "app.log.1", "app.log.2", ... through to "app.log.5". The file being written to is always "app.log" - when it gets filled up, it is closed and renamed to "app.log.1", and if files "app.log.1", "app.log.2" etc. exist, then they are renamed to "app.log.2", "app.log.3" etc. respectively. If maxBytes is zero, rollover never occurs. Overrides: logging.Filterer.__init__ (inherited documentation)