From: Aaron Eppert <eppertan@cs.rose-hulman.edu>
To: netfilter-devel@lists.netfilter.org
Subject: libiptc and setsockopt
Date: Thu, 12 Dec 2002 16:23:34 -0500 [thread overview]
Message-ID: <20021212212334.GA2841@cs.rose-hulman.edu> (raw)
libiptc's iptc_commit(...) commit function appears to be
erroring out on rather valid data in the portion that
does a setsockopt() on SO_SET_REPLACE. The errno that is
set appears to be EAGAIN. Can anyone shed a bit of light
on the situation as to why this may happen. My application
is (unfortunately) using pthreads and all calls to libiptc
functions are wrapped with a mutex to prevent anyone from
calling into the library twice as I noticed it is hardly
thread safe.
Thank you for your time,
Aaron Eppert
reply other threads:[~2002-12-12 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021212212334.GA2841@cs.rose-hulman.edu \
--to=eppertan@cs.rose-hulman.edu \
--cc=netfilter-devel@lists.netfilter.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 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.