[coyotos-dev] Binary naming

[David-Sarah Hopwood]

Jonathan S. Shapiro wrote:
> On Fri, 2008-04-11 at 10:51 -0400, Christopher Nelson wrote:
>> On Thu, 2008-04-10 at 15:45 -0400, Jonathan S. Shapiro wrote:
>>> It isn't clear that any equivalent to the process status command should
>>> even *exist* in Coyotos. One user has no intrinsic right to examine the
>>> processes of another, or even to examine the process substructure of
>>> their own applications!
>> What about management applications?  Presumably there will need to be a
>> way to view all processes executing in order to drop runaway processes,
>> or perhaps to do some accounting.
> 
> Why? If the goal is to do resource management and accounting, then what
> you want to look at is the resource consumption pools. It is none of
> your business how many, or how few, processes a given application
> internally constructs out of its storage.
> 
> They aren't your processes.

Besides, if you needed to be able to enumerate "runaway" processes in order
to kill them, they might be created faster than you can do so. Revoking a
resource pool solves that problem.

For the purpose of allowing a user to kill applications that they started,
the user's shell can keep track of the resource pools that it assigns
to each application. It's not necessary to be able to enumerate subprocesses
started by an application's initial process.

-- 
David-Sarah Hopwood