ale5000

In cases where it hasn't been noticed, microG has been supporting license verification for some time now. You must update both microG Services and microG Companion and enable the corresponding...

Thanks but unfortunately it doesn't fix all cases. I first thought the problem was only with exec but instead the problem is also with `su`. This is the behavior of...

@rmyorston I noticed another issue, this: `sh -c 'sh'` should enter in an interactive subshell but instead it just remain not-interactive.

Thanks, now the interactive/non-interactive mode works fine in all cases. Now I tried to check exec. I usually use exec to avoid keeping the previous process open, but it seems...

> Windows doesn't have an `exec()` system call so the implementation of the `exec` shell builtin can't work as it does on Unix. The shell tries to reuse processes where...

If the `su` process (process 2) isn't called with `-W` then the caller (process 1) won't wait for the `su` process (process 2) to exit, so when the `su` process...

If I'm not wrong we already know it, when `$PPID` is 1 the process can close itself without problems (I think). This would also apply to other cases where the...

> What other cases did you have in mind? I haven't thought too much about other cases but I can think of one example. For example if a script (near...

I tried in various ways in a new window created with `su` but also with a separate window created using `cmd.exe /c start busybox ash` and it seems to work...

I also tried this: ``` my_func() { sleep 8; exec sh -c 'echo "test" > my_file.txt; sleep 25'; } my_func & kill $$ ``` An it seems to behave properly...