Fri Aug 21 11:17:04 PDT 2009
- Previous message: [Slony1-general] Master/slave replication priority on slony1/2
- Next message: [Slony1-general] fork() and debug stdout/stderror -- time to clean it up?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
All: So Slony has been around in one form or another since 2004, but to this day it continues to send stdout/stderr to the PTY/TTY from which it was spawned, even after fork()'s the daemon. Even if init(8) spawned it on console, which data center terminal servers just love. Can I get a show of hands who else would like this adjusted? Its just not compliant with POSIX system standard, or generally accepted industry practices. ~BAS
- Previous message: [Slony1-general] Master/slave replication priority on slony1/2
- Next message: [Slony1-general] fork() and debug stdout/stderror -- time to clean it up?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list