Bug 691102 - ss: Extra options aren't taken into account when sizing output for the terminal
Summary: ss: Extra options aren't taken into account when sizing output for the terminal
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: iproute
Version: 24
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Phil Sutter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-26 18:29 UTC by Scott Schmit
Modified: 2017-08-08 11:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 11:39:37 UTC
Type: ---


Attachments (Terms of Use)

Description Scott Schmit 2011-03-26 18:29:54 UTC
Description of problem:
ss will place its columns to account for the terminal width to ensure that the local and remote end of the socket are as aligned as possible. However, this placement ignores whether or not additional information is requested, making that information difficult to read. For what it's worth, I'd argue that even when ss is run with no extra arguments, the output should not be wider than needed to fit all the data on the line (the excess whitespace between columns make it harder to visually line up the rows).

Version-Release number of selected component (if applicable):
iproute-2.6.35-6.fc14.x86_64

How reproducible:
100%

Steps to Reproduce:
1. ss -e on a default-sized terminal
2. run ss -e again on a wider terminal
  
Actual results:
The information from -e will always wrap, no matter how wide the terminal is, and huge amounts of space will be used between the local/remote columns.

Expected results:
The placement of columns is more intelligent, taking into account that -e also has information that needs to fit on the line

Additional info:
This also takes place for -p, -i, etc

Comment 1 Scott Schmit 2011-12-07 04:45:53 UTC
This is still present in Fedora 16, iproute-2.6.39-4.fc16.x86_64
(You probably realize this; just staying ahead of the EOL pruner.)

Comment 2 Fedora End Of Life 2013-01-17 00:12:33 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Scott Schmit 2013-01-17 06:01:10 UTC
Still present in iproute-3.3.0-5.fc17.x86_64

Comment 4 Fedora End Of Life 2013-07-04 06:28:04 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora Admin XMLRPC Client 2014-08-20 08:54:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Jan Kurik 2015-07-15 15:16:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 7 Pavel Šimerda (pavlix) 2015-08-27 11:31:08 UTC
I think this issue is still present upstream.

Comment 10 Pavel Šimerda (pavlix) 2015-08-28 09:23:54 UTC
Phil confirmed that this is an upstream issue as well.

Comment 12 Fedora Admin XMLRPC Client 2015-09-24 08:03:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Phil Sutter 2015-09-24 12:14:38 UTC
This is merely a bug but a feature (at least there's code which deliberately tries to achieve the current behaviour of wrapping extended information to the next line).

Kindly also see my email to netdev list with a more in-depth analysis of the problem and possible solutions:
http://marc.info/?l=linux-netdev&m=144309341511153&w=2

Any comments welcome, of course.

Comment 14 Jan Kurik 2016-02-24 15:39:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 15 Fedora End Of Life 2017-07-25 18:28:51 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2017-08-08 11:39:37 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.