Greg,
Thank you, found the issue in "root" .profile, you were correct a '1' had been
added to Prompt Command variable.
Respectfully,
William Krongard
Express Scripts Services,
Server Support
Work: (952)-837-7537
Cell: (763) 442-0640
Server Support Confluence page:
Server Support landing pag
On 6/28/20 9:49 AM, felix wrote:
> Bash Versions: 3.2.57(1)-release, 5.0.3(1)-release, 5.1.0(1)-alpha
>
> In order to reduce forks and make some tasks a lot quicker, I run
> forked filters as background tasks, with dedicated I/O fd.
>
> For sample, to convert human datetime to UNIX SECONDS, inst
On 6/29/20 4:33 PM, Dmitry Alexandrov wrote:
> Dear maintainer,
>
> I believe, that the current behaviour of GNU Bash:
>
> $ command cat &
> [1] 3831
> $ ps --pid $! --ppid $!
> PID TTY TIME CMD
>3831 pts/300:00:00 bash
>3832 pts/300:00:0
Hi,
I'm trying to understand what approach bash takes to async-signal safety in
its design.
Generally, programs that use signals (such as SIGCHLD or SIGALRM) must make
sure that
(a) they do not access state (such as variables) from within the signal
handler if such state could also be accessed f
Chet Ramey wrote:
> On 6/29/20 4:33 PM, Dmitry Alexandrov wrote:
>> 1) unexpected, as (a) it does not seem to be documented, (b) itʼs
>> counter-intuitive and (c) other bourne-like shells (busybox ash, dash,
>> ksh93, mksh, zsh) does not do that;
>
> It's an opportunity for optimization, not a b
On 6/30/20 4:37 PM, Dmitry Alexandrov wrote:
> Chet Ramey wrote:
>> On 6/29/20 4:33 PM, Dmitry Alexandrov wrote:
>>> 1) unexpected, as (a) it does not seem to be documented, (b) itʼs
>>> counter-intuitive and (c) other bourne-like shells (busybox ash, dash,
>>> ksh93, mksh, zsh) does not do that
Eli Schwartz wrote:
> Useful replacements:
Thank you. Yes, I have to pick up habit to post known user-level workarounds
along with bugreports.
> If you need to ensure a disk executable is used,
Of course. Why ‘command’ otherwise?
> $ "$(type -P cat)" &
> [1] 2092352
> $ ps --pid $! --ppid $
