>> chpst is a monster of a program and at least with runscripts written in >> execline it's generally easier to understand 3-4 process state >> manipulators than a pile of chpst options. > > this is more complicated to use, though.
it is even unnecessary, inefficient, and wasteful. why exec chaining into several different utils where doing all the requested process state changes in one go by using the same utility to achieve them would suffice ?
