Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
IndexSoft

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 174 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

smartd.conf




DESCRIPTION

       /etc/smartd.conf is the configuration file for the  smartd
       daemon,  which  monitors the Self-Monitoring, Analysis and
       Reporting Technology (SMART) system built into many  ATA-3
       and later ATA, IDE and SCSI-3 hard drives.

       If  smartd receives a HUP signal, it will re-read the con­
       figuration file.  If smartd is running in debug mode, then
       an  INT signal will also make it re-read the configuration
       file. An INT signal can be generated by typing <CONTROL-C>
       in the terminal window where smartd is running.


CONFIGURATION FILE /etc/smartd.conf

       In the absence of a configuration file, smartd will try to
       open the 12 ATA  devices  /dev/hd[a-l]  and  the  26  SCSI
       devices /dev/sd[a-z].  This can be annoying if you have an
       ATA or SCSI device that hangs or misbehaves when receiving
       SMART  commands.  Even if this causes no problems, you may
       be annoyed by the  string  of  error  log  messages  about
       block-major  devices that can't be found, and SCSI devices
       that can't be opened.

       One can avoid this problem, and gain more control over the
       types of events monitored by smartd, by using the configu­
       ration file /etc/smartd.conf.  This file contains  a  list
       of devices to monitor, with one device per line.  An exam­
       ple file is included with the smartmontools  distribution.
       You   will   find   this   sample  configuration  file  in
       /usr/share/doc/packages/smartmontools/. For security,  the
       configuration  file  should  not be writable by anyone but
       root. The syntax of the file is as follows:

              There  should  be  one  device  listed  per   line,
              although  you may have lines that are entirely com­
              ments or white space.

              Any text following a hash sign (#) and  up  to  the
              end  of  the  line  is  taken  to be a comment, and
              ignored.

              Lines may be continued by using a backslash (\)  as
              the  last  non-whitespace  or non-comment item on a
              line.

       Here is an example configuration file.  It's for illustra­
       tive  purposes only; please don't copy it onto your system
       # startup.
       #
         /dev/sda
         /dev/sdc -m admin@yoyodyne.com -M test
       #
       # Strange device. It's SCSI:
       #
         /dev/weird -d scsi
       #
       # Three ATA disks connected to a 3ware controller
       #
         /dev/sdb -d 3ware,0 -a
         /dev/sdb -d 3ware,1 -a
         /dev/sdb -d 3ware,2 -a
       #
       # The following line enables monitoring of the
       # ATA Error Log and the Self-Test Error Log.
       # It also tracks changes in both Prefailure
       # and Usage Attributes, apart from Attributes
       # 9, 194, and 231, and shows continued lines:
       #
         /dev/hdd -l error \
                  -l selftest \
                  -t \      # Attributes not tracked:
                  -I 194 \  # temperature
                  -I 231 \  # also temperature
                  -I 9      # power-on hours
       #
       ################################################


CONFIGURATION FILE DIRECTIVES

       If  the  first non-comment entry in the configuration file
       is the text string DEVICESCAN  in  capital  letters,  then
       smartd  will  ignore any remaining lines in the configura­
       tion file, and will  scan  for  devices.   DEVICESCAN  may
       optionally  be  followed  by Directives that will apply to
       all devices that are found in the scan.  Please see  below
       for additional details.

       The following are the Directives that may appear following
       the  device  name  or  DEVICESCAN  on  any  line  of   the
       /etc/smartd.conf  configuration  file. Note that these are
       NOT command-line options for smartd.  The Directives below
       may appear in any order, following the device name.

       For  an  ATA  device,  if  no  Directives appear, then the
       device will be monitored as if the '-a' Directive (monitor
       all SMART properties) had been given.
       (but see note below).

       -d TYPE
              Specifies the type of the device.   This  Directive
              may  be used multiple times for one device, but the
              arguments ata,  scsi,  and  3ware,N  are  mutually-
              exclusive.  If  more  than one is given then smartd
              will use the last one which appears.

              If none of these three  arguments  is  given,  then
              smartd  will first attempt to guess the device type
              by looking at whether the sixth  character  in  the
              device  name  is  an 's' or an 'h'.  This will work
              for device names like  /dev/hda  or  /dev/sdb,  and
              corresponds  to  choosing ata or scsi respectively.
              If smartd can't guess from  this  sixth  character,
              then  it will simply try to access the device using
              first ATA and then SCSI ioctl()s.

              The valid arguments to this Directive are:

              ata - the device type is ATA.  This prevents smartd
              from issuing SCSI commands to an ATA device.

              scsi  -  the  device  type  is SCSI.  This prevents
              smartd from issuing ATA commands to a SCSI  device.

              3ware,N  -  the  device consists of one or more ATA
              disks connected to a  3ware  RAID  controller.  The
              non-negative  integer  N (in the range from 0 to 15
              inclusive) denotes which disk on the controller  is
              monitored.

              This  Directive  may  at  first  appear  confusing,
              because the 3ware controller is a SCSI device (such
              as  /dev/sda)  and  should be listed as such in the
              the  configuration  file.   However  when  the  ´-d
              3ware,N´  Directive is used, then the corresponding
              disk is addressed using native ATA  commands  which
              are  ´passed  through´  the  SCSI  driver.  All ATA
              Directives listed in this man page may be used.

              Note that older 3w-xxxx drivers  do  not  pass  the
              ´Enable  Autosave´  (-S  on)  and ´Enable Automatic
              Offline´ (-o on) commands to the disk, and  produce
              these  types  of  harmless  syslog  error  messages
              instead:  ´3w-xxxx:   tw_ioctl():   Passthru   size
              (123392)  too  big´. This can be fixed by upgrading
              to version 1.02.00.037  or  later  of  the  3w-xxxx
              driver,  or  by applying a patch to older versions.
              See    http://smartmontools.sourceforge.net/    for
              normal - do not try to monitor the disk if a manda­
              tory  SMART  command  fails,  but  continue  if  an
              optional SMART command fails.  This is the default.

              permissive  -  try  to  monitor the disk even if it
              appears to lack SMART capabilities.   This  may  be
              required  for  some old disks (prior to ATA-3 revi­
              sion 4) that implemented  SMART  before  the  SMART
              standards  were  incorporated  into  the  ATA/ATAPI
              Specifications.

              [Please see the smartctl -T command-line option.]

       -o VALUE
              Enables or disables SMART Automatic Offline Testing
              when  smartd  starts  up and has no further effect.
              The valid arguments to this Directive  are  on  and
              off.

              The  delay between tests is vendor-specific, but is
              typically four hours.

              Note that SMART Automatic Offline  Testing  is  not
              part  of  the  ATA  Specification.   Please see the
              smartctl -o command-line option  documentation  for
              further information about this feature.

       -S VALUE
              Enables  or disables Attribute Autosave when smartd
              starts up and has no  further  effect.   The  valid
              arguments   to  this  Directive  are  on  and  off.
              [Please see the smartctl -S command-line option.]

       -H     Check the SMART health status of the disk.  If  any
              Prefailure  Attributes  are  less  than or equal to
              their threshold values, then disk failure  is  pre­
              dicted in less than 24 hours, and a message at pri­
              ority 'CRITICAL' will be logged to syslog.  [Please
              see the smartctl -H command-line option.]

       -l TYPE
              Reports increases in the number of errors in one of
              the two SMART logs.  The valid  arguments  to  this
              Directive are:

              error  -  report  if  that the number of ATA errors
              reported in the ATA Error Log has  increased  since
              the last check.

              selftest  -  report  if  that  the number of errors
              reported in the SMART Self-Test Log  has  increased
              since  the  last check.  Note that such errors will
              intended  design  life  period."  [Please  see  the
              smartctl -A command-line option.]

       -m ADD Send  a  warning  email to the email address ADD if
              the '-H', '-l', or '-f' Directives detect a failure
              or  a  new error, or if a SMART command to the disk
              fails. This Directive  only  works  in  conjunction
              with these other Directives (or with the equivalent
              default '-a' Directive).

              To prevent your email in-box from getting filled up
              with  warning  messages,  by  default only a single
              warning will be sent for each of the  enabled  test
              types,  '-H',  '-l', or '-f', even if more than one
              failure or error is detected or if the  failure  or
              error  persists.   [This  behavior can be modified;
              see the '-M' Directive below.]

              To send email to more than one user, please use the
              following  "comma  separated" form for the address:
              user1@add1,user2@add2,...,userN@addN    (with    no
              spaces).

              To test that email is being sent correctly, use the
              '-M test' Directive described  below  to  send  one
              test email message on smartd startup.

              By  default,  email  is  sent using the system mail
              command.  In order that smartd find the  mail  com­
              mand   (normally  /bin/mail)  an  executable  named
              'mail' must be in the path of the shell or environ­
              ment from which smartd was started.  If you wish to
              specify an explicit path  to  the  mail  executable
              (for   example  /usr/local/bin/mail)  or  a  custom
              script to run, please use the '-M  exec'  Directive
              below.

              Note  that  there  is a special argument <nomailer>
              which can be given to the '-m'  Directive  in  con­
              junction  with  the '-M exec' Directive. Please see
              below for an explanation of its effect.

       -M TYPE
              These Directives modify the behavior of the  smartd
              email  warnings  enabled with the '-m' email Direc­
              tive described above.  These '-M'  Directives  only
              work in conjunction with the '-m' Directive and can
              not be used without it.

              Multiple -M Directives may be given.  If  conflict­
              emails,  after  a  one-day interval, then a two-day
              interval, then a four-day interval, and so  on  for
              each  type  of disk problem detected. Each interval
              is twice as long as the previous interval.

              test - send a single test  email  immediately  upon
              smartd  startup.   This  allows  one to verify that
              email is delivered correctly.

              exec PATH - run the executable PATH instead of  the
              default  mail  command,  when  smartd needs to send
              email.  PATH must point  to  an  executable  binary
              file or script.

              By  setting  PATH  to point to a customized script,
              you can make smartd perform useful  tricks  when  a
              disk  problem  is  detected  (beeping  the console,
              shutting down the machine, broadcasting warnings to
              all  logged-in users, etc.)  But please be careful.
              smartd  will  block  until  the   executable   PATH
              returns,  so  if your executable hangs, then smartd
              will also hang.  Some sample scripts  are  included
              in   /usr/share/doc/packages/smartmontools/example­
              scripts/.

              The return status of the executable is recorded  by
              smartd  in  SYSLOG, but the executable's STDOUT and
              STDERR are directed to /dev/null, so if you wish to
              leave some other record behind, the executable must
              send mail or write to a file or device.

              Before running the executable, smartd sets a number
              of  environment variables.  These environment vari­
              ables may  be  used  to  control  the  executable's
              behavior.   The  environment  variables exported by
              smartd are:
              SMARTD_MAILER is set to the argument of -M exec, if
              present  or  else  to  'mail' (examples: /bin/mail,
              mail).
              SMARTD_DEVICE is set to the device path  (examples:
              /dev/hda, /dev/sdb).
              SMARTD_DEVICETYPE is set to the device type (possi­
              ble values: ata, scsi,  3ware,N).  Here  N=0,...,15
              denotes  the  ATA  disk  behind  a  3ware RAID con­
              troller.
              SMARTD_DEVICESTRING is set to the  device  descrip­
              tion.   For  SMARTD_DEVICETYPE of ata or scsi, this
              is the same as SMARTD_DEVICE.  For 3ware RAID  con­
              trollers,    the    form    used    is    ´/dev/sdc
              [3ware_disk_01]´. In this case  the  device  string
              contains  a  space  and  is  NOT quoted.  So to use
              $SMARTD_DEVICESTRING in a bash  script  you  should
              (the  command  to  read  the  SMART  self-test  log
              failed);  abd  FAILEDopendevice (the open() command
              to the device failed).
              SMARTD_ADDRESS is set to the address  argument  ADD
              of  the  '-m'  Directive, unless ADD is <nomailer>.
              This is a comma-delineated list of email  addresses
              (example: admin@yoyodyne.com).
              SMARTD_MESSAGE  is set to the warning email message
              string from smartd.  This message  string  contains
              space  characters  and  is  NOT  quoted.  So to use
              $SMARTD_MESSAGE in a bash script you should  proba­
              bly enclose it in double quotes.
              SMARTD_TFIRST  is a text string giving the time and
              date at which the first problem of  this  type  was
              reported.  This  text string contains space charac­
              ters and no newlines, and is NOT quoted. For  exam­
              ple:
              Sun Feb  9 14:58:19 2003 CST
              SMARTD_TFIRSTEPOCH is an integer, which is the unix
              epoch (number of seconds since  Jan  1,  1970)  for
              SMARTD_TFIRST.

              The  shell  which  is  used  to run PATH is system-
              dependent. For vanilla linux/glibc it's  bash.  For
              other  systems,  the man page for system (3) should
              say what shell is used.

              If the '-m ADD' Directive is given  with  a  normal
              address argument, then the executable pointed to by
              PATH will be run in a shell  with  STDIN  receiving
              the  body  of  the email message, and with the same
              command-line arguments:
              -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS
              that would normally be provided to  'mail'.   Exam­
              ples include:
              -m user@home -M exec /bin/mail
              -m admin@work -M exec /usr/local/bin/mailto
              -m root -M exec /Example_1/bash/script/below

              If the '-m ADD' Directive is given with the special
              address argument  <nomailer>  then  the  executable
              pointed  to by PATH is run in a shell with no STDIN
              and no command-line arguments, for example:
              -m <nomailer> -M exec /Example_2/bash/script/below

              Some EXAMPLES of scripts that can be used with  the
              '-M  exec'  Directive  are given below. Some sample
              scripts are also included  in  /usr/share/doc/pack­
              ages/smartmontools/examplescripts/.

       -p     Report anytime that a Prefail Attribute has changed
              integer in the range from 1 to 255.  This Directive
              modifies the behavior of the '-f' Directive and has
              no effect without it.

              This is useful, for example, if you have a very old
              disk  and don't want to keep getting messages about
              the hours-on-lifetime Attribute (usually  Attribute
              9)  failing.   This  Directive  may appear multiple
              times for a single device, if you  want  to  ignore
              multiple Attributes.

       -I ID  Ignore device Attribute ID when tracking changes in
              the Attribute values.  ID must be a decimal integer
              in  the  range from 1 to 255.  This Directive modi­
              fies the behavior  of  the  '-p',  '-u',  and  '-t'
              tracking  Directives  and has no effect without one
              of them.

              This is useful, for example, if one of  the  device
              Attributes   is   the   disk  temperature  (usually
              Attribute 194 or 231). It's annoying to get reports
              each  time the temperature changes.  This Directive
              may appear multiple times for a single  device,  if
              you want to ignore multiple Attributes.

       -r ID  When tracking, report the Raw value of Attribute ID
              along  with  its  (normally  reported)   Normalized
              value.   ID  must be a decimal integer in the range
              from 1 to 255.  This Directive modifies the  behav­
              ior of the '-p', '-u', and '-t' tracking Directives
              and has no effect without one of them.  This Direc­
              tive may be given multiple times.

              A  common  use  of  this  Directive is to track the
              device Temperature (often ID=194 or 231).

       -R ID  When tracking, report whenever  the  Raw  value  of
              Attribute   ID   changes.   (Normally  smartd  only
              tracks/reports changes of the Normalized  Attribute
              values.)  ID must be a decimal integer in the range
              from 1 to 255.  This Directive modifies the  behav­
              ior of the '-p', '-u', and '-t' tracking Directives
              and has no effect without one of them.  This Direc­
              tive may be given multiple times.

              If   this  Directive  is  given,  it  automatically
              implies the '-r' Directive for the same  Attribute,
              so that the Raw value of the Attribute is reported.

              A common use of this  Directive  is  to  track  the
              device  Temperature  (often  ID=194 or 231).  It is
              SV4012H Firmware Version:  RM100-08)  some  of  the
              two-  and  four-byte  quantities  in the SMART data
              structures are byte-swapped (relative  to  the  ATA
              specification).    Enabling   this   option   tells
              smartctl to  evaluate  these  quantities  in  byte-
              reversed  order.   Some  signs that your disk needs
              this option are (1) no self-test log printed,  even
              though you have run self-tests; (2) very large num­
              bers of ATA errors reported in the ATA  error  log;
              (3) strange and impossible values for the ATA error
              log timestamps.

              [Please see the smartctl -F command-line option.]

       -v N,OPTION
              Modifies the labeling for Attribute  N,  for  disks
              which use non-standard Attribute definitions.  This
              is useful in connection with the  Attribute  track­
              ing/reporting Directives.

              This  Directive  may  appear  multiple times. Valid
              arguments to this Directive are:

              9,minutes - Raw Attribute number 9 is power-on time
              in minutes.  Its raw value will be displayed in the
              form 'Xh+Ym'.  Here X is hours, and Y is minutes in
              the range 0-59 inclusive.  Y is always printed with
              two digits, for example ´06' or ´31' or '00'.

              9,seconds - Raw Attribute number 9 is power-on time
              in seconds.  Its raw value will be displayed in the
              form 'Xh+Ym+Zs'.  Here X is hours, Y is minutes  in
              the  range  0-59 inclusive, and Z is seconds in the
              range 0-59 inclusive.  Y and Z are  always  printed
              with  two digits, for example ´06' or ´31' or '00'.

              9,halfminutes - Raw Attribute number 9 is  power-on
              time, measured in units of 30 seconds.  This format
              is used by some Samsung disks.  Its raw value  will
              be displayed in the form 'Xh+Ym'.  Here X is hours,
              and Y is minutes in the range 0-59 inclusive.  Y is
              always printed with two digits, for example ´06' or
              ´31' or '00'.

              9,temp - Raw Attribute number 9 is the disk temper­
              ature in Celsius.

              192,emergencyretractcyclect  - Raw Attribute number
              192 is the Emergency Retract Cycle Count.

              193,loadunload - Raw Attribute number 193  contains
              194,unknown  -  Raw Attribute number 194 is NOT the
              disk  temperature,  and   its   interpretation   is
              unknown.  This is primarily useful for the -P (pre­
              sets) Directive.

              198,offlinescanuncsectorct - Raw  Attribute  number
              198 is the Offline Scan UNC Sector Count.

              200,writeerrorcount  -  Raw Attribute number 200 is
              the Write Error Count.

              201,detectedtacount - Raw Attribute number  201  is
              the Detected TA Count.

              220,temp  -  Raw  Attribute  number 220 is the disk
              temperature in Celsius.

              Note: a table of hard drive models,  listing  which
              Attribute  corresponds to temperature, can be found
              at: http://coredump.free.fr/linux/hddtemp.db

              N,raw8 - Print the Raw value of Attribute N as  six
              8-bit  unsigned base-10 integers.  This may be use­
              ful for decoding the meaning of the Raw value.  The
              form  'N,raw8' prints Raw values for ALL Attributes
              in this form.  The form  (for  example)  '123,raw8'
              only prints the Raw value for Attribute 123 in this
              form.

              N,raw16 - Print the Raw value  of  Attribute  N  as
              three  16-bit  unsigned base-10 integers.  This may
              be useful for  decoding  the  meaning  of  the  Raw
              value.   The  form  'N,raw16' prints Raw values for
              ALL Attributes in this form.  The form  (for  exam­
              ple)  '123,raw16'  only  prints  the  Raw value for
              Attribute 123 in this form.

              N,raw48 - Print the Raw value of Attribute N  as  a
              48-bit  unsigned base-10 integer.  This may be use­
              ful for decoding the meaning of the Raw value.  The
              form 'N,raw48' prints Raw values for ALL Attributes
              in this form.  The form (for  example)  '123,raw48'
              only prints the Raw value for Attribute 123 in this
              form.

       -P TYPE
              Specifies whether  smartd  should  use  any  preset
              options  that  are  available  for this drive.  The
              valid arguments to this Directive are:

              use - use any presets that are available  for  this
              Directives: '-H' to check the SMART health  status,
              '-f'  to report failures of Usage (rather than Pre­
              fail) Attributes, '-t' to  track  changes  in  both
              Prefailure  and  Usage Attributes, '-l selftest' to
              report increases in the  number  of  Self-Test  Log
              errors,  and  '-l error' to report increases in the
              number of ATA errors.

              Note that -a is the default for  ATA  devices.   If
              none of these other Directives is given, then -a is
              assumed.

       #      Comment: ignore the remainder of the line.

       \      Continuation character: if this is  the  last  non-
              white  or non-comment character on a line, then the
              following line is a  continuation  of  the  current
              one.

       If  you  are  not  sure which Directives to use, I suggest
       experimenting for a few minutes with smartctl to see  what
       SMART  functionality  your  disk(s) support(s).  If you do
       not like voluminous syslog  messages,  a  good  choice  of
       smartd configuration file Directives might be:
       -H -l selftest -l error -f.
       If you want more frequent information, use: -a.

       ADDITIONAL DETAILS ABOUT DEVICESCAN
              If the first non-comment entry in the configuration
              file is the text string DEVICESCAN in capital  let­
              ters,  then  smartd will ignore any remaining lines
              in  the  configuration  file,  and  will  scan  for
              devices.

              If  DEVICESCAN  is  not followed by any Directives,
              then  smartd  will  scan  for  both  ATA  and  SCSI
              devices,  and will monitor all possible SMART prop­
              erties of any devices that are found.

              DEVICESCAN may optionally be followed by any  valid
              Directives,  which  will  be applied to all devices
              that are found in the scan.  For example
              DEVICESCAN -m root@yoyodyne.com
              will scan for all devices, and then  monitor  them.
              It  will  send one email warning per device for any
              problems that are found.
              DEVICESCAN -d ata -m root@yoyodyne.com
              will do the same, but restricts  the  scan  to  ATA
              devices only.
              DEVICESCAN -H -d ata -m root@yoyodyne.com
              -a  to  the output of the smartd email warning mes­
              sage and sends it to ADDRESS.

              #! /bin/bash

              # Save the email message (STDIN) to a file:
              cat > /root/msg
               "
              # Append the output of smartctl -a to the message:
              /usr/sbin/smartctl -a -d $SMART_DEVICETYPE $SMARTD_DEVICE >> /root/msg

              # Now email the message to the user at address ADD:
              /bin/mail -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS < /root/msg

              Example  2:  This  script  is  for  use  with   '-m
              <nomailer>  -M exec PATH'. It warns all users about
              a disk problem, waits 30 seconds, and  then  powers
              down the machine.

              #! /bin/bash

              # Warn all users of a problem
              wall 'Problem detected with disk: ' "$SMARTD_DEVICESTRING"
              wall 'Warning message from smartd is: ' "$SMARTD_MESSAGE"
              wall 'Shutting down machine in 30 seconds... '

              # Wait half a minute
              sleep 30

              # Power down the machine
              /sbin/shutdown -hf now

              Some  example  scripts  are  distributed  with  the
              smartmontools  package,   in   /usr/share/doc/pack­
              ages/smartmontools/examplescripts/.

              Please  note  that  these  scripts typically run as
              root, so any files that they read/write should  not
              be writable by ordinary users or reside in directo­
              ries like /tmp that are writable by ordinary  users
              and may expose your system to symlink attacks.


AUTHOR

       Bruce Allen smartmontools-support@lists.sourceforge.net
       University of Wisconsin - Milwaukee Physics Department


CREDITS



SEE ALSO:

       smartd (8), smartctl (8), syslogd (8)


CVS ID OF THIS PAGE:

       $Id:  smartd.conf.5,v  1.58 2003/08/20 06:00:18 pervalidus
       Exp $

smartmontools-5.1  $Date: 2003/08/20 06:00:18 $    SMARTD.CONF(5)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =


  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds