Re: Process launch problem with DFLY

    It's more likely to be the fact that the process's interactivity
    heuristic is classifying the process as a batch process rather then an
    interactive process.  There is also a known priority roll over bug which
    I just fixed a day or two ago but if you are not using 'renice' you
    wouldn't be effected by it.

    'ps y' provides useful information in this regard.  'PRI' is the
    dynamic process priority, where *lower* numbers mean higher 
    priority (faster) and higher numbers mean lower priority (slower).

    The interactivity measure is IAC.  Negative numbers tend to mean that
    the process is interactive while positive numbers tend to mean that the
    process is batch.  Numbers hovering around 0 mean that the system is
    not really sure *what* the process is.  Note that even in large builds
    many of the longer lived 'make' processes will appear to be interactive
    because they run only sporatically.

    The numbers only apply to normal processes, not pure kernel threads.

					-Matt
					Matthew Dillon 
					<[e-mail]>