On Thu, Dec 11, 2008 at 02:35:43PM -0800, Noah wrote:
> Hi there,
> sometimes I find there one or two processes with the command name of 
> 'dialog' tacking the cpu on my freebsd machines.  any clues what creates 
> this situation and how I can circumvent the problem?  It appears to 
> happen around the time I run portmanager to update all the system ports.

dialog is interactive.  Sometimes it's possible to start dialog (or
other interactive process) and disconnect the terminal input.  Then
(depending on how errors are handled), it tries repeatedly to read

(that's addressed in the version of dialog which I maintain, but FreeBSD
has, iirc, a variant from long ago which isn't strictly compatible).


Thomas E. Dickey

Attachment: pgpiwAXoYEr69.pgp
Description: PGP signature

Reply via email to