Fri Aug 21 14:41:38 PDT 2009
- Previous message: [Slony1-general] fork() and debug stdout/stderror -- time to clean it up?
- Next message: [Slony1-general] More on 8.4 .vs. Slony 2.0.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Brian A. Seklecki" <seklecki at noc.cfi.pgh.pa.us> writes: > 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. I wouldn't object to seeing a patch to improve this matter... If it takes some work, but doesn't look heinous, I'd join in on the remediation... -- output = reverse("ofni.sailifa.ac" "@" "enworbbc") Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-general] fork() and debug stdout/stderror -- time to clean it up?
- Next message: [Slony1-general] More on 8.4 .vs. Slony 2.0.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list