| Summary: | ASTERISK-12787: [patch] asterisk -rx writes history | ||
| Reporter: | Tzafrir Cohen (tzafrir) | Labels: | |
| Date Opened: | 2008-09-27 08:14:56 | Date Closed: | 2008-11-05 17:28:59.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) 0001-no-need-for-history-on-asterisk-rx.patch | |
| Description: | asterisk -rx tries to write history. In fact, in two different places. I believe that most users would not want the those commands recorded. Furthermore, the way it is used today, often leads to an empty (just headers file) /root/.asterisk_history being generated. | ||
| Comments: | By: Jeff Peeler (jpeeler) 2008-09-27 18:58:25 I would think most users would want all commands logged. By: Tzafrir Cohen (tzafrir) 2008-09-27 23:48:52 If I have a script that runs: for i in `seq 1000`; do asterisk -rx 'originate something' done I wouldn't want it to flood my history. And anyway, we currently don't save it. We only initialize the history file. By: Jeff Peeler (jpeeler) 2008-09-28 13:39:46 I think the history should be logged, didn't check to see if it is currently or not. Perhaps a command line option as to whether or not to log would be a good idea. By: Tilghman Lesher (tilghman) 2008-11-05 17:28:59.000-0600 Committed revision 154922. | ||