From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: Rodrigo Real <rreal@ucpel.tche.br>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Cobol app takes 100% CPU
Date: Thu, 27 Mar 2008 11:53:10 -0600 [thread overview]
Message-ID: <47EBDF06.9040503@sbcglobal.net> (raw)
In-Reply-To: <87ej9wpdsa.fsf@pequena.ucpel.tche.br>
Rodrigo Real wrote:
> I once took a look at Tame, but didn't tried it, since it was a paid
> software and I didn't know anything about it, I just didn't pay
> attention. But it is good to know that it works.
I didn't reply, because I wasn't sure I understood your
issue. Have you tried simply running dosemu with nice?
I wouldn't care if dosemu ate all the CPU, so long as
other processes weren't slowed down when they wanted to
run.
For example, I run the GIMPS on my machine. It's always
100% CPU utilization as a consequence. But if the response
is slow, it's not because of GIMPS.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
next prev parent reply other threads:[~2008-03-27 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 12:55 Cobol app takes 100% CPU Rodrigo Real
2008-03-26 15:28 ` Frank Cox
2008-03-27 12:11 ` Rodrigo Real
2008-03-27 14:20 ` Frank Cox
2008-03-27 15:57 ` Bart Oldeman
2008-03-27 17:53 ` Rodrigo Real
2008-03-27 17:53 ` Mike McCarty [this message]
2008-03-27 18:11 ` Rodrigo Real
2008-03-30 20:37 ` Jan Kandziora
2008-03-31 1:18 ` Rodrigo Real
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 14:12 Manfred Scherer
2008-03-31 13:46 ` Rodrigo Real
2008-03-31 9:47 ` Manfred Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47EBDF06.9040503@sbcglobal.net \
--to=mike.mccarty@sbcglobal.net \
--cc=linux-msdos@vger.kernel.org \
--cc=rreal@ucpel.tche.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.