From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject:
 Re: [0.9.12] export --format xt_geoip: (25, 'Inappropriate ioctl for device')
Date: Tue, 29 Mar 2022 15:10:54 +0100
Message-ID: <F89458DE-0F1F-4ED2-829A-CA5B2B50B837@ipfire.org>
In-Reply-To:
 <CA+sCei11=+qTjjeWT+D0_8VRJZQhg+mwZn_BGcMmfSxHriKViw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0862194974454699048=="
List-Id: <location.lists.ipfire.org>

--===============0862194974454699048==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Valters,

Hmm, this should not happen like this.

I am not even sure why this is trying to do any ioctls for terminals on the o=
utput file.

Is this reproducible with any of the other formats, too, or is it only xt_geo=
ip?

-Michael

> On 29 Mar 2022, at 15:07, Valters Jansons <valter.jansons(a)gmail.com> wrot=
e:
>=20
> On v0.9.12, I am observing an issue with XTGeoIP exports: the *.iv4 files d=
o not get written.
>=20
> The sample command I use to reproduce this on Ubuntu 20.04 is very basic:
> location export --format xt_geoip --directory /usr/share/xt_geoip
>=20
> All IPv6 outputs are written successfully, but upon reaching IPv4 it errors=
 with:
> (25, 'Inappropriate ioctl for device')
>=20
> A quicker test case is to add argument `--family ipv4` so that IPv6 is hopp=
ed over and it tries IPv4 right away.
>=20
> With strace, it seems to be:
> openat(AT_FDCWD, "/usr/share/xt_geoip/A1.iv4", O_WRONLY|O_CREAT|O_TRUNC|O_C=
LOEXEC, 0666) =3D 4
> fstat(4, {st_mode=3DS_IFREG|0600, st_size=3D0, ...}) =3D 0
> ioctl(4, TCGETS, 0x7ffd234c3260)        =3D -1 ENOTTY (Inappropriate ioctl =
for device)
>=20
> Please let me know if I can provide any further information.
>=20
> Best regards,
> Valters Jansons


--===============0862194974454699048==--