Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15783
| From | Daniel Colascione <dancol@dancol.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Request For Enhancement - TID variable |
| Date | 2019-12-26 08:48 -0800 |
| Message-ID | <mailman.1461.1577378926.1979.bug-bash@gnu.org> (permalink) |
| References | <20191226153751.587634704BBB@snark.thyrsus.com> <ff2cd1e9-b697-415b-97bd-206e44712345@dancol.org> |
On 12/26/19 7:37 AM, Eric S. Raymond wrote: > In attempting to use GNU parallel, with some bash scripts, I > discovered I had a problem with tempfile collisions due to > all of the thread having the same PID. > > I was able to come up with a workaround, but... > > RFE: bash should have a TID varuable that returns the vakue of gettid(2). > > If the bash devs are too busy for this like the idea, I could write > the patch. Are you sure that'd help? Parallel runs bash in a bunch of subprocesses, so looking at PID would suffice to distinguish jobs. Are you sure you weren't seeing an invariant PID because you were letting the PID variable expansion happen too early?
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Request For Enhancement - TID variable Daniel Colascione <dancol@dancol.org> - 2019-12-26 08:48 -0800
csiph-web