Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1242138 > unrolled thread

Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone Simon Richter <sjr@debian.org> - 2025-04-15 13:30 +0200
    Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone Luca Boccassi <luca.boccassi@gmail.com> - 2025-04-15 16:40 +0200
      Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone Simon Richter <sjr@debian.org> - 2025-04-16 01:10 +0200
        Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone Luca Boccassi <bluca@debian.org> - 2025-04-16 12:40 +0200

#1242138 — Bug#1103242: /bin/ip: "ip mon" does not exit when output is gone

Package: iproute2
Version: 6.1.0-3
Severity: minor
File: /bin/ip
Tags: upstream
X-Debbugs-Cc: sjr@debian.org

Hi,

I started "ip mon" in the background, and closed the shell and the terminal.

The "ip" command is still running, receiving netlink messages and writing to
stdout, receiving EIO for this attempt.

Monitor mode should probably exit when it cannot write output.

   Simon

-- System Information:
Debian Release: 12.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 6.1.0-31-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libbpf1                1:1.1.0-1
ii  libbsd0                0.11.7-2
ii  libc6                  2.36-9+deb12u9
ii  libcap2                1:2.66-4
ii  libcap2-bin            1:2.66-4
ii  libdb5.3               5.3.28+dfsg2-1
ii  libelf1                0.188-2.1
ii  libmnl0                1.0.4-3
ii  libselinux1            3.4-1+b6
ii  libtirpc3              1.3.3+ds-1
ii  libxtables12           1.8.9-2

Versions of packages iproute2 recommends:
ii  libatm1  1:2.5.1-4+b2

Versions of packages iproute2 suggests:
pn  iproute2-doc  <none>
ii  python3       3.11.2-1+b1

-- debconf information excluded

[toc] | [next] | [standalone]

#1242161

Control: tags -1 moreinfo

On Tue, 15 Apr 2025 at 12:21, Simon Richter <sjr@debian.org> wrote:
>
> Package: iproute2
> Version: 6.1.0-3
> Severity: minor
> File: /bin/ip
> Tags: upstream
> X-Debbugs-Cc: sjr@debian.org
>
> Hi,
>
> I started "ip mon" in the background, and closed the shell and the terminal.
>
> The "ip" command is still running, receiving netlink messages and writing to
> stdout, receiving EIO for this attempt.
>
> Monitor mode should probably exit when it cannot write output.

Hi,

Isn't this normal behaviour? IE, if I do 'sleep infinity &' and close
the terminal, it will likewise hang around

[toc] | [prev] | [next] | [standalone]

#1242212

Hi,

On 15.04.25 23:35, Luca Boccassi wrote:

>> I started "ip mon" in the background, and closed the shell and the terminal.

>> Monitor mode should probably exit when it cannot write output.

> Isn't this normal behaviour? IE, if I do 'sleep infinity &' and close
> the terminal, it will likewise hang around

Yes, but "sleep" will eventually exit, and doesn't produce output, so it 
doesn't have an opportunity to notice that stdout has been revoked.

And since the only function in monitor mode is to produce this output, 
it can just exit here.

    Simon

[toc] | [prev] | [next] | [standalone]

#1242259

On Wed, 16 Apr 2025 at 00:06, Simon Richter <sjr@debian.org> wrote:
>
> Hi,
>
> On 15.04.25 23:35, Luca Boccassi wrote:
>
> >> I started "ip mon" in the background, and closed the shell and the terminal.
>
> >> The "ip" command is still running, receiving netlink messages and writing to
stdout, receiving EIO for this attempt.
>
> >> Monitor mode should probably exit when it cannot write output.
>
> > Isn't this normal behaviour? IE, if I do 'sleep infinity &' and close
> > the terminal, it will likewise hang around
>
> Yes, but "sleep" will eventually exit, and doesn't produce output, so it
> doesn't have an opportunity to notice that stdout has been revoked.
>
> And since the only function in monitor mode is to produce this output,
> it can just exit here.

I see - then this is more like a feature request than a
packaging/downstream regression/issue.

Stephen, David, what do you think about the above request?

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web