Fri Aug 12 10:39:14 PDT 2005
- Previous message: [Slony1-general] solaris 9 install into home dir
- Next message: [Slony1-general] win32 service code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Can anyone confirm what the slon debug level setting does (for slon 1.1) - I'm only interested in INFO messages and anything more urgent... /usr/local/pgsql/bin/slon -d 1 bpreplicate2 "dbname=bp_live user=postgres" >> /data/pgsql/data/slonlog 2>&1 gives this output in the log file: 2005-08-12 09:26:07 GMT CONFIG main: configuration complete - starting threads 2005-08-12 09:26:07 GMT DEBUG1 localListenThread: thread starts 2005-08-12 09:26:08 GMT CONFIG enableNode: no_id=2 2005-08-12 09:26:08 GMT DEBUG1 remoteWorkerThread_2: thread starts 2005-08-12 09:26:08 GMT DEBUG1 remoteListenThread_2: thread starts 2005-08-12 09:26:08 GMT DEBUG1 cleanupThread: thread starts 2005-08-12 09:26:08 GMT DEBUG1 syncThread: thread starts Does the level just control the volme of output, and not what kind of message is output? Is there a way of controlling the type of message output? What is the significance of the DEBUG1 .. DEBUG4 type messages? I'm also a little worried that too much output will quickly fill the log files on the different nodes. John
- Previous message: [Slony1-general] solaris 9 install into home dir
- Next message: [Slony1-general] win32 service code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list