All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ratheesh k <ratheesh.ksz@gmail.com>
Cc: Netfilter mailing list <netfilter@vger.kernel.org>,
	laforge@gnumonks.org, Eric Leblond <eleblond@edenwall.com>,
	chifflier@edenwall.com
Subject: Re: ULOGD and other logs
Date: Mon, 13 Sep 2010 15:33:45 +0200	[thread overview]
Message-ID: <4C8E2839.3060604@netfilter.org> (raw)
In-Reply-To: <AANLkTi=tPs=39vmRzc=41z=Vt8kHmK7vygKrfn5=0rh=@mail.gmail.com>

On 13/09/10 15:12, ratheesh k wrote:
> Hi ,
>
>   I am using ulogd to   store iptables logs to /tmp/logfile.txt.  There
> is an application ( say X ) running on userspace ( using nfqueue  in
> FORWARD chain in filter table ) to do some kind of blocking  packets
> based on time ( some  thing like a minimal parental control feature ).
> I would also want to generate some logs and put into the same
> /tmp/logfile.txt file.  Since  ulogd and  X are using same file , we
> need some file locking mechanism. Is there any other way to forward
> these message to netlink socket and ulogd can itself handle, so that i
> dont have to do any kind of synchronization.
>
> May be i can put the question in this way: Kernel is sending some
> message and ulogd listens and receives the message on netlink socket.
> Could any other application in userspace  , send some  message  to
> this socket and ulogd can read and write to the log file f ?

There's the UNIX plugin for ulogd2 (not yet in mainline) that Eric 
Leblond and Pierre Chifflier contributed time ago. However, some minor 
issues prevented to push into mainline, any word on it, Eric, Pierre?

      reply	other threads:[~2010-09-13 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 13:12 ULOGD and other logs ratheesh k
2010-09-13 13:33 ` Pablo Neira Ayuso [this message]

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=4C8E2839.3060604@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=chifflier@edenwall.com \
    --cc=eleblond@edenwall.com \
    --cc=laforge@gnumonks.org \
    --cc=netfilter@vger.kernel.org \
    --cc=ratheesh.ksz@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.