2
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
4
<!ENTITY kappname "&kinfocenter;">
5
<!ENTITY % addindex "IGNORE">
6
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
9
<book lang="&language;">
11
<title>The &infocenter;</title>
15
<firstname>Michael</firstname>
16
<surname>McBride</surname>
17
<affiliation><address>&Mike.McBride.mail;</address></affiliation>
19
<!-- TRANS:ROLES_OF_TRANSLATORS -->
23
<date>2010-01-08</date>
24
<releaseinfo>&kde; SC 4.4</releaseinfo>
27
<para>This documentation describes &kde;’s information center.</para>
31
<keyword>KDE</keyword>
32
<keyword>kinfocenter</keyword>
33
<keyword>system</keyword>
34
<keyword>information</keyword>
35
<keyword>module</keyword>
40
<chapter id="introduction">
41
<title>The &infocenter;</title>
44
The &infocenter; provides you with a centralized and convenient
45
overview of your system and desktop environment.
49
The information center is made up of multiple modules. Each module is a
50
separate application, but the information center organizes all of these
51
programs into a convenient location.
55
This next section details the use of the information center itself. For
56
information on individual modules, please see <link linkend="module">Default KInfo
57
Center Modules</link>.
60
<sect1 id="information-center-starting">
61
<title>Starting the &infocenter;</title>
64
The &infocenter; can be started in three ways:
70
By selecting <menuchoice><guimenu>Applications
71
</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Info
72
Center</guimenuitem></menuchoice> from the application launcher in the panel.
79
action="simul">&Alt;<keycap>F2</keycap></keycombo>.
80
This will bring up &krunner;. Type
81
<userinput><command>kinfocenter</command></userinput>, and press &Enter;.
87
You can type <command>kinfocenter &</command> at any command prompt.
93
All three of these methods are equivalent, and produce the same result.
98
<sect1 id="information-center-screen">
99
<title>The &infocenter; Screen</title>
102
When you start the information center, you are presented with a window,
103
which can be divided into three functional parts.
107
<screeninfo>The &infocenter; Screen.</screeninfo>
110
<imagedata fileref="kinfocenter.png" format="PNG"/>
113
<phrase>The &infocenter; Screen</phrase>
119
Across the top is a toolbar. The toolbar will provide you with quick
120
access to most of &infocenter;’s features like export, get help on the current
121
module and a help menu.
125
Along the left hand side, is a column with a filter field at the top.
126
This is a where you choose which module to investigate. To navigate through the various <acronym>KCM</acronym> modules, left click on
127
the module in the tree view. You can also use the arrow keys to scroll though the <acronym>KCM</acronym>'s and pressing &Enter; will select the module. The module will
128
now appear of the main panel of the &infocenter; window. Some items within the tree view are categories, you can left click or again press &Enter; to expand and collapsed these items. This
129
will show the modules under the category.
130
You can right click on the module listing to show the following options:
132
<listitem><para><guimenuitem>Collapse All</guimenuitem>: Collapses the tree to show only top level modules and categories.</para></listitem>
133
<listitem><para><guimenuitem>Expand All</guimenuitem>: Expands the tree to show modules.</para></listitem>
134
<listitem><para><guimenuitem>Clear Search</guimenuitem>: This will clear any filter you have applied on the module listing via the search box</para></listitem>
139
The main panel shows you the system information about the selected module.
144
In this example, we are running &kde; 2.99, we started &infocenter;
145
as user <systemitem class="username">adridg</systemitem>, the computer is
146
named <systemitem class="systemname">aramis</systemitem>, it is a
147
FreeBSD system, Version 4.4-RELEASE, on a Pentium.
152
<!--*****************************************************************-->
155
<sect1 id="info-center-menus">
156
<title>The &infocenter; Toolbar</title>
158
<para>This next section gives you a brief description of what each toolbar item does. </para>
159
<sect2 id="info-center-export-file">
161
<guimenu>Export</guimenu> button
164
The export button allows you to export information from the current information module if the
165
module allows this functionality. Clicking the export button will bring up a file dialog that will allow
166
you to choose the location of the file.
171
<sect2 id="info-center-module-help">
173
<guimenu>Module help</guimenu> button
176
This button opens khelpcenter with the current help page for the information module.
180
<sect2 id="info-center-menu-help">
181
<title><guimenu>Help</guimenu> Menu button</title>
182
&help.menu.documentation;
186
<sect1 id="info-center-exiting">
187
<title>Exiting The &kde; Information Center</title>
189
<para>You can exit the info center one of two ways: </para>
193
Type <keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo> on the keyboard.
198
<para>Click on the <guiicon>Close</guiicon> button on the frame surrounding the info center.</para>
204
<!--*****************************************************************-->
206
<chapter id="module">
207
<title>The Default &infocenter; Modules</title>
209
<!--****************************************-->
211
<sect1 id="kcm_infosummary">
212
<title>Summary Information Module</title>
215
The summary information <acronym>KCM</acronym> provides a quick way to display important information.
216
The module has three categories; <acronym>OS</acronym> Information, <acronym>CPU</acronym> Information and Hard Drive Information.
218
<note><para>You may have more than one of these information boxes per category.</para></note>
221
<title><acronym>OS</acronym> Information Box</title>
224
<screeninfo>Screenshot of <acronym>OS</acronym> Information box</screeninfo>
227
<imagedata fileref="os_block.png" format="PNG"/>
230
<phrase><acronym>OS</acronym> Information Box</phrase>
235
The <acronym>OS</acronym> information box has the following information:
238
<listitem><para><guilabel>OS Version</guilabel>: This is the version information of the Operating System KInfoCenter is present on.</para></listitem>
239
<listitem><para><guilabel>KDE SC Version</guilabel>: This is the version of the KDE Software Collection KInfoCenter was compiled on.</para></listitem>
240
<listitem><para><guilabel>Hostname</guilabel>: This is the hostname of the computer KInfoCenter is present on.</para></listitem>
246
<title><acronym>CPU</acronym> Information Box</title>
249
<screeninfo>Screenshot of <acronym>CPU</acronym> Information box</screeninfo>
252
<imagedata fileref="pro_block.png" format="PNG"/>
255
<phrase><acronym>CPU</acronym> Information Box</phrase>
260
The <acronym>CPU</acronym> information box has the following information:
263
<listitem><para><guilabel>Processor</guilabel>: This is the vendors name for your CPU</para></listitem>
264
<listitem><para><guilabel>Processor Number</guilabel>: This is the <acronym>ID</acronym> number of your <acronym>CPU</acronym>, starting from zero.</para></listitem>
265
<listitem><para><guilabel>Processor Max Speed</guilabel>: This is the processors maximum speed.</para></listitem>
271
<title>Hard Drive Information Box</title>
274
<screeninfo>Screenshot of Hard Drive Information box</screeninfo>
277
<imagedata fileref="sto_block.png" format="PNG"/>
280
<phrase>Hard Drive Information Box</phrase>
285
The Hard Drive information box has the following information:
288
<listitem><para><guilabel>Drive Title</guilabel>: This is the vendors name for the hard drive.</para></listitem>
289
<listitem><para><guilabel>Storage Size</guilabel>: This is the current size of your hard drive. </para></listitem>
290
<listitem><para><guilabel>Bus</guilabel>: This is the bus your hard drive uses.</para></listitem>
295
<!--****************************************-->
297
<sect1 id="kcm_memory">
298
<title>Memory Information Module</title>
300
<para>This module displays the current memory usage. It is updated
301
constantly, and can be very useful for pinpointing bottlenecks when certain
302
applications are executed.</para>
304
<sect2 id="memory-intro">
305
<title>Memory Types</title>
307
<para>The first thing you must understand, is there are two types of
308
<quote>memory</quote>, available to the operating system and the programs
309
that run within it.</para>
311
<para>The first type, is called physical memory. This is the memory located
312
within the memory chips, within your computer. This is the
313
<acronym>RAM</acronym> (for Random Access Memory) you bought when you
314
purchased your computer.</para>
316
<para>The second type of memory, is called virtual or swap memory. This
317
block of memory, is actually space on the hard drive. The operating
318
system reserves a space on the hard drive for <quote>swap space</quote>.
319
The operating system can use this virtual memory (or swap space), if it
320
runs out of physical memory. The reason this is called
321
<quote>swap</quote> memory, is the operating system takes some data that
322
it doesn't think you will want for a while, and saves that to disk in
323
this reserved space. The operating system then loads the new data you
324
need right now. It has <quote>swapped</quote> the not needed data, for
325
the data you need right now. Virtual or swap memory is not as fast as
326
physical memory, so operating systems try to keep data (especially often
327
used data), in the physical memory.</para>
329
<para>The total memory, is the combined total of physical memory and
330
virtual memory.</para>
334
<sect2 id="memory-use">
335
<title>Memory Information Module</title>
337
<para>This window is divided into a top and bottom section</para>
339
<para>The top section shows you the total physical memory, total free
340
physical memory, shared memory, and buffered memory.</para>
342
<para>All four values are represented as the total number of bytes, and
343
as the number of megabytes (1 megabyte = slightly more than 1,000,000
346
<para>The bottom section shows you three graphs: </para>
349
<listitem><para><guilabel>Total Memory</guilabel> (this is the combination of physical and virtual memory).</para></listitem>
350
<listitem><para><guilabel>Physical Memory</guilabel></para></listitem>
351
<listitem><para>Virtual memory, or <guilabel>Swap Space</guilabel>.</para></listitem>
354
<para>The green areas are free, and the red areas are used.</para>
356
<tip><para>The exact values of each type of memory are not critical, and
357
they change regularly. When you evaluate this page, look at
360
<para>Does your computer have plenty of free space (green areas)? If
361
not, you can increase the swap size or increase the physical
364
<para>Also, if your computer seems sluggish: is your physical memory
365
full, and does the hard drive always seem to be running? This suggests
366
that you do not have enough physical memory, and your computer is
367
relying on the slower virtual memory for commonly used data. Increasing
368
your physical memory will improve the responsiveness of your
369
computer.</para></tip>
374
<!--****************************************-->
377
<title>Device Information Module</title>
379
<para>Device Information is a device viewer module. It shows all relevant devices that are present within your <acronym>PC</acronym>. It has three sections,
380
a device viewer, a information panel and a <acronym>UDI</acronym> listing for the currently selected device.</para>
382
<title>Device Listing</title>
383
<para>The device viewer displays all the current devices detected on your <acronym>PC</acronym> in a tree. The main topics at the beginning of the tree
384
are the device categories, left click on a collapsed category to expand it and vice versa to collapse it.
385
To display information about a device, left click on the device in the viewer, the information will display on the right side information panel.
386
You can right click on the device viewer to show the following options: </para>
388
<listitem><para><guimenuitem>Collapse All</guimenuitem>: Collapses the tree to show only the main categories.</para></listitem>
389
<listitem><para><guimenuitem>Expand All</guimenuitem>: Expands the tree to show all the children devices.</para></listitem>
390
<listitem><para><guimenuitem>Show All Devices</guimenuitem>: Show all the categories no matter if devices are present in those categories</para></listitem>
391
<listitem><para><guimenuitem>Show Relevant Devices</guimenuitem>: Only show categories that have devices present.</para></listitem>
393
<para>The default display is to collapse all while showing only relevant devices. Please note that the devices shown
394
in the device listing are not all devices within your PC, they are just devices that have been detected via the Solid.</para>
395
<para> The device viewer can show the following devices:</para>
397
<listitem><para>Processors: These are your computers <acronym>CPU</acronym>s ( Central Processing Units ).</para></listitem>
398
<listitem><para>Storage Drives: Devices that are used to store your <acronym>PC</acronym>s files and data.</para></listitem>
399
<listitem><para>Network Interfaces: Devices that allow you to connect to a network or to another <acronym>PC</acronym>.</para></listitem>
400
<listitem><para>Audio Interfaces: Devices that allow your <acronym>PC</acronym> to play Sound. They are split into 2 categories, <acronym>ALSA</acronym> and <acronym>OSS</acronym> sound architectures.</para></listitem>
401
<listitem><para>Video Devices: Devices that allow you to stream live video. </para></listitem>
402
<listitem><para>Serial Devices: Devices that are connected to your serial port in your PC.</para></listitem>
403
<listitem><para>Smart Card Devices: Devices that are smart card readers. </para></listitem>
404
<listitem><para>Digital Video Broadcasting Devices: Devices that use the open standards for digital television.</para></listitem>
405
<listitem><para>Device Buttons: These are buttons that are present on your <acronym>PC</acronym> or external devices. </para></listitem>
406
<listitem><para>Batteries: These are battery devices that are plugged into your laptop. </para></listitem>
407
<listitem><para><acronym>AC</acronym> Adapters: These devices will be present when you plug in your <acronym>AC</acronym> Adapter. </para></listitem>
408
<listitem><para>Multimedia Players: Devices that play media files, like a music player. </para></listitem>
409
<listitem><para>Camera Devices: These are digital camera that are connected to your <acronym>PC</acronym>.</para></listitem>
412
<para>Video devices do not include your video card adapter</para>
415
<sect2 id="infopanel">
416
<title>Information Panel</title>
417
<para>The information panel is where device information is shown when you select a device. The first two information topics are always:</para>
419
<listitem><para><guilabel>Product</guilabel>: The name of the device.</para></listitem>
420
<listitem><para><guilabel>Vendor</guilabel>: The vendors name of the device.</para></listitem>
422
<para>The following information topics are dependent on the device chosen. They are labeled with easy to understand names.
423
The information labels have the ability to be selected and copied from.</para>
425
<para>Processor <quote>Max Speed</quote> and <quote>Supported Instruction sets</quote> topics are usual not set by solid.</para>
428
<para>Top categories in the device listing do not show any information.</para>
431
<sect2 id="udilabel">
432
<title><acronym>UDI</acronym> Information</title>
433
<para>The bottom information panel shows the current selected devices <acronym>UDI</acronym>. This is the unique device identifier.
434
The label has the ability to be selected and copied from.</para>
438
<!--****************************************-->
440
<sect1 id="interrupts">
441
<title>Interrupt Request (<abbrev>IRQ</abbrev>) Information Module</title>
443
<para>This page displays information about the Interrupt Request
444
Lines in use, and the devices that use them.</para>
446
<para>An <acronym>IRQ</acronym> is a hardware line used in a
447
<acronym>PC</acronym> by (<acronym>ISA</acronym> bus) devices like
448
keyboards, modems, sound cards, &etc;, to send interrupt signals to the
449
processor to tell it that the device is ready to send or accept data.
450
Unfortunately, there are only sixteen <acronym>IRQ</acronym>'s (0-15)
451
available in the i386 (<acronym>PC</acronym>) architecture for sharing among
452
the various <acronym>ISA</acronym> devices.</para>
454
<para>Many hardware problems are the result of <acronym>IRQ</acronym>
455
conflicts, when two devices try to use the same <acronym>IRQ</acronym>, or
456
software is misconfigured to use a different <acronym>IRQ</acronym> from the
457
one a device is actually configured for.</para>
459
<note><para>The exact information displayed is system-dependent. On some
460
systems, <acronym>IRQ</acronym> information cannot be displayed
463
<para>On &Linux;, this information is read from
464
<filename class="directory">/proc/interrupts</filename>, which is only
465
available if the <filename class="directory">/proc</filename>
466
pseudo-filesystem is compiled into the kernel.</para>
468
<para>The first column, is the <acronym>IRQ</acronym> number. The second
469
column, is the number of interrupts that have been received since the last
470
reboot. The third column shows the type of interrupt. The fourth,
471
identifies the device assigned to that interrupt.</para>
473
<para>The user cannot modify any settings on this page.</para>
476
<!--****************************************-->
479
<title><acronym>DMA</acronym> Channel Information Module</title>
481
<para> This page displays information about the <acronym>DMA</acronym>
482
(Direct Memory Access) Channels. A <acronym>DMA</acronym> channel is a
483
direct connection that allows devices to transfer data to and from
484
memory without going through the processor. Typically, i386-architecture
485
systems (<acronym>PC</acronym>'s) have eight <acronym>DMA</acronym>
486
channels (0-7). </para>
488
<note> <para> The exact information displayed is system-dependent. On
489
some systems, <acronym>DMA</acronym> Channel information cannot be
490
displayed yet. </para> </note>
492
<para> On &Linux;, this information is read from <filename
493
class="devicefile">/proc/dma</filename>, which is only available if the
494
<filename class="directory">/proc</filename> pseudo-filesystem is
495
compiled into the kernel. </para>
497
<para> A list of all currently-registered (<acronym>ISA</acronym> bus)
498
<acronym>DMA</acronym> channels that are in use is shown. The first
499
column shows the <acronym>DMA</acronym> channel, and the second column
500
shows the device which uses that channel. </para>
503
Unused <acronym>DMA</acronym> channels are not listed.
507
The user cannot modify any settings on this page.
511
<!--****************************************-->
513
<sect1 id="kcmview1394">
514
<title>IEEE 1394 Device Information Module</title>
516
<para>The IEEE 1394 interface, also known as <trademark>FireWire</trademark>,
517
is a serial bus interface standard for high-speed
518
communications and isochronous real-time data transfer.</para>
520
<para>The list in this module displays all devices attached to IEEE 1394 bus and
521
allows you to reset the bus by clicking the <guibutton>Generate 1394 Bus Reset</guibutton>
524
<para>The meaning of the columns in this list:</para>
526
<listitem><para><guilabel>Name</guilabel>: port or node name, the number can change with each bus reset</para></listitem>
527
<listitem><para><guilabel>GUID</guilabel>: the 64 bit GUID of the node</para></listitem>
528
<listitem><para><guilabel>Local</guilabel>: checked if the node is an IEEE 1394 port of your computer</para></listitem>
529
<listitem><para><guilabel>IRM</guilabel>: checked if the node is isochronous resource manager capable</para></listitem>
530
<listitem><para><guilabel>CRM</guilabel>: checked if the node is cycle master capable</para></listitem>
531
<listitem><para><guilabel>ISO</guilabel>: checked if the node supports isochronous transfers</para></listitem>
532
<listitem><para><guilabel>BM</guilabel>: checked if the node is bus manager capable</para></listitem>
533
<listitem><para><guilabel>PM</guilabel>: checked if the node is power management capable</para></listitem>
534
<listitem><para><guilabel>Acc</guilabel>: the cycle clock accuracy of the node, valid from 0 to 100</para></listitem>
535
<listitem><para><guilabel>Speed</guilabel>: the speed of the node</para></listitem>
536
<listitem><para><guilabel>Vendor</guilabel>: the vendor of the device</para></listitem>
540
<!--****************************************-->
543
<title><acronym>PCI</acronym>-bus/Installed <acronym>PCI</acronym> Cards Information Module</title>
545
<para>This page displays information about the
546
<acronym>PCI</acronym>-bus and installed <acronym>PCI</acronym> cards,
547
and other devices that use the Peripheral Component Interconnect
548
(<acronym>PCI</acronym>) bus.</para>
550
<note><para>The exact information displayed is system-dependent. On some
551
systems, <acronym>PCI</acronym>-information can not yet be
552
displayed.</para> </note>
554
<para>On &Linux;, this information is read from <filename
555
class="devicefile">/proc/pci</filename> which is only available if the
556
<filename class="directory">/proc</filename> pseudo-filesystem is
557
compiled into the kernel. A listing of all <acronym>PCI</acronym>
558
devices found during kernel initialization, and their configuration, is
561
<para>Each entry begins with a bus, device and function number.</para>
562
<para>The user cannot modify any settings on this page.</para>
565
<!--****************************************-->
568
<title>Input/Output Port Information Module</title>
570
<para>This page displays information about the I/O ports.</para>
572
<para>I/O Ports are memory addresses used by the processor for direct
573
communication with a device that has sent an
574
interrupt signal to the processor.</para>
576
<para>The exchange of commands or data between the processor and the device
577
takes place through the I/O port address of the device, which is a
579
number. No two devices can share the same I/O port. Many devices use
581
I/O port addresses, which are expressed as a range of hexadecimal
584
<note><para>The exact information displayed is system-dependent. On some
585
systems, I/O port information can not yet be displayed.</para></note>
587
<para>On &Linux;, this information is read from <filename
588
class="devicefile">/proc/ioports</filename> which is only available if
589
the <filename class="devicefile">/proc</filename> pseudo-filesystem is
590
compiled into the kernel. A list of all currently-registered I/O port
591
regions that are in use is shown.</para>
593
<para>The first column is the I/O port (or the range of I/O ports), the
594
second column identifies the device that uses these I/O ports.</para>
596
<para>The user cannot modify any settings on this page.</para>
599
<!--****************************************-->
602
<title><acronym>SCSI</acronym> Interface Information Module</title>
604
<para>This page displays information about Small Computer Systems
605
Interface (<acronym>SCSI</acronym>) Interfaces and the attached
606
<acronym>SCSI</acronym> devices.</para>
608
<note><para>The exact information displayed is system-dependent. On
609
some systems <acronym>SCSI</acronym> information cannot be displayed
612
<para>On &Linux;, this information is read from <filename
613
class="devicefile">/proc/scsi/scsi</filename>, which is only available
614
if the <filename class="directory">/proc</filename> pseudo-filesystem is
615
compiled into the kernel. A listing of all <acronym>SCSI</acronym>
616
devices known to the kernel is shown.</para>
618
<para>The devices are sorted numerically by their host, channel, and
619
<acronym>ID</acronym> numbers.</para>
621
<para>The user cannot modify any settings on this page.</para>
624
<!--****************************************-->
627
<title><acronym>USB</acronym> Controller/<acronym>USB</acronym> Devices Information Module</title>
629
<para>This module allows you to see the devices attached to your
630
<acronym>USB</acronym> bus(es).</para>
632
<para>This module is for information only, you cannot edit any
633
information you see here.</para>
636
<!--****************************************-->
638
<sect1 id="smbstatus">
639
<title>Samba Status Information Module</title>
641
<para>The Samba and <acronym>NFS</acronym> Status Monitor is a front end
642
to the programs <command>smbstatus</command> and
643
<command>showmount</command>. Smbstatus reports on current Samba
644
connections, and is part of the suite of Samba tools, which implements
645
the <acronym>SMB</acronym> (Session Message Block) protocol, also called
646
the NetBIOS or LanManager protocol.</para>
648
<para>This protocol can be used to provide printer sharing or drive
649
sharing services on a network including machines running the various
650
flavors of &Microsoft; &Windows;.</para>
652
<para><command>showmount</command> is part of the <acronym>NFS</acronym>
653
software package. <acronym>NFS</acronym> stands for Network File System
654
and is the traditional &UNIX; way to share folders over the
655
network. In this case the output of <command>showmount</command>
656
<option>-a localhost</option> is parsed. On some systems showmount is in
657
<filename class="directory">/usr/sbin</filename>, check if you have
658
showmount in your <envar>PATH</envar>.</para>
660
<sect2 id="smb-exports">
661
<title>Exports</title>
663
<para>On this page you can see a big list which shows the currently
664
active connections to Samba shares and <acronym>NFS</acronym> exports of
665
your machine. The first column shows you whether the resource is a Samba
666
(<acronym>SMB</acronym>) share or a <acronym>NFS</acronym> export. The
667
second column contains the name of the share, the third the name of the
668
remote host, which accesses this share. The remaining columns have only
669
a meaning for Samba-shares.</para>
671
<para>The fourth column contains the User <abbrev>ID</abbrev> of the
672
user, who accesses this share. Note that this does not have to be equal
673
to the &UNIX; user <abbrev>ID</abbrev> of this user. The same applies
674
for the next column, which displays the group <abbrev>ID</abbrev> of the
677
<para>Each connection to one of your shares is handled by a single
678
process (<command>smbd</command>), the next column shows the process
679
<abbrev>ID</abbrev> (<acronym>pid</acronym>) of this
680
<command>smbd</command>. If you kill this process the connected user
681
will be disconnected. If the remote user works from &Windows;, as soon
682
as this process is killed a new one will be created, so he will almost
683
not notice it.</para>
685
<para>The last column shows how many files this user has currently open.
686
Here you see only, how many files he has <emphasis>open</emphasis> just
687
now, you don't see how many he copied or formerly opened &etc;</para>
691
<sect2 id="smb-imports">
692
<title>Imports</title>
694
<para> Here you see which Samba- and <acronym>NFS</acronym>-shares from
695
other hosts are mounted on your local system. The first column shows
696
whether it is a Samba- or <acronym>NFS</acronym>-share, the second column
697
displays the name of the share, and the third shows where it is
700
<para>The mounted <acronym>NFS</acronym>-shares you should see on
701
&Linux; (this has been tested), and it should also work on &Solaris;
702
(this has not been tested).</para>
709
<para>This page presents the contents of your local samba log file in a
710
nice way. If you open this page, the list will be empty. You have to
711
press the <guibutton>Update</guibutton> button, then the samba log file
712
will be read and the results displayed. Check whether the samba log file
713
on your system is really at the location as specified in the input
714
line. If it is somewhere else or if it has another name, correct
715
it. After changing the file name you have to press
716
<guibutton>Update</guibutton> again.</para>
718
<para>Samba logs its actions according to the log level (see
719
<filename>smb.conf</filename>). If loglevel = 1, samba logs only when
720
somebody connects to your machine and when this connection is closed
721
again. If log level = 2, it logs also if somebody opens a file and if he
722
closes the file again. If the log level is higher than 2, yet more
723
stuff is logged.</para>
725
<para>If you are interested in who accesses your machine, and which
726
files are accessed, you should set the log level to 2 and regularly
727
create a new samba log file (⪚ set up a <command>cron</command> task
728
which once a week moves your current samba log file into another
729
folder or something like that). Otherwise your samba log file may
730
become very big.</para>
732
<para>With the four checkboxes below the big list you can decide, which
733
events are displayed in the list. You have to press
734
<guibutton>Update</guibutton> to see the results. If the log level of
735
your samba is too low, you won't see everything.</para>
737
<para>By clicking on the header of one column you can sort the list by
741
<sect2 id="smb-statistics">
742
<title>Statistics</title>
744
<para>On this page you can filter the contents of the third page for
745
certain contents.</para>
747
<para>Let's say the <guilabel>Event</guilabel> field (not the one in the
748
list) is set to <userinput>Connection</userinput>,
749
<guilabel>Service/File</guilabel> is set to <userinput>*</userinput>,
750
<guilabel>Host/User</guilabel> is set to <userinput>*</userinput>,
751
<guilabel>Show expanded service info</guilabel> is disabled and
752
<guilabel>Show expanded host info</guilabel> is disabled.</para>
754
<para>If you press <guibutton>Update</guibutton> now, you will see how
755
often a connection was opened to share <literal>*</literal> (&ie; to any
756
share) from host <literal>*</literal> (&ie; from any host). Now enable
757
<guilabel>Show expanded host info</guilabel> and press
758
<guibutton>Update</guibutton> again. Now you will see for every host
759
which matches the wildcard <literal>*</literal>, how many connections
760
were opened by him.</para>
762
<para>Now press <guibutton>clear</guibutton>.</para>
764
<para>Now set the <guilabel>Event</guilabel> field to File Access and
765
enable <guilabel>Show expanded service info</guilabel> and press
766
<guibutton>Update</guibutton> again.</para>
768
<para>Now you will see how often every single file was accessed. If you
769
enable <guilabel>Show expanded host info</guilabel> too, you will see
770
how often every single user opened each file.</para>
772
<para>In the input lines <guilabel>Service/File</guilabel> and
773
<guilabel>Host/User</guilabel> you can use the wildcards
774
<literal>*</literal> and <literal>?</literal> in the same way you use
775
them at the command line. Regular expressions are not
778
<para>By clicking on the header of a column you can sort the list by
779
this column. This way you can check out which file was opened most
780
often, or which user opened the most files or whatever.</para>
785
<sect2 id="smb-stat-author">
786
<title>Section Author</title>
788
<para>Module copyright 2000: Michael Glauche and &Alexander.Neundorf; &Alexander.Neundorf.mail;</para>
790
<para>Originally written by: Michael Glauche</para>
792
<para>Currently maintained by: &Alexander.Neundorf; &Alexander.Neundorf.mail;</para>
795
<title>Contributors</title>
796
<listitem><para>Conversion to kcontrol applet:</para>
797
<para>&Matthias.Hoelzer-Kluepfel; &Matthias.Hoelzer-Kluepfel.mail;</para></listitem>
798
<listitem><para>Use of <classname>K3Process</classname> instead of popen, and more error checking:</para>
799
<para>&David.Faure; &David.Faure.mail;</para></listitem>
800
<listitem><para>Conversion to kcmodule, added tab pages 2,3,4, bug
802
<para>&Alexander.Neundorf; &Alexander.Neundorf.mail;</para></listitem>
805
<para>Documentation copyright 2000 &Alexander.Neundorf; &Alexander.Neundorf.mail;</para>
807
<para>Documentation translated to docbook by &Mike.McBride; &Mike.McBride.mail;</para>
809
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
814
<!--****************************************-->
817
<title>Network Interfaces Information Module</title>
820
This page displays information about the network interfaces
821
installed in your computer.
824
<note><para>The exact information displayed is system-dependent. On
825
some systems, this information can not yet be displayed.</para></note>
827
<para>The user cannot modify any settings on this page.</para>
830
<!--****************************************-->
833
<title>OpenGL Information Module</title>
835
<para>This page displays information about installed <acronym>OpenGL</acronym> implementation.
836
OpenGL (for "Open Graphics Library") is a cross-platform,
837
hardware independent interface for 3D graphics. </para>
839
<para><acronym>GLX</acronym> is the binding for OpenGL to X Window system.</para>
841
<para> <acronym>DRI</acronym> (Direct Rendering Infrastucture) provides hardware acceleration for OpenGL.
842
You must have a videocard with 3D accelerator and properly installed driver for this.</para>
845
<para>Read more at the official OpenGL site <ulink url="http://www.opengl.org">http://www.opengl.org</ulink> </para>
848
<!--****************************************-->
851
<title>X Server Information Module</title>
853
<para>This screen is useful for getting specific information about your
854
X server and the current session of X.</para>
856
<para>When you open this module, you are presented with some
857
information. The left hand side of the window is organized into a
858
tree. Some of the elements have a plus sign in front of the label.
859
Clicking this sign opens a <quote>submenu</quote> related to the
860
label. Clicking on a minus sign in front of a label hides the
863
<para>The right hand side of the window contains the individual
864
values for each of the parameters on the left.</para>
866
<para>The information presented will vary depending on your
869
<note><para>Some setups may not be able to determine some or all of the
870
parameters.</para></note>
872
<para>You can not change any values from this menu. It is for
873
information only.</para>
876
<!--****************************************-->
880
<chapter id="credits">
881
<title>Credits and License</title>
883
<para>&infocenter;</para>
884
<para>Program copyright 1997-2001 The &infocenter; Developers</para>
885
<para>Contributors:</para>
888
<listitem><para>Matthias Hoelzer-Kluepfel
889
&Matthias.Hoelzer-Kluepfel.mail;</para></listitem>
890
<listitem><para>&Matthias.Elter; &Matthias.Elter.mail;</para></listitem>
893
<para>Documentation <trademark class="copyright">copyright 2000 Michael
894
McBride</trademark> &Mike.McBride.mail;</para>
896
<para>Contributors:</para>
899
<listitem><para>&Paul.Campbell; &Paul.Campbell.mail;</para></listitem>
900
<listitem><para>&Helge.Deller; &Helge.Deller.mail;</para></listitem>
901
<listitem><para>&Mark.Donohoe;</para></listitem>
902
<listitem><para>&Patrick.Dowler;</para></listitem>
903
<listitem><para>&Duncan.Haldane; <email>duncan@kde.org</email></para></listitem>
904
<listitem><para>&Steffen.Hansen; <email>stefh@mip.ou.dk</email>.</para></listitem>
905
<listitem><para>Matthias Hoelzer-Kluepfel &Matthias.Hoelzer-Kluepfel.mail;</para></listitem>
906
<listitem><para>Martin Jones &Martin.R.Jones.mail;</para></listitem>
907
<listitem><para>&Jost.Schenck; &Jost.Schenck.mail;</para></listitem>
908
<listitem><para>&Jonathan.Singer; &Jonathan.Singer.mail;</para></listitem>
909
<listitem><para>&Thomas.Tanghus; &Thomas.Tanghus.mail;</para></listitem>
910
<listitem><para>&Krishna.Tateneni; &Krishna.Tateneni.mail;</para></listitem>
911
<listitem><para>Ellis Whitehead <email>ewhitehe@uni-freiburg.de</email></para></listitem>
915
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->