> > 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. -- meem
