"Fossies" - the Fresh Open Source Software Archive

Member "xosview-1.23/README.linux" (11 Jul 2020, 8630 Bytes) of package /linux/misc/xosview-1.23.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1   To build xosview:
    2 
    3     Follow the instructions found in README.  In addition please consider
    4     the following:
    5 
    6       - The memory meter can now display shared memory correctly.
    7         Unfortunatly, it needs more information than a "stock" linux
    8         kernel provides to do this.  It can get this information with
    9         the help of a kernel module (memstat.o) which is provided with
   10         this release.  If this module is not loaded, then xosview will
   11         not provide a "shared" memory field in the memory meter.
   12 
   13         The memstat module is now built by default if you are running a 2.0.x
   14         or 2.2.x kernel.  Paal Beyer <pbeyer@online.no> provided code to make
   15         it work under linux 2.1.  At the moment it seems that 2.1 is in a bit
   16         of a transitory state as far as the proc filesystem goes.  So, the
   17         memstat module is disabled by default for 2.1 kernels.  It has been
   18         built under linux2.1.71.  If you do not want to build the memstat
   19         module you can run configure with a '--disable-linux-memstat' switch.
   20         At the moment this module will not work for the 2.4 kernels.
   21 
   22 To install xosview:
   23 
   24         If one installs xosview via the 'make install' target it will place
   25      things in the following locations.  The binary (xosview) will be copied
   26      to /usr/bin/X11/xosview and will be suid root.  If you do not want to
   27      run xosview suid root (this will just disable the serial meters) you
   28      can change the permissions to whatever you like.  The X defaults for
   29      xosview (Xdefaults) are copied to /usr/lib/X11/app-defaults/XOsview.
   30 
   31   To run xosview :
   32 
   33       - The network meter has been changed from the way it behaved in
   34         version 1.3.2.  It now displays the network usage in bytes / sec.
   35         This is done by using the IP accounting features of the kernel.
   36         Newer 2.1 series kernels contain this information in /proc/net/dev.
   37         If you are running one of these kernels, xosview will use this
   38         information and you will not need to read further in this section.
   39 
   40 	NOTE (2.1+ series kernels): /proc/net/dev has the downside of
   41 	logging ANY packet passing on your interface, regardless of its
   42 	destination/source. This causes the network meter to report
   43 	non-zero traffic even if there are no in/outbound packets from the
   44 	machine. Ipchains provides a way to solve this, but it requires
   45 	xosview to access /proc/net/ip_fwchains, which requires root
   46 	privileges (i.e. it's bad).  If xosview is installed setuid root
   47 	it can access the ip_fwchains file: it'll then scan it for two
   48 	chains named "iacct" and "oacct" to determine traffic.
   49 	The chains are created with the following commands (you must
   50 	be root to execute this), where YOUR-IP is either your ip or
   51 	your hostname:
   52 
   53 ipchains -N iacct
   54 ipchains -N oacct
   55 ipchains -A iacct -s \! YOUR-IP -d YOUR-IP
   56 ipchains -A oacct -s YOUR-IP -d \! YOUR-IP
   57 ipchains -A input -j iacct
   58 ipchains -A output -j oacct
   59 
   60 	(these rules will also eliminate any traffic from your machine
   61 	to your machine).
   62 
   63         If you are running an older 2.1 or 2.0 kernel then you must setup
   64         ipaccounting to get the information for xosview.  In order for this
   65         new network meter to function you must do the following for older
   66         kernels:
   67 
   68                   1 Make sure that IP accounting is enabled in your
   69                     kernel.  This means you may need to rebuild it.
   70 
   71                   2 Enable IP accounting for all IP packets into and out
   72                     of your machine.  This is done by using a program called
   73                     'ipfwadm'.  The example below is how I run ipfwadm to do
   74                     this at boot time in my rc.local:
   75 
   76 /sbin/ipfwadm -A -a -P all -S 192.168.0.3 -D 0/0
   77 /sbin/ipfwadm -A -a -P all -S 0/0 -D 192.168.0.3
   78 
   79         If you do not do these steps, you will still be able to use xosview.
   80         You just will not be able to use the network meter.
   81 
   82       - The serial meter code in has been updated so that it
   83         displays more useful information.  To do this xosview now looks
   84         directly at a couple of the serial registers.  As a result of
   85         this, xosview now need to be suid root in order to use the serial
   86         meters.  If you try to use xosview with a serial meter enabled
   87         and it is not suid root it will display a message to this effect
   88         and exit.  A non suid version of xosview will still function
   89         normally.  It just will not be able to run with the serial meters
   90         toggled on.  I hope that at some point in the future the Linux
   91         /proc filesystem will provide some more useful serial stats and
   92         xosview will not have to be suid to get serial information.
   93 
   94       - The memory meter no longer displays shared memory by default.  The
   95         information found in /proc/meminfo is not sufficient to figure out
   96         what percentage of real memory is being used for 'shared'.  There
   97         is a kernel module which comes with xosview that provides this
   98         information.  It is found in the linux/memstat directory.  If this
   99         module is loaded into the kernel, a new entry will show up in /proc
  100         called /proc/memstat.  Xosview will display a shared memory field if
  101         it finds this file (ie the memstat module is loaded).
  102 
  103       - If you have an SMP machine xosview will now show a seperate cpumeter
  104         for each processor provided your kernel has support for this.  To
  105         get this to work you will need Jerome Forissier's kernel patch which
  106         modifies the proc filesystem to provide stats on a per processor basis.
  107         You can find this patch at the following URL:
  108 
  109         http://www-isia.cma.fr/~forissie/smp_kernel_patch/
  110 
  111         These patches are only needed for 2.0 kernels.  Newer kernels
  112         already have the patch.
  113 
  114       - Raidmeter notes from Thomas Waldmann:
  115 
  116         Linux now supports a RAID meter.  This meter is disabled by default
  117         since a couple of kernel patches are currently required to get
  118         it working.  It can be enabled via an X resource.
  119 
  120         You need a kernel patched with raid0145-19990824 stuff AND
  121         mdstat-tw1.diff.  xosview RAID display won't work without
  122         mdstat-tw1.diff applied!
  123 
  124         Because I didn't find out the kernel variable which holds the md device
  125         count, you have to set it in the Xdefaults file (you don't need to
  126         change it if you have 1 md device). If you know how to modify the
  127         kernel to make this obsolete, please tell me!
  128 
  129         Also there might be some redundant values in /proc/mdstat - I just
  130         included everything that was there in old format.
  131 
  132         linux/mdstat-tw1.diff
  133           change /proc/mdstat to be more easily readable and parseable
  134 
  135         RAID1 and RAID5 arrays will give a nice "working disk map" and
  136         "resync status" display. When using a RAID1 or RAID5 array it is
  137         very important to NOTICE a disk failure. If you don't notice it
  138         because your system continues to work normally, you'll have a bad
  139         day if the next disk fails...
  140 
  141         RAID0 won't give a senseful display because there is no "working
  142         disk map" and there is no "resync status" at all. As RAID0 has no
  143         redundancy you will for sure notice a disk failure (that's the
  144         moment when all your data is gone and you need a backup tape), so
  145         you maybe won't need xosview for that.
  146 
  147 
  148         The usual disclaimer
  149         ====================
  150 
  151         The patches work on my machine, but there's no guarantee at all.
  152         Use on your OWN risk. If it breaks your RAID array, you own the parts.
  153 
  154         What you need
  155         =============
  156 
  157         kernel source 2.2.11 or 2.2.12 or 2.2.13
  158         (ftp.kernel.org/pub/linux/kernel/...)
  159 
  160         kernel RAID patch raid0145-19990824-2.2.11 + corresponding raidtools
  161         (ftp.kernel.org/pub/linux/daemons/raid/alpha/...)
  162 
  163         Installation
  164         ============
  165 
  166         Kernel
  167         ------
  168 
  169         Unpack kernel source, patch it with the RAID patch (if you are using
  170         kernel 2.2.12 or 2.2.13 you will get some warnings. Answer "n" for
  171         any question.  You can ignore the warnings safely, you get them
  172         because some stuff in the patch already IS in the kernel source).
  173 
  174         Patch your kernel source with the mdstat-tw1.diff:
  175 
  176         cd /usr/src/linux
  177         patch -p1 <mdstat-tw1.diff
  178 
  179         Compile / install kernel as usual.
  180 
  181         Install raidtools source, compile it and install binaries.
  182 
  183         Reboot.
  184 
  185         cat /proc/mdstat to see new layout.
  186 
  187 Mike Romberg (mike.romberg@noaa.gov)