Roland Mainz wrote:
> Peter Memishian wrote:
>
>> > > So there is a unique pid for each program and thus it can still be
>> pkill'd?
>> >
>> > If you start the command as seperate child job (e.g. $ sleep 12345 & #)
>> > it will always have a seperate pid. But that was not the problem which
>> > caused CR #6793120 - the process name changed from "sleep 12345" to
>> > something like "ksh93 sleep 12345" which caused the PIT test scripts to
>> > fail because they matched exactly for the process name "sleep 12345".
>> > The upcoming patch makes sure the processes get their expected name.
>>
>> Please tell me that this does not involve horrible hacks involving faking
>> up or munging process names in the kernel.
>>
>
> <joke>Nah... we just use a buffer overrun in the doors subsystem to hack
> into nscd, from there we crawl into the kernel and patch the process
> table ...</joke>
>
> Seriously... we change the alias.sh wrapper into a binary and therefore
> get the expected process name (this is a temporary solution until we
> switch (as originally designed) to compiled shell scripts (which should
> have the same effect)).
>
Why not just do the compiled shell scripts thing *now*? Why the
intermediate step?
-- Garrett
> ----
>
> Bye,
> Roland
>
>
