| Summary: | ASTERISK-18304: Problem with batch-creation of astdb entries | ||
| Reporter: | Tzafrir Cohen (tzafrir) | Labels: | |
| Date Opened: | 2011-08-21 09:03:54 | Date Closed: | 2011-09-12 14:33:04 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | 1.8.5.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | (I'm not completely sure that the following is a legitimate bug, but anyway) Following the Freepbxdb.pm modules I added to dahdi-perl ( http://svnview.digium.com/svn/dahdi?view=revision&revision=10142 ), and some potential astdb corruption cases I encountered to make a simpler test case of a direct write of commands to the asterisk.ctl . The attached astcmd is a script that uses the same code and accepts any commands from the standard input. $ (echo database deltree tzafrir; for i in `seq 50`; do echo database put tzafrir test$i 123; done) | astcmd $ asterisk -rx 'database show tzafrir' | grep ^/ | wc -l 47 Whereas: $ asterisk -rnx 'database deltree tzafrir'>/dev/null; for i in `seq 50`; do asterisk -rnx "database put tzafrir test$i 1234" >/dev/null; done $ asterisk -rx 'database show tzafrir' | grep ^/ | wc -l 50 That is, using astcmd, 3 are missing. It is always the same 3: entries no. 16, 32 and 48 . | ||
| Comments: | |||