Date: Wed, 14 Feb 2007 17:58:17 -0800 From: "pete wright" <nomadlogic@gmail.com> To: "Robert Huff" <roberthuff@rcn.com> Cc: questions@freebsd.org Subject: Re: origin of system message? Message-ID: <57d710000702141758n18d7d2b6tf710639b661234d@mail.gmail.com> In-Reply-To: <17875.40030.186110.223360@jerusalem.litteratus.org> References: <200702142204.l1EM4XZv001580@jerusalem.litteratus.org> <17875.35782.223268.107539@jerusalem.litteratus.org> <45D38DF5.60207@rz.tu-clausthal.de> <17875.37343.235431.762503@jerusalem.litteratus.org> <57d710000702141513l62a3e760lbe50ddfed9249831@mail.gmail.com> <17875.40030.186110.223360@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/14/07, Robert Huff <roberthuff@rcn.com> wrote: > pete wright writes: > > > > > > Feb 14 17:03:50 jerusalem kernel: Connection attempt to UDP 209.6.203.219:1026 from 202.97.238.130:52821 > > > > > > > > > > What program/process issues this, and at what facility and > > > > > level? > > > > I don't want to stop the messages, merely re-direct them. > > > > you can set that up in your syslog.conf(5) file. > > <pointed look> > And in order to do that ... what information do I need? > </pointed look> > :-) heh, sorry. the man page for syslog.conf is pretty helpfull for setting this stuff up. the command to read it is "man 5 syslog.conf" so that was short hand. it'll show you how to setup rules for various log messages and how to route them to different log files(or syslogd servers). i suspect you want a log file that'll just contain these UDP and TCP connection attempts... -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57d710000702141758n18d7d2b6tf710639b661234d>