Dale Worley wrote: > On Tue, 2009-03-24 at 11:43 -0400, Damian Krzeminski wrote: >> Christopher Parfitt wrote: >>> When Superadmin adds Speed Dial/BLF for a User a warning restart message >>> is seen to tell the Superadmin to restart the Presence Service. >>> If a user with no superadmin rights logs into User Portal and adds a >>> speed dial with presence, then saves and updates the phone they do not >>> see the warning error message to restart the Presence Service but it is >>> in fact still generated. >>> Even if the User saw the restart message they cannot restart the >>> presence service from the User Portal. >>> That brings up the question: Does the Presence Service have to be >>> restarted when a new Speed Dial with Presence is added or should this >>> restart message be removed? >>> >> IOW: does sipXrls need to be restarted when resource-lists.xml changes? > > No. Within a couple of seconds, sipXrls will discover that the file has > been changed and will re-read the file and reconfigure itself. sipXrls > configuration parameters in sipxrls-config do require a restart, though. > > Dale >
Good. So this is essentially the same problem as: http://track.sipfoundry.org/browse/XCF-3515 The good news it's mostly cosmetic: sipXconfig may request that you restart a service when it's not really needed. Previously every configuration file was replicated slightly differently and sipXconfig could make case-by-case decision if replicating a file requires restart. But now we use common replication infrastructure that assumes that every configuration file replication needs to be followed by service restart. I'll add a comment to that issue. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
