From owner-freebsd-questions Fri Apr 3 13:37:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06872 for freebsd-questions-outgoing; Fri, 3 Apr 1998 13:37:11 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06729 for ; Fri, 3 Apr 1998 13:36:23 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id NAA11058; Fri, 3 Apr 1998 13:36:16 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Fri, 3 Apr 1998 13:36:16 -0800 (PST) From: Doug White Reply-To: Doug White To: Studded cc: FreeBSD Questions Subject: Re: Odd syslog entrys In-Reply-To: <35253BB4.BC9BC943@san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Apr 1998, Studded wrote: > A customer wanted me to take a look at some odd syslog entries on his > machine. I am guessing that someone connected directly to syslogd and > entered the info directly. If this is the case, I would appreciate > confirmation and if anyone knows the method I'd like to demonstrate to > the customer what happened and show that the leak is plugged. They did > not have the -s option enabled on syslogd but I killed it and restarted > with that option. Here are the messages: I would agree with that appraisal. I would also contact the administrators ofj59.mlk31.jaring.my and t4o3lp25.telia.com (jaring.my and telia.com respectively, those are probably dialin lines) and complain about their user's bad language. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message