Fri Aug 27 11:30:28 PDT 2010
- Previous message: [Slony1-commit] Slony-I-commit When doing a fail node where the failed node is not a pr
- Next message: [Slony1-commit] Slony-I-commit If the nodelock can not be obtained then the worker will
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Commit: http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=e692b6c6ecee3a6ff0539a40245dbceb4ef8f85c Log Message ----------- Replace usage of alarm() for restarting slon with a KILL of the child and a sleep before restarting. Numerous instances were observed where the parent/watchdog slon instance would exit on a SIGALRM. The various POSIX standards define rules about what functions can be called by a signal handler. We suspect not following these guidelines was part of the problem. Branch ------ REL_2_0_STABLE Modified Files -------------- src/slon/slon.c | 15 ++------------- 1 files changed, 2 insertions(+), 13 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit When doing a fail node where the failed node is not a pr
- Next message: [Slony1-commit] Slony-I-commit If the nodelock can not be obtained then the worker will
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list