Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7561647
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T13:12:39+00:00 2026-05-30T13:12:39+00:00

I have a Bash script script which roughly looks like: #!/bin/bash cmd1 | cmd2

  • 0

I have a Bash script “script” which roughly looks like:

#!/bin/bash

cmd1 | cmd2 | cmd3

When I do a kill script (or more precisely when I do a ‘stop script’ in supervisord), not all cmd* are killed. How can I make sure they are terminated along with the script that spawned them?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T13:12:41+00:00Added an answer on May 30, 2026 at 1:12 pm

    Supervisord has stopasgroup and killasgroup options (false by default) which determine whether to propagate SIGTERM/SIGKILL signals to child processes.

    [program:script]
    command=script
    stopasgroup=true
    killasgroup=true
    

    (These config variables are both documented at http://supervisord.org/configuration.html.)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a simple test bash script which looks like that: #!/bin/bash cmd=rsync -rv
I have a bash script which calls another bash script, like so: #!/bin/bash echo
Currently I have a bash script which runs the find command, like so: find
I have a bash script file which starts with a function definition, like this:
I have a Bash shell script in which I would like to pause execution
I have a bash shell script which has the line: g=$(/bin/printf ${i}) when ${i}
I have a BASH script which runs other commands and I would like to
So, I have a bash script inside of which I'd like to have a
I have a Makefile from which I want to call another external bash script
I have some ksh scripts which I'd like to convert to run with bash

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.