Thu Jul 8 11:39:57 PDT 2010
- Previous message: [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.
- Next message: [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=139 Summary: sighandler is calling non async safe functions Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 The sighandler function in slon.c calls slon_log() which in turn makes calls to non-async safe functions including pthread_mutex_lock() and malloc(). We should not be doing this. Occasionally my slon process kill get in a state where it stops and I can't kill it unless I do a kill -9. This might be the cause of that. We should alter sighandler to only call async safe signals (ie no slon_log) slon_terminate_worker should also not call slon_log since sighanlder calls it (but otherwise it seems safe) -- 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 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.
- Next message: [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list