Avoid to catch the SIGCHLD signal triggered every five minutes
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	dereckson
	Dec 19 2015, 07:59

Tags

Referenced Files

None

Subscribers

Description

Every five minutes, a SIGCHLD is sent to the Wearg process.

We should use a table of signals to capture ignoring SIGCHLD in RabbitMQ or we should avoid to call broker::get_messages where the seconds is 0 and the minute is a multiple of five.

00:00:00 <wearg> [DEBUG] Ignoring SIGCHLD
00:00:16 <wearg> [00:00:16] --- Sat Dec 19 2015
01:00:00 <wearg> [DEBUG] Ignoring SIGCHLD
01:30:00 <wearg> [DEBUG] Ignoring SIGCHLD
05:55:00 <wearg> [DEBUG] Ignoring SIGCHLD
06:55:00 <wearg> [DEBUG] Ignoring SIGCHLD

Revisions and Commits

rVIPERSERV ViperServ scripts [legacy Mercurial repo]
	D111	rVIPERSERVdd5b1b408ce3 Bypass message queue when it risks a collision with SIGCHLD.

Event Timeline

dereckson created this task.Dec 19 2015, 07:59

dereckson raised the priority of this task from to Normal.

dereckson updated the task description. (Show Details)

dereckson added projects: Dæghrefn, Message queues, rabbitmq-tcl.

dereckson added a subscriber: dereckson.

dereckson added a revision: D111: Bypass message queue when it risks a collision with SIGCHLD..Dec 19 2015, 17:46

dereckson moved this task from Backlog to Need a volunteer on the Message queues board.Dec 21 2015, 20:10

dereckson closed this task as Resolved by committing rVIPERSERVdd5b1b408ce3: Bypass message queue when it risks a collision with SIGCHLD..Dec 27 2015, 09:59

dereckson added a commit: rVIPERSERVdd5b1b408ce3: Bypass message queue when it risks a collision with SIGCHLD..