James Golovich wrote: > Option 2 is the way I implemented it, although I actually did it in > reverse since there is still a short time before receiving the command > that verbose and log output could make its way there. So when a non -rx > console (or one not started with -m) connects it esentially sends over a > 'logger mute silent' command which unmutes it. I added the silent > keyword so that the "Console is not muted anymore." message doesn't get > printed every time. > > It also requires the patch from bug #10888 since that first read command > that asterisk does occasionally will have 2-3 commands in it, and the > way it works now we throw away anything after the first '\0'.
Oh, I didn't realize that you already had a patch for it. Cool! The issue had come up in discussion on IRC a couple of times, so I just figured I would do a brain dump of my thoughts on the issue. But, it looks like you were way ahead of me. :) -- Russell Bryant Software Engineer Digium, Inc. _______________________________________________ --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
