From owner-freebsd-security@FreeBSD.ORG Thu Jun 12 05:50:47 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1363D37B401 for ; Thu, 12 Jun 2003 05:50:47 -0700 (PDT) Received: from minimail.digi.com (minimail.digi.com [204.221.110.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C61743FB1 for ; Thu, 12 Jun 2003 05:50:46 -0700 (PDT) (envelope-from Kelly_Flanagan@digi.com) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 12 Jun 2003 07:50:45 -0500 Message-ID: <71A17D6448EC0140B44BCEB8CD0DA36E197923@minimail.digi.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Serial Ports and syslogd Thread-Index: AcMw4bdZV3++K75hQNmEcqmdXc3JRg== From: "Kelly Flanagan" To: Subject: Serial Ports and syslogd X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2003 12:50:47 -0000 Hello,=20 It's a bit off topic, but I'm hoping someone has seen this before. I'm = running a couple of headless boxes, one is 4.7 release, the other is 4.8 = release. Both have the same issue with newsyslog when I've got the = serial port enabled for console management. (-h in boot.conf and a getty = running on cuaa0 after the boot process)=20 Logrotate tries to send an HUP to syslogd, but it's not working = properly. I get rotated logs, but they stay empty. If I "nuke" syslogd, = and try to restart it, it eventually dies with "waiting for child" = messages and my sendmail hangs. Syslogd comes back alive after reboot. = I'm just logging locally with -s -s for flags to syslogd.=20 So, I find a few discussions saying fsync() may be the reason, and try = swaping syslogd with this line removed in syslogd.c (without being very = good at C) and knowing full well, I'll loose the most important, last = few lines of logs when my machine dies. Still no help.=20 /*flags =3D ISKERNEL | SYNC_FILE | ADDDATE;*/=20 Anybody using serial without any logging problems? Or is there a better = way to kill syslogd and restart it?