> My idea was to provide a simple, "preconfigured" tool to do this.
Without writing any new code, it seems that we already have a tool for
doing this. The manpage for priocntl(1) is pretty explicit:
In addition to the system-wide limits on user priority
(displayed with priocnt
Hi Roland,
Roland Mainz wrote:
My idea was to provide a simple, "preconfigured" tool to do this. Right
now we have more or less the following levels of "interactivity" in the
scheduler classes:
1. "RT" (realtime)
2. "IA" (interactive processes (more or less a subclass of "TS" where an
active GUI
I would suggest that, in order to make it a more useful product, you plan on
making it portable from the very beginning. I myself have had many
headaches trying to make it work because it was developed with only Solaris
in mind and the other operating systems were just an afterthought.
Also, I
I would suggest that, in order to make it a more useful product, you
plan on making it portable from the very beginning. I myself have had
many headaches trying to make it work because it was developed with only
Solaris in mind and the other operating systems were just an
afterthought.
Also, I
I would suggest that, in order to make it a more useful product, you
plan on making it portable from the very beginning. I myself have had
many headaches trying to make it work because it was developed with only
Solaris in mind and the other operating systems were just an
afterthought.
Also, I kn
