Warning: do not SIGHUP master (2.1.17 or 2.2.10) to add or remove services

[Henrique de Moraes Holschuh]

See http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2582

As far as I can tell, if you are unlucky enough to cause a realloc by adding
a service, you may get memory corruption if there are *any* workers of *any*
service running, as soon as they exit/die.

Also, if there are any workers left for a removed service, it may also
cause memory corruption when they exit/die and master notices it.

The amount of damage depends *only* on your luck. It could be none. It could
be some annoying noise on syslog. It could be a completely deranged Cyrus
master doing something really not amusing to a production server.

Mucking around with an existing service (e.g. changing command line
parameters, or listening socket) is safe.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html