helpThe GNU Bourne-Again SHell - Support: sr #110358, bash: please provide an easy way...

 
 

sr #110358: bash: please provide an easy way to spawn a new process group from script

Submitted by:  None
Submitted on:  Sun 01 Nov 2020 07:24:06 PM UTC
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Wont Do
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Sun 01 Nov 2020 07:24:06 PM UTC, comment #3: 

This item has been reassigned from the project Savannah Administration support tracker to your tracker.

The original report is still available at support #110356

Following are the information included in the original report:

[field #0]                  Item ID: 110356

[field #1]                 Group ID: 5802

[field #2]              Open/Closed: Open

[field #3]                 Severity: 3 - Normal

[field #4]                  Privacy: Public

[field #7]                         : Unknown support Field Display Type

[field #8]                         : Unknown support Field Display Type

[field #9]                 Category: None

[field #10]             Submitted by: None

[field #11]              Assigned to: None

[field #12]             Submitted on: Sat 31 Oct 2020 06:51:58 PM MDT

[field #13]                  Summary: bash: please provide an easy way to spawn a new process group from script

[field #14]      Original Submission: I was battling this problem now for several hours

i wanted to do this:

{ a | b; } & pid=$!

and then later

kill -- -$pid

to kill all the processes spawned by the pipeline.

But this proved to be immensely complicated as no new process group is spawned from within a script (unless set -m which is not recommended)

Please, provide a syntactic construct to spawn a new process group (or at least there should be some usable command to do that).

[field #16]               Item Group: None

[field #17]                   Status: None

[field #18]        Component Version: None

[field #19]         Operating System: None

[field #20]          Reproducibility: None

[field #21]               Size (loc): None

[field #22]            Fixed Release: None

[field #23]          Planned Release: None

[field #24]                   Effort: 0.00

[field #28]                 Priority: 5 - Normal

[field #31]         Percent Complete: 0%

[field #33]                  Release: None

[field #36]         Originator Email: clime7@gmail.com

[field #58]     Custom Select Box #1: None

[field #59]     Custom Select Box #2: None

[field #60]     Custom Select Box #3: None

[field #61]     Custom Select Box #4: None

[field #62]     Custom Select Box #5: None

[field #63]     Custom Select Box #6: None

[field #64]     Custom Select Box #7: None

[field #65]     Custom Select Box #8: None

[field #66]     Custom Select Box #9: None

[field #67]    Custom Select Box #10: None

Bob Proulx <rwp>
Project Member
Sun 01 Nov 2020 07:22:56 PM UTC, comment #2: 

I should also note that for bash the primary bug and discussion venue is with email to the bug-bash AT gnu.org mailing list.  That is the better place to discuss bugs.

Also since you are asking for help the better venue is the help-bash AT gnu.org mailing list.  That's the best place to ask questions such as this.

Bob Proulx <rwp>
Project Member
Sun 01 Nov 2020 07:20:12 PM UTC, comment #1: 

You have reported a bash issue against the Savannah Administration project.  We don't have anything to do with individual projects hosted at Savannah.  I will transfer your ticket to the bash project.

However separate from that I suggest you look at the setsid(1) command which runs programs in a new session as that appears to be what you are wanting to do.

Bob Proulx <rwp>
Project Member
Sun 01 Nov 2020 07:24:06 PM UTC, original submission:  

I was battling this problem now for several hours

i wanted to do this:

{ a | b; } & pid=$!

and then later

kill -- -$pid

to kill all the processes spawned by the pipeline.

But this proved to be immensely complicated as no new process group is spawned from within a script (unless set -m which is not recommended)

Please, provide a syntactic construct to spawn a new process group (or at least there should be some usable command to do that).

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by chet (Updated the item)
  • -email is unavailable- added by rwp (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-11-09 chet StatusNone => Wont Do
    2020-11-01 rwp Reassign itemSavannah Administration, sr #110356 => The GNU Bourne-Again SHell, sr #110358

    Back to the top


    Powered by Savane 3.9