I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
On Wed, Feb 25, 2009 at 12:50 PM, Les Mikesell lesmikesell@gmail.com wrote:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
New website with all of the missing documentation. www.google.com
It may take you a little bit to find what you're looking for, as they contain far more documentation than you could ever read in a lifetime.
/I kid! //not really
On Wed, 25 Feb 2009, Jim Perrin wrote:
On Wed, Feb 25, 2009 at 12:50 PM, Les Mikesell lesmikesell@gmail.com wrote:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
What? You can't read Postscript with less??
/usr/share/doc/iproute-2.6.18/ss.ps
---------------------------------------------------------------------- Jim Wildman, CISSP, RHCE jim@rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine
Jim Perrin wrote:
On Wed, Feb 25, 2009 at 12:50 PM, Les Mikesell lesmikesell@gmail.com wrote:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
New website with all of the missing documentation. www.google.com
It may take you a little bit to find what you're looking for, as they contain far more documentation than you could ever read in a lifetime.
/I kid! //not really
I was hoping for something easier than reading the 344,000,000 hits on google. Not kidding either.
On Wed, Feb 25, 2009 at 9:58 AM, Jim Perrin jperrin@gmail.com wrote:
On Wed, Feb 25, 2009 at 12:50 PM, Les Mikesell lesmikesell@gmail.com wrote:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
New website with all of the missing documentation. www.google.com
Thanks, Jim - I desperately needed a good laugh!
mhr
On Wed, Feb 25, 2009 at 12:50 PM, Les Mikesell lesmikesell@gmail.com wrote:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
On a slightly more helpful note, once you know the name of the rpm which provided the package, you can use 'rpm -qd packagename' to see the documentation included with that package. Not everything has a manpage, but there might be a readme or other doc with info.
On Wed, Feb 25, 2009 at 01:00:39PM -0500, Jim Perrin wrote:
On Wed, Feb 25, 2009 at 12:50 PM, Les Mikesell lesmikesell@gmail.com wrote:
I accidentally typed ss instead of ls and was surprised when it did something... ?I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
On a slightly more helpful note, once you know the name of the rpm which provided the package, you can use 'rpm -qd packagename' to see
Or, using the "f" option % rpm -qdf /usr/sbin/ss
Which could be combined with a simple grep:
% grep -lw ss $(rpm -qdf /usr/sbin/ss) /usr/share/doc/iproute-2.6.18/RELNOTES /usr/share/doc/iproute-2.6.18/ss.ps
They're the 2 files I'd look at!
on 2-25-2009 9:50 AM Les Mikesell spake the following:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
ss is part of iproute. It is similar to netstat.
Scott Silva wrote:
on 2-25-2009 9:50 AM Les Mikesell spake the following:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
ss is part of iproute. It is similar to netstat.
Yeah, but where's the 'teach a man to fish...'?
on 2-25-2009 10:29 AM Les Mikesell spake the following:
Scott Silva wrote:
on 2-25-2009 9:50 AM Les Mikesell spake the following:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
ss is part of iproute. It is similar to netstat.
Yeah, but where's the 'teach a man to fish...'?
Jim Perrin tried to teach you to fish, but as you found out, there are a lot of fish in lake Google!
OK.. Here is the fishing lesson.
"which ss" gives you a path
"yum provides /usr/sbin/ss" gives you a package name
"ls /usr/share/doc/$packagename" gives you some files to look at.
in that listing was ss.ps. Find a way to open or read ss.ps like gv or ggv and you have some info.
CSI it ain't!
On Wed, Feb 25, 2009 at 2:39 PM, Scott Silva ssilva@sgvwater.com wrote:
on 2-25-2009 10:29 AM Les Mikesell spake the following:
Scott Silva wrote:
on 2-25-2009 9:50 AM Les Mikesell spake the following:
I accidentally typed ss instead of ls and was surprised when it did something... I can use rpm's --whatprovides to see where it came from, but how are you supposed to find out want a program does when it doesn't have a man page?
ss is part of iproute. It is similar to netstat.
Yeah, but where's the 'teach a man to fish...'?
Jim Perrin tried to teach you to fish, but as you found out, there are a lot of fish in lake Google!
OK.. Here is the fishing lesson.
"which ss" gives you a path
"yum provides /usr/sbin/ss" gives you a package name
"ls /usr/share/doc/$packagename" gives you some files to look at.
in that listing was ss.ps. Find a way to open or read ss.ps like gv or ggv and you have some info.
CSI it ain't!
Reading postscript is easy with ghostscript:
# ps2ascii ss.ps | more
Should have all the pieces necessary now...
-Ross
On Wed, Feb 25, 2009 at 10:07:12AM -0800, Scott Silva wrote:
Subject: Re: [CentOS] programs with no man pages?
Upstream (debian then Fedora ) there seems to be a man page.
SS(8) SS(8)
NAME ss - another utility to investigate sockets
SYNOPSIS ss [options] [ FILTER ]
DESCRIPTION ss is used to dump socket statistics. It allows showing information similar to netstat. It can dis- play more TCP and state informations than other tools. ....
Nifty Cluster Mitch wrote:
On Wed, Feb 25, 2009 at 10:07:12AM -0800, Scott Silva wrote:
Subject: Re: [CentOS] programs with no man pages?
Upstream (debian then Fedora ) there seems to be a man page.
SS(8) SS(8)
NAME ss - another utility to investigate sockets
SYNOPSIS ss [options] [ FILTER ]
DESCRIPTION ss is used to dump socket statistics. It allows showing information similar to netstat. It can dis- play more TCP and state informations than other tools. ....
Thanks - even more than the obvious problem of finding reference documentation there is the issue of knowing you might want to use it at all. If 'man -k socket' doesn't suggest ss, how are you supposed to find out about it?
-
Jim Perrin -
Jim Wildman -
Les Mikesell -
MHR -
Nifty Cluster Mitch -
Ross Walker -
Scott Silva -
Stephen Harris