Fix for CR #6793120 ... / was: Re: [ksh93-integration-discuss] ksh93update 2[PSARC/2009/063FastTrack timeout 02/09/2009]

2009-02-04 Thread Roland Mainz
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 pr

Fix for CR #6793120 ... / was: Re: [ksh93-integration-discuss] ksh93update 2[PSARC/2009/063FastTrack timeout 02/09/2009]

2009-02-04 Thread Garrett D'Amore
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