From: Valters Jansons <valter.jansons@gmail.com>
To: location@lists.ipfire.org
Subject: Re: [0.9.12] export --format xt_geoip: (25, 'Inappropriate ioctl for device')
Date: Tue, 29 Mar 2022 17:16:41 +0300 [thread overview]
Message-ID: <CA+sCei0oNVNmD58DvMKmhaYcqZXU+-SHq2emYQ9uoDMTkd2XwA@mail.gmail.com> (raw)
In-Reply-To: <F89458DE-0F1F-4ED2-829A-CA5B2B50B837@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Tue, Mar 29, 2022 at 5:10 PM Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> Hmm, this should not happen like this.
>
> I am not even sure why this is trying to do any ioctls for terminals on the output file.
>
> Is this reproducible with any of the other formats, too, or is it only xt_geoip?
Indeed, I could not find what seems to cause this, and have not been
able to work around it.
I did not yet try other exporters - I have been focusing on xt_geoip
as we use it for a system's firewall rules.
But considering the IPv6 files for xt_geoip are being written
correctly, it feels to me like others exporters might work. Will
check.
Wanted to bring this to your attention before spending more time on
it, as you maybe were aware.
-Valters
next prev parent reply other threads:[~2022-03-29 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+sCei11=+qTjjeWT+D0_8VRJZQhg+mwZn_BGcMmfSxHriKViw@mail.gmail.com>
2022-03-29 14:10 ` Michael Tremer
2022-03-29 14:16 ` Valters Jansons [this message]
2022-03-29 14:25 ` Valters Jansons
[not found] <CA+sCei3rpFGm=5QYxP-tsG4bjZL6+NQHG07XG540QGVkng5U4w@mail.gmail.com>
2022-03-29 15:03 ` Michael Tremer
2022-03-30 15:36 ` Michael Tremer
2022-03-30 15:59 ` Valters Jansons
2022-03-30 16:04 ` Michael Tremer
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=CA+sCei0oNVNmD58DvMKmhaYcqZXU+-SHq2emYQ9uoDMTkd2XwA@mail.gmail.com \
--to=valter.jansons@gmail.com \
--cc=location@lists.ipfire.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