Re: Weird signal issues using yocto's warrior busybox (aarch64) when memory is cached

2020-01-29 Thread Lauri Kasanen
Hi, Try running your uptime loop script under valgrind? - Lauri ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox

Weird signal issues using yocto's warrior busybox (aarch64) when memory is cached

2020-01-29 Thread Sergio Paracuellos
Hi all, I am using busybox included version in yocto's warrior which is version 1.30.1 for aarch64 architecture. I log in to the system and run the following script directly in the prompt: while [ 1 ]; do uptime && free && sleep 1; done When the machine has all of the memory free this script

Re: [PATCH] ash, hush: allow builtins to be tab-completed, closes 7532

2020-01-29 Thread Denys Vlasenko
Applied, thanks On Tue, Jan 21, 2020 at 5:02 PM Ron Yorston wrote: > > function old new delta > complete_cmd_dir_file768 861 +93 > get_builtin_name - 45 +45 >

Re: [PATCH] xargs: fix handling of quoted arguments, closes 11441

2020-01-29 Thread Denys Vlasenko
On Fri, Jan 24, 2020 at 2:17 PM Ron Yorston wrote: > > As reported in bug 11441 when presented with a large number of quoted > arguments xargs can return 'argument line too long': > >seq 1 2 | sed -e 's/^/"/' -e 's/$/"/' | busybox xargs echo > > This happens because the variant of

Re: [PATCH] vi: fixes to string search in colon commands, closes 10321

2020-01-29 Thread Denys Vlasenko
Applied, thanks! On Thu, Jan 23, 2020 at 4:31 PM Ron Yorston wrote: > > Handling of string searches in colon commands (e.g ':/pat1/,/pat2/cmd') > differ from standard vi: > > - As reported in bug 10321 such searches can't be repeated using the > 'n' command. This is because the last search

Re: [PATCH] ash: improve expandstr()

2020-01-29 Thread Denys Vlasenko
Applied, thanks! On Thu, Jan 23, 2020 at 12:26 PM Ron Yorston wrote: > > The dash maintainer recently posted a fix for issues with expanding > PS1. These had already been fixed differently in BusyBox ash. Borrow > a couple of improvements: > > - Use a single call to setjmp() to trap errors in

Re: [PATCH] syslogd: add config option to include milliseconds in timestamps

2020-01-29 Thread Denys Vlasenko
Applied, thanks! On Mon, Jan 27, 2020 at 3:36 PM Peter Korsgaard wrote: > > For some use cases, having logs with more than 1 second accuracy can be > helpful. Add an option to include milliseconds when adding a timestamp in > HH:MM:SS.mmm format, similar to syslog-ng with fraq_digits(3) or