----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/4282/#review14019 -----------------------------------------------------------
Ship it! Ew. Ew ew ew. On the other hand, I can't think of another way to do this and restore the behaviour that used to exist. So, blech. - Matt Jordan On Dec. 17, 2014, 4:55 p.m., rmudgett wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/4282/ > ----------------------------------------------------------- > > (Updated Dec. 17, 2014, 4:55 p.m.) > > > Review request for Asterisk Developers. > > > Repository: Asterisk > > > Description > ------- > > The QUEUESTART log entry has historically acted like a fully booted event for > the queue_log file. When the QUEUESTART entry was posted to the log was > broken by the change made by ASTERISK-15863. > > * Made post the QUEUESTART queue_log entry when Asterisk fully boots. This > restores the intent of that log entry and happens after realtime has had a > chance to load. > > > Diffs > ----- > > /branches/11/main/logger.c 429698 > /branches/11/main/asterisk.c 429698 > /branches/11/include/asterisk/_private.h 429698 > > Diff: https://reviewboard.asterisk.org/r/4282/diff/ > > > Testing > ------- > > The QUEUESTART entry is now written to the queue_log file when Asterisk boots > rather than waiting for the first event to happen. > > > Thanks, > > rmudgett > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
