From owner-freebsd-hackers Sat Mar 20 11:34: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id C91CF14FF0 for ; Sat, 20 Mar 1999 11:33:51 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id PAA34185 for hackers@freebsd.org; Sat, 20 Mar 1999 15:43:43 GMT (envelope-from dm) Message-ID: <19990320154343.A34085@globalserve.net> Date: Sat, 20 Mar 1999 15:43:43 +0000 From: Dan Moschuk To: hackers@freebsd.org Subject: odd pthreads problem. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have encounted a small problem that I believe is with pthreads. I have a threaded program that operates under a fair amount of load. When it is started from crontab, the CPU usage jumps to 100%, when it is started from the command line it idles around 3-7%. However, when it is started from the commandline, I get a fairly regular screen dump of "junk" (similar to what you'd see if you cat'd a binary file to stdout). This occurs even when stdout/stderr is redirected to /dev/null. I have gone through my code a few times, and there are *no* instances where it prints to the screen. This has been tested with 2.2.7 and last weeks 4.0-current. Ideas? Regards, -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "If at first you don't succeed, redefine success" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message