From: Shaun Grogan <flakvest@charter.net>
To: Linux Admin <linux-admin@vger.kernel.org>
Subject: Re: syslog-ng
Date: 29 May 2003 11:21:32 -0400 [thread overview]
Message-ID: <1054221692.10311.4.camel@dash1bravo> (raw)
In-Reply-To: <20030529135852.20073.qmail@inbox.net>
Sorry for being such a noob but here are the 2 lines I included in
syslog-ng.conf and never got it to work. What am I missing?
destination soho6 { file("/var/log/remote/soho6.log"); };
destination IP: { file("/var/log/remote/soho6.log"); };
On Thu, 2003-05-29 at 09:58, Luis Lain wrote:
> Hi Shaun,
>
> you have to include it in /etc/syslog.conf
> something like:
>
> routerservice /var/log/router.log
>
>
>
> Shaun Grogan <flakvest@charter.net> wrote:
>
>
> > I'm running syslog-ng and want to trap specifc info coming from a remote
> > machine into it's own file instead of into /var/log/messsages. asically
> > the info is coming from my router, a Watchguard Soho6 and is going to
> > messages right now, I just want syslog-ng to put that info into it's own
> > file. Below is a sample of the info coming in.
> >
> > May 27 14:09:26 soho6 IP: ICMP type (3) code (3) received from
> > 204.152.184.196 @2003-05-27-14:12:12
> >
> > Thanks,
> > Shaun W. Grogan
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-05-29 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 13:58 syslog-ng Luis Lain
2003-05-29 15:21 ` Shaun Grogan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 14:56 syslog-ng Shaun Grogan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1054221692.10311.4.camel@dash1bravo \
--to=flakvest@charter.net \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).