Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month at the Massachusetts Institute of Technology, in Building E51.

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] docker Re: Corralling Processes on Linux



On 02/05/2018 04:02 PM, Mike Small wrote:
> At what point does it make sense to go to the cgroup level or even
> container level and at what point are traditional Unix abstractions like
> process groups and sessions adequate?  If Kent is creating all the
> processes himself and they all fall in one process group then kill(2) on
> the negative of the process group leader should kill them all.

Even if they are daemons? Also, the parent is (currently) a command line 
utility that goes away each time it is run.

My use case: I specifically want this command line utility to be 
minimalist for now, but add features in the future (interrogate the 
daemons about their state, do something interesting about the ones which 
report an error condition, maybe shove some into a disabled state) 
without constantly killing all of the daemons. I want the guts of this 
software to be able to get ahead of the executive orchestrating it. The 
result will be a far looser confederacy of processes than we are 
familiar with in monolithic programs.

-kb



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org