Bug#985478: [PATCH] options: Always reset OPTIND in getoptsreset

2024-05-19 Thread Harald van Dijk
On 19/05/2024 12:19, Herbert Xu wrote: On Wed, Jan 04, 2023 at 04:50:34PM +, Harald van Dijk wrote: Personally, I do think it is better if shells allow assigning arbitrary values to OPTIND, including unsetting it, and only have the getopts command raise an error if the value is non-numeric

Bug#974705: Changes to job handling cause hangs in wait

2020-12-01 Thread Harald van Dijk
On 01/12/2020 10:56, Herbert Xu wrote: On Tue, Dec 01, 2020 at 10:55:06AM +, Harald van Dijk wrote: You wrote: "So the problem is really in the parent of this shell, which appears to be bash:" You should read my follow-up email too that suggested changing the systemd script.

Bug#974705: Changes to job handling cause hangs in wait

2020-12-01 Thread Harald van Dijk
On 01/12/2020 10:53, Herbert Xu wrote: On Tue, Dec 01, 2020 at 10:50:19AM +, Harald van Dijk wrote: This used to exit immediately, leaving the sleep process running in the background without waiting for it. On the dash that's currently provided by Ubuntu, based on 0.5.10.2, it

Bug#974705: Changes to job handling cause hangs in wait

2020-12-01 Thread Harald van Dijk
On 01/12/2020 10:34, Herbert Xu wrote: On Tue, Dec 01, 2020 at 10:14:04AM +, Harald van Dijk wrote: POSIX says: "If the wait utility is invoked with no operands, it shall wait until all process IDs known to the invoking shell have terminated and exit with a zero exit status

Bug#974705: Changes to job handling cause hangs in wait

2020-12-01 Thread Harald van Dijk
ted-stdout); For some reason this is causing the final two tee's to be created as children of debian/tests/timedated rather than the bash shell. This is because of the same optimisation that dash also has, where it tries to avoid creating a subshell for the last command in a list when it can just exec() without a fork() instead. A minimal example without an explicit exec is bash -c 'dash -c ": & wait" <(sleep 1d)' Cheers, Harald van Dijk

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-31 Thread Harald van Dijk
Hi Vitaly, On 31/03/2020 20:07, Vitaly Zuevsky wrote: I must have confused two concepts: waited process in OS -vs- waited job inside shell interpreter. I am trying to see how it work in practice: # true & false & # [2] + Done(1)false [1] + Done true #

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-29 Thread Harald van Dijk
On 29/03/2020 23:07, Jilles Tjoelker wrote: On Sun, Mar 29, 2020 at 08:06:31PM +0100, Harald van Dijk wrote: On 29/03/2020 18:54, Vitaly Zuevsky wrote: I have now fixed this bug locally. The leak is in jobtab array (jobs.c). I concluded that the most logical approach would be eliminating

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-29 Thread Harald van Dijk
hile true do (true &) sleep .1 done Cheers, Harald van Dijk

Bug#646847: dash.1 - Confusion between two pages c[h]sh

2014-11-10 Thread Harald van Dijk
s csh but also adds chsh be more appropriate, or do you prefer to leave it as it is now? Cheers, Harald van Dijk Cheers, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org