From owner-freebsd-hackers Sun Jul 12 22:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10798 for freebsd-hackers-outgoing; Sun, 12 Jul 1998 22:02:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from greeves.mfn.org (greeves.mfn.org [204.238.179.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10791 for ; Sun, 12 Jul 1998 22:02:45 -0700 (PDT) (envelope-from sysadmin@mfn.org) Received: from noc.mfn.org (noc.mfn.org [204.238.179.35]) by greeves.mfn.org (8.8.7/8.8.7) with SMTP id AAA14921 for ; Mon, 13 Jul 1998 00:03:09 -0500 (CDT) (envelope-from sysadmin@mfn.org) Received: by noc.mfn.org with Microsoft Mail id <01BDAE1B.73B84C90@noc.mfn.org>; Mon, 13 Jul 1998 05:02:36 +0100 Message-ID: <01BDAE1B.73B84C90@noc.mfn.org> From: NOC-GFX To: "'freebsd-hackers@freebsd.org'" Subject: rwhod / syslogd anomaly Date: Mon, 13 Jul 1998 05:02:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, First, let me apologize if this is the wrong forum, I wasn't sure: I've gone around and around with this on -questions but with no resolution... First off, the base problem started out as rwhod dying with no messages or log entries to LOG_DAEMON, for reasons I still haven't figured out. It dies after about three minutes of up time (the magic number according to the source), and doesn't peep a thing. And the *really* strange part is that if you try to bring up back up, it won't start, *nor* leave a message/log entry as to why not! I have not coded in c since 1985, so to say that my skills are rusty is an understatement: this has left me in the position of trying to track this thing down using really dirty hacks like fprintf's to mark where I am in the code. So far I have put a message out to std-err before every single exit() call in the source, and have not seen a single one show up. On top of that, I made sure that the facility for logging rwhod was up and set correctly by forcing errors while it was up for its initial (IPL) 3 minute run. Before it dies, it logs correctly, after it dies, it neither runs nor logs. So, here's where I'm at now: (1) A thorough search of the archives has turned up nothing for either rwhod/syslogd. (2) I need to establish (a) what can stop a program dead like this, and (b) what can prevent it from either logging or putting messages out to stderr, all without generating *any* messages itself. (I have gone over the other logs dozens of times with a fine tooth comb, even the "Daemon" log, which is just massive). Does anybody have any thoughts on this? J.A. Terranson sysadmin@mfn.org (PS: Please cc me directly, as I am not a -hackers recipient. Thanks!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message