Mon Oct 14 10:57:50 PDT 2013
- Previous message: [Slony1-bugs] [Bug 316] WAIT FOR EVENT with a non-existing CONFIRMED node is a no-op
- Next message: [Slony1-bugs] [Bug 317] When stdout of slonik is not a terminal it is fully buffered
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=317 Summary: When stdout of slonik is not a terminal it is fully buffered Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: slonik AssignedTo: slony1-bugs at lists.slony.info ReportedBy: janwieck at yahoo.com CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 Slonik uses both, stdout and stderr. When stdout is not a terminal, it becomes fully buffered by default. If slonik dies with a crash, the last of stdout may be lost in this case. Also if stdout and stderr are combined at a higher level, messages can appear out of order. I propose to call setlinebuf(3) on stdout at the start of slonik. I further propose to move all output to stdout. That includes implementing a notice processor that will use the same output function that adds the script position to other messages. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 316] WAIT FOR EVENT with a non-existing CONFIRMED node is a no-op
- Next message: [Slony1-bugs] [Bug 317] When stdout of slonik is not a terminal it is fully buffered
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list