| Summary: | ASTERISK-00077: stderr | ||
| Reporter: | kaku (kaku) | Labels: | |
| Date Opened: | 2003-08-10 03:32:53 | Date Closed: | 2011-06-07 14:04:57 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | if you try to connect multiple instances of asterisk console stderr is only connected to the first one and the others have stdin and stdout in common. I dont know if thats done intentional or not ,but this can give alot of trouble if you have some problem and is only watching the second existance of asterisk console. ****** ADDITIONAL INFORMATION ****** errors and warning only get written to the first existance of asterisk console . | ||
| Comments: | By: John Todd (jtodd) 2003-08-11 21:29:53 I believe this is intentional. A possible repair/feature addition to resolve this might be to create a command similiar to Cisco's "terminal monitor" and "terminal no monitor" which requests that all error/warning messages are logged or not logged to that terminal. In this fashion, it could be possible to activate the standard debugging from any particular CLI session to which one happens to be attached. By: Mark Spencer (markster) 2003-08-12 17:40:46 You can tail -f /var/log/asterisk/messages or similar. By: Mark Spencer (markster) 2003-08-12 17:41:09 If you want, you can resubmit as a feature request. | ||