Skip to content
Snippets Groups Projects
Commit 61d36f42 authored by (no author)'s avatar (no author)
Browse files

This commit was manufactured by cvs2svn to create branch 

'unlabeled-1.76.2'.

git-svn-id: https://smartmontools.svn.sourceforge.net/svnroot/smartmontools/branches/unlabeled-1.76.2@721 4ea69e1a-61f1-4043-bf83-b5c94c648137
parent ff0c70f4
No related branches found
No related tags found
No related merge requests found
Expand all Show whitespace changes
Inline Side-by-side
Showing
with 0 additions and 3374 deletions
CVSROOT/checkoutlist deleted 100644 → 0
+ 0
− 13
View file @ ff0c70f4
# The "checkoutlist" file is used to support additional version controlled
# administrative files in $CVSROOT/CVSROOT, such as template files.
#
# The first entry on a line is a filename which will be checked out from
# the corresponding RCS file in the $CVSROOT/CVSROOT directory.
# The remainder of the line is an error message to use if the file cannot
# be checked out.
#
# File format:
#
# [<whitespace>]<filename><whitespace><error message><end-of-line>
#
# comment lines begin with '#'
CVSROOT/commitinfo deleted 100644 → 0
+ 0
− 15
View file @ ff0c70f4
# The "commitinfo" file is used to control pre-commit checks.
# The filter on the right is invoked with the repository and a list
# of files to check. A non-zero exit of the filter program will
# cause the commit to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/config deleted 100644 → 0
+ 0
− 14
View file @ ff0c70f4
# Set this to "no" if pserver shouldn't check system users/passwords
#SystemAuth=no
# Put CVS lock files in this directory rather than directly in the repository.
#LockDir=/var/lock/cvs
# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
# level of the new working directory when using the `cvs checkout'
# command.
#TopLevelAdmin=no
# Set `LogHistory' to `all' or `TOFEWGCMAR' to log all transactions to the
# history file, or a subset as needed (ie `TMAR' logs all write operations)
#LogHistory=TOFEWGCMAR
CVSROOT/cvswrappers deleted 100644 → 0
+ 0
− 23
View file @ ff0c70f4
# This file affects handling of files based on their names.
#
# The -t/-f options allow one to treat directories of files
# as a single file, or to transform a file in other ways on
# its way in and out of CVS.
#
# The -m option specifies whether CVS attempts to merge files.
#
# The -k option specifies keyword expansion (e.g. -kb for binary).
#
# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
#
# wildcard [option value][option value]...
#
# where option is one of
# -f from cvs filter value: path to filter
# -t to cvs filter value: path to filter
# -m update methodology value: MERGE or COPY
# -k expansion mode value: b, o, kkv, &c
#
# and value is a single-quote delimited value.
# For example:
#*.gif -k 'b'
CVSROOT/editinfo deleted 100644 → 0
+ 0
− 21
View file @ ff0c70f4
# The "editinfo" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
CVSROOT/loginfo deleted 100644 → 0
+ 0
− 28
View file @ ff0c70f4
# The "loginfo" file controls where "cvs commit" log information
# is sent. The first entry on a line is a regular expression which must match
# the directory that the change is being made to, relative to the
# $CVSROOT. If a match is found, then the remainder of the line is a filter
# program that should expect log information on its standard input.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name ALL appears as a regular expression it is always used
# in addition to the first matching regex or DEFAULT.
#
# You may specify a format string as part of the
# filter. The string is composed of a `%' followed
# by a single format character, or followed by a set of format
# characters surrounded by `{' and `}' as separators. The format
# characters are:
#
# s = file name
# V = old version number (pre-checkin)
# v = new version number (post-checkin)
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
^sm5$ /cvsroot/sitedocs/CVSROOT/cvstools/syncmail -u %{sVv} smartmontools-cvs@lists.sourceforge.net
^www$ /cvsroot/sitedocs/CVSROOT/cvstools/syncmail -u %{sVv} ballen4705@users.sourceforge.net
CVSROOT/modules deleted 100644 → 0
+ 0
− 26
View file @ ff0c70f4
# Three different line formats are valid:
# key -a aliases...
# key [options] directory
# key [options] directory files...
#
# Where "options" are composed of:
# -i prog Run "prog" on "cvs commit" from top-level of module.
# -o prog Run "prog" on "cvs checkout" of module.
# -e prog Run "prog" on "cvs export" of module.
# -t prog Run "prog" on "cvs rtag" of module.
# -u prog Run "prog" on "cvs update" of module.
# -d dir Place module in directory "dir" instead of module name.
# -l Top-level directory only -- do not recurse.
#
# NOTE: If you change any of the "Run" options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And "directory" is a path to a directory relative to $CVSROOT.
#
# The "-a" option specifies an alias. An alias is interpreted as if
# everything on the right of the "-a" had been typed on the command line.
#
# You can encode a module within a module by using the special '&'
# character to interpose another module into the current module. This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
CVSROOT/notify deleted 100644 → 0
+ 0
− 12
View file @ ff0c70f4
# The "notify" file controls where notifications from watches set by
# "cvs watch add" or "cvs edit" are sent. The first entry on a line is
# a regular expression which is tested against the directory that the
# change is being made to, relative to the $CVSROOT. If it matches,
# then the remainder of the line is a filter program that should contain
# one occurrence of %s for the user to notify, and information on its
# standard input.
#
# "ALL" or "DEFAULT" can be used in place of the regular expression.
#
# For example:
#ALL mail %s -s "CVS notification"
CVSROOT/rcsinfo deleted 100644 → 0
+ 0
− 13
View file @ ff0c70f4
# The "rcsinfo" file is used to control templates with which the editor
# is invoked on commit and import.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being made to, relative to the
# $CVSROOT. For the first match that is found, then the remainder of the
# line is the name of the file that contains the template.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/taginfo deleted 100644 → 0
+ 0
− 20
View file @ ff0c70f4
# The "taginfo" file is used to control pre-tag checks.
# The filter on the right is invoked with the following arguments:
#
# $1 -- tagname
# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
# $3 -- repository
# $4-> file revision [file revision ...]
#
# A non-zero exit of the filter program will cause the tag to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
CVSROOT/verifymsg deleted 100644 → 0
+ 0
− 21
View file @ ff0c70f4
# The "verifymsg" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
sm5/CHANGELOG deleted 100644 → 0
+ 0
− 755
View file @ ff0c70f4
This diff is collapsed.
sm5/COPYING deleted 100644 → 0
+ 0
− 340
View file @ ff0c70f4
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
sm5/Makefile deleted 100644 → 0
+ 0
− 182
View file @ ff0c70f4
# Makefile for smartmontools
#
# Home page: http://smartmontools.sourceforge.net
#
# $Id: Makefile,v 1.65 2003/04/23 13:19:40 guidog Exp $
#
# Copyright (C) 2002-3 Bruce Allen <smartmontools-support@lists.sourceforge.net>
#
# This program is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by the Free
# Software Foundation; either version 2, or (at your option) any later
# version.
#
# You should have received a copy of the GNU General Public License (for
# example COPYING); if not, write to the Free Software Foundation, Inc., 675
# Mass Ave, Cambridge, MA 02139, USA.
#
# This code was originally developed as a Senior Thesis by Michael Cornwell
# at the Concurrent Systems Laboratory (now part of the Storage Systems
# Research Center), Jack Baskin School of Engineering, University of
# California, Santa Cruz. http://ssrc.soe.ucsc.edu/
CC = gcc
# Debugging
# CFLAGS = -fsigned-char -Wall -g
# Build against kernel header files. Change linux-2.4 to correct path for your system
# CFLAGS = -fsigned-char -Wall -O2 -I./usr/src/linux-2.4/include
# Normal build NOTE: I have had reports that with gcc 3.2 this code
# fails if you use anything but -Os. I'll remove this comment when
# this is resolved, or I am reminded of it! GCC GNATS bug report
# #8404. If you are getting strange output from gcc 3.2 try
# uncommenting LDFLAGS -s below. Stripping the symbols seems to fix
# the problem.
CFLAGS = -fsigned-char -Wall -O2
CPPFLAGS = -DHAVE_GETOPT_H -DHAVE_GETOPT_LONG
LDFLAGS = # -s
GZIP=/bin/gzip
INSTALL = install
INSTALL_PROGRAM = ${INSTALL}
INSTALL_DATA = ${INSTALL} -m 644
releasefiles=atacmds.c atacmds.h ataprint.c ataprint.h CHANGELOG COPYING \
extern.h knowndrives.c knowndrives.h Makefile README scsicmds.c scsicmds.h \
scsiprint.c scsiprint.h smartctl.8 smartctl.c smartctl.h smartd.8 smartd.c \
smartd.h smartd.initd TODO WARNINGS VERSION smartd.conf smartd.conf.5 \
utility.c utility.h examplescripts/
counter=$(shell cat VERSION)
pkgname=smartmontools-5.1
pkgname2=$(pkgname)-$(counter)
docdir=/usr/share/doc/$(pkgname)
es=examplescripts
examplesdir=$(docdir)/$(es)
all: smartd smartctl
@echo -e "\n\nSmartd can now use a configuration file /etc/smartd.conf. Do:\n\n\tman ./smartctl.8\n\tman ./smartd.8\n\tman ./smartd.conf.5\n"
@echo -e "to read the manual pages now. Unless you do a \"make install\" the manual pages won't be installed.\n"
smartctl: smartctl.c atacmds.o ataprint.o scsicmds.o scsiprint.o utility.o knowndrives.o\
smartctl.h atacmds.h ataprint.h scsicmds.h scsiprint.h \
utility.h extern.h knowndrives.h VERSION Makefile
$(CC) -DSMARTMONTOOLS_VERSION=$(counter) -o smartctl $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) smartctl.c \
atacmds.o ataprint.o knowndrives.o scsicmds.o scsiprint.o utility.o
smartd: smartd.c atacmds.o ataprint.o scsicmds.o utility.o knowndrives.o \
smartd.h atacmds.h ataprint.h knowndrives.h scsicmds.h utility.h extern.h VERSION \
Makefile
$(CC) -DSMARTMONTOOLS_VERSION=$(counter) -o smartd $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) smartd.c \
atacmds.o ataprint.o knowndrives.o scsicmds.o utility.o
atacmds.o: atacmds.c atacmds.h utility.h extern.h Makefile
$(CC) $(CFLAGS) $(CPPFLAGS) -c atacmds.c
ataprint.o: ataprint.c atacmds.h ataprint.h knowndrives.h smartctl.h extern.h utility.h \
Makefile
$(CC) $(CFLAGS) $(CPPFLAGS) -c ataprint.c
scsicmds.o: scsicmds.c scsicmds.h extern.h Makefile
$(CC) $(CFLAGS) $(CPPFLAGS) -c scsicmds.c
scsiprint.o: scsiprint.c extern.h scsicmds.h scsiprint.h smartctl.h utility.h Makefile
$(CC) $(CFLAGS) $(CPPFLAGS) -c scsiprint.c
utility.o: utility.c utility.h Makefile
$(CC) $(CFLAGS) $(CPPFLAGS) -c utility.c
knowndrives.o: knowndrives.c knowndrives.h utility.h atacmds.h ataprint.h Makefile
$(CC) $(CFLAGS) $(CPPFLAGS) -c knowndrives.c
# This extracts the configuration file directives from smartd.8 and
# inserts them into smartd.conf.5
smartd.conf.5: smartd.8
sed '1,/STARTINCLUDE/ D;/ENDINCLUDE/,$$D' < smartd.8 > tmp.directives
sed '/STARTINCLUDE/,$$D' < smartd.conf.5 > tmp.head
sed '1,/ENDINCLUDE/D' < smartd.conf.5 > tmp.tail
cat tmp.head > smartd.conf.5
echo "\# STARTINCLUDE" >> smartd.conf.5
cat tmp.directives >> smartd.conf.5
echo "\# ENDINCLUDE" >> smartd.conf.5
cat tmp.tail >> smartd.conf.5
rm -f tmp.head tmp.tail tmp.directives
clean:
rm -f *.o smartctl smartd *~ \#*\# smartmontools*.tar.gz smartmontools*.rpm temp.* smart*.8.gz smart*.5.gz
install:
if [ ! -f smartd -o ! -f smartctl ] ; then echo -e "\n\nYOU MUST FIRST DO \"make\"\n" ; exit 1 ; fi
$(GZIP) -c smartctl.8 > smartctl.8.gz
$(GZIP) -c smartd.8 > smartd.8.gz
$(GZIP) -c smartd.conf.5 > smartd.conf.5.gz
rm -f $(DESTDIR)/usr/share/man/man8/smartctl.8
rm -f $(DESTDIR)/usr/share/man/man8/smartd.8
$(INSTALL_PROGRAM) -D smartctl $(DESTDIR)/usr/sbin/smartctl
$(INSTALL_PROGRAM) -D smartd $(DESTDIR)/usr/sbin/smartd
$(INSTALL_PROGRAM) -D smartd.initd $(DESTDIR)/etc/rc.d/init.d/smartd
$(INSTALL_DATA) -D smartctl.8.gz $(DESTDIR)/usr/share/man/man8/smartctl.8.gz
$(INSTALL_DATA) -D smartd.8.gz $(DESTDIR)/usr/share/man/man8/smartd.8.gz
$(INSTALL_DATA) -D smartd.conf.5.gz $(DESTDIR)/usr/share/man/man5/smartd.conf.5.gz
$(INSTALL_DATA) -D CHANGELOG $(DESTDIR)/$(docdir)/CHANGELOG
$(INSTALL_DATA) -D COPYING $(DESTDIR)/$(docdir)/COPYING
$(INSTALL_DATA) -D README $(DESTDIR)/$(docdir)/README
$(INSTALL_DATA) -D TODO $(DESTDIR)/$(docdir)/TODO
$(INSTALL_DATA) -D VERSION $(DESTDIR)/$(docdir)/VERSION
$(INSTALL_DATA) -D WARNINGS $(DESTDIR)/$(docdir)/WARNINGS
$(INSTALL_DATA) -D smartd.conf $(DESTDIR)/$(docdir)/smartd.conf
$(INSTALL_DATA) -D $(es)/README $(DESTDIR)/$(docdir)/$(es)/README
$(INSTALL_PROGRAM) -D $(es)/Example1 $(DESTDIR)/$(examplesdir)/Example1
$(INSTALL_PROGRAM) -D $(es)/Example2 $(DESTDIR)/$(examplesdir)/Example2
$(INSTALL_PROGRAM) -D $(es)/Example3 $(DESTDIR)/$(examplesdir)/Example3
if [ ! -f $(DESTDIR)/etc/smartd.conf ]; then \
$(INSTALL_DATA) -D smartd.conf $(DESTDIR)/etc/smartd.conf; \
else \
$(INSTALL_DATA) -D smartd.conf $(DESTDIR)/etc/smartd.conf.example;\
fi
@echo -e "\n\nTo manually start smartd on bootup, run /etc/rc.d/init.d/smartd start"
@echo "To automatically start smartd on bootup, run /sbin/chkconfig --add smartd"
@echo -e "\n\nSmartd can now use a configuration file /etc/smartd.conf. Do:\nman 8 smartd\n."
@echo -e "A sample configuration file may be found in ${docdir}.\n\n"
# perhaps for consistency I should also have $(DESTDIR) for the uninstall...
uninstall:
rm -f /usr/share/man/man8/smartctl.8 /usr/share/man/man8/smartd.8 /usr/sbin/smartctl \
/usr/share/man/man8/smartctl.8.gz /usr/share/man/man8/smartd.8.gz \
/usr/share/man/man5/smartd.conf.5.gz /usr/sbin/smartd
rm -rf /usr/share/doc/smartmontools-5.1/
if [ -f /var/lock/subsys/smartd -a -f /etc/rc.d/init.d/smartd ] ; then /etc/rc.d/init.d/smartd stop ; fi
if [ -f /etc/rc.d/init.d/smartd ] ; then /sbin/chkconfig --del smartd ; fi
if [ -f /etc/rc.d/init.d/smartd ] ; then rm -f /etc/rc.d/init.d/smartd ; fi
if [ -f /etc/smartd.conf.example ] ; then rm -f /etc/smartd.conf.example ; fi
if [ -f /etc/smartd.conf ] ; then echo -e "\n\nWe have NOT REMOVED /etc/smartd.conf\n\n" ; fi
# Some of this mess is to automatically increment the release numbers.
# The number of the next release is kept in the file "VERSION"
release: smartd.conf.5
if [ ! -f add -o ! -d CVS ] ; then echo "The make release target requires files checked out of CVS" ; exit 1 ; fi
cat smartmontools.spec | sed '/Release:/d' > temp.spec
echo "Release: " $(counter) > temp.version
cat temp.version temp.spec > smartmontools.spec
rm -f temp.spec temp.version
. cvs-script && cvs commit -m "Release 5.1.$(counter)"
. cvs-script && cvs tag -d "RELEASE_5_1_$(counter)" && cvs tag "RELEASE_5_1_$(counter)"
rm -rf $(pkgname)
mkdir $(pkgname)
cp -a $(releasefiles) $(pkgname)
rm -rf $(pkgname)/examplescripts/CVS
tar zcvf $(pkgname).tar.gz $(pkgname)
mv -f $(pkgname) $(pkgname2)
tar zcvf $(pkgname2).tar.gz $(pkgname2)
rm -rf $(pkgname2)
mv -f $(pkgname).tar.gz /usr/src/redhat/SOURCES/
rpm -ba smartmontools.spec
mv /usr/src/redhat/RPMS/i386/$(pkgname)*.rpm .
mv /usr/src/redhat/SRPMS/$(pkgname)*rpm .
rm -f /usr/src/redhat/SOURCES/$(pkgname).tar.gz
echo `hostname` | grep -q lap && echo $(shell ./add) > VERSION
sm5/README deleted 100644 → 0
+ 0
− 263
View file @ ff0c70f4
===============================================
SMARTMONTOOLS - SMART utility toolset for Linux
===============================================
== HOME ==
The home for smartmontools is located at:
http://smartmontools.sourceforge.net
Please see this web site for updates, documentation, and for
submitting patches and bug reports.
You will find a mailing list for support and other questions at:
http://lists.sourceforge.net/lists/listinfo/smartmontools-support
== COPYING ==
Copyright (C) 2002-3 Bruce Allen <smartmontools-support@lists.sourceforge.net>
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2, or (at your option) any later
version.
You should have received a copy of the GNU General Public License (for
example COPYING); if not, write to the Free Software Foundation, Inc., 675
Mass Ave, Cambridge, MA 02139, USA.
== CREDITS ==
This code was originally developed as a Senior Thesis by Michael Cornwell
at the Concurrent Systems Laboratory (now part of the Storage Systems
Research Center), Jack Baskin School of Engineering, University of
California, Santa Cruz. http://ssrc.soe.ucsc.edu/
== OVERVIEW ==
SMARTMONTOOLS contains utilities that control and monitor storage
devices using the Self-Monitoring, Analysis and Reporting Technology
(S.M.A.R.T.) system build into ATA and SCSI Hard Drives. This is used
to check the reliability of the hard drive and to predict drive
failures. SMARTMONTOOLS Version 5.x is designed to comply to the
ATA/ATAPI-5 specification (Revision 1). Future releases of
SMARTMONTOOLS (Versions 6.x and 7.x) will comply with the ATA/ATAPI-6
and ATA/ATAPI-7 specifications.
This package is meant to be an up-to-date replacement for the
ucsc-smartsuite and smartsuite packages, and is derived from that
code.
== CONTENTS ==
The suite contains two utilities:
smartctl is a command line utility designed to perform
S.M.A.R.T. tasks.such as disk self-checks, and to
report the S.M.A.R.T. status of the disk.
smartd is a daemon that periodically monitors S.M.A.R.T. status and
reports errors and changes in S.M.A.R.T. attributes to syslog.
SEE THE FILE "WARNINGS" FOR REPORTS OF HARDWARE WHERE THESE UTILITIES MIGHT
CAUSE SERIOUS PROBLEMS SUCH AS LOCKUPS.
If you have just downloaded smartmontools from the URL above, then
you can read about these commands using the man pages. Within this
directory the commands:
man ./smartctl.8
and
man ./smartd.8
will display the manual pages for the two commands. If you have
already installed the package on your system, then:
man smartctl
and
man smartd
will display the same information.
== INSTALLATION ==
To install, use the commands:
make
make install
Any recent Linux distribution should support this package. Note that
smartmontools requires Linux kernel 2.2.14 or greater in order to run
at all. But to give the ATA RETURN SMART STATUS command, the kernel
needs to support the HDIO_DRIVE_TASK ioctl(). Any 2.4 series kernel
should provide this support. I am told that some of the 2.2.20 and
later kernels also provide this support if they are properly
patched/configured.
Seventeen files are installed:
/usr/sbin/smartd [Executable daemon]
/usr/sbin/smartctl [Executable command-line utility]
/etc/rc.d/init.d/smartd [Init/Startup script for smartd]
/usr/share/man/man8/smartctl.8.gz [Manual page]
/usr/share/man/man8/smartd.8.gz [Manual page]
/usr/share/man/man5/smartd.conf.5.gz [Manual page]
/usr/share/doc/smartmontools-5.1/README [What you are reading!]
/usr/share/doc/smartmontools-5.1/TODO [Things that need to be done/fixed]
/usr/share/doc/smartmontools-5.1/CHANGELOG [A log of changes. Also see CVS]
/usr/share/doc/smartmontools-5.1/COPYING [GNU Public License.]
/usr/share/doc/smartmontools-5.1/VERSION [Version number]
/usr/share/doc/smartmontools-5.1/WARNINGS [Systems where lockups or other serious problems reported]
/usr/share/doc/smartmontools-5.1/smartd.conf [Example Configuration file for /etc/]
/usr/share/doc/smartmontools-5.1/examplescripts [Executable scripts for -M exec of smartd.conf (4 files)]
Source and binary RPM files are available at the website listed above.
PLEASE READ THE MANUAL PAGES FOR SMARTCTL AND SMARTD FOR MORE INFORMATION.
STARTING WITH SMARTMONTOOLS 5.1.X, THE COMMAND LINE OPTIONS AND THE
SMARTD.CONF DIRECTIVES HAVE BEEN RENAMED. WHAT FOLLOWS IS A SUMMARY
TABLE SHOWING THE COMPARISON BETWEEN THE OLD AND THE NEW OPTION AND
DIRECTIVE NAMES.
== NEW OPTION NAMES FOR SMARTCTL 5.1 ==
The following is a synopsis of the new options in smartctl 5.1 -- please see the
man pages for more information.
-h, --help, --usage
Show usage and syntax help
-V, --version, --copyright, --license
Show version, copyright, and license info then exit
-q MODE, --quietmode=MODE
Set the quiet mode to one of: errorsonly, silent
-d TYPE, --device=TYPE
Set the device type to one of: ata, scsi
-T TYPE, --tolerance=TYPE
Set tolerance level to one of:
normal - Exit if a mandatory SMART command fails [DEFAULT]
conservative - Exit if any SMART command fails
permissive - Continue even if a mandatory SMART command fails
-b TYPE, --badsum=TYPE
Action to take on a bad checksum. TYPE and its meaning are:
warn - Issue a warning, but continue [DEFAULT]
exit - Exit smartctl
ignore - Continue silently without issuing a warning [NEW]
-s VALUE, --smart=VALUE
Enable/disable SMART. VALUE is one of: on, off
-o VALUE, --offlineauto=VALUE
Enable/disable automatic offline testing. VALUE is one of: on, off
-S VALUE, --saveauto=VALUE
Enable/disable attribute autosave. VALUE is one of: on, off
-H, --health
Show SMART health status
-c, --capabilities
Show SMART capabilities
-A, --attributes
Show SMART vendor-specific attributes and values.
-l TYPE, --log=TYPE
Show device log. Type is one of: error, selftest
-i, --info
Show drive information
-a, --all
Show all SMART information. Equivalent to -HcAi -l error -l selftest
-v N,OPTION , --vendorattribute=N,OPTION
Set vendor specific OPTION for attribute N. Currently supported are:
N OPTION Effect
-----------------------------------------------------------
009 minutes Display in minutes instead of hours
Note that in the future this option may be used multiple times
with different arguments, to modify options for different
attributes.
-t TEST, --test=TEST
Perform TEST immediately. TEST is one of: offline, short, long
-C, --captive
When used with -t, performs test in captive mode. Has no effect on
offline test, or when used without -t option.
-X, --abort
Abort any non-captive test
The following table shows the mapping of old to new smartctl options and of
old to new smartd.conf directives:
-------------------------------------------------------------------------------------------------------------------
smartctl smartctl options smartctl options smartd.conf smartd.conf
options Versions >= 5.1 Versions >= 5.1 DIRECTIVES DIRECTIVES
Versons<=5.0 (short options) (long options) Versions <= 5.0 Versions >= 5.1
-------------------------------------------------------------------------------------------------------------------
-h, -? -h, -? --help
-V -V --version, --copyright, --license
-i -i --info CONFLICT
-q -q errorsonly --quietmode=errorsonly
-Q -q silent --quietmode=silent
-n -d ata --device=ata -A -d ata
-N -d scsi --device=scsi -S -d scsi
-P -T permissive --tolerance=permissive -P -T permissive
-U -T conservative --tolerance=conservative
-W -b --badsum=exit
-r --report=TYPE
-e -s on --smart=on
-d -s off --smart=off
-t -o on --offlineauto=on -T 1 -o on
-T -o off --offlineauto=off -T 0 -o off
-f -S on --saveauto=on -s 1 -S on
-F -S off --saveauto=off -s 0 -S off
-c -H --health -c -H
-g -c --capabilities
-v -A --attributes -p, -u, -f, -t -p, -u, -t
-l -l error --log=error -l -l error
-L -l selftest --log=selftest -L -l selftest
-a -a --all -a -a
-m -v 9,minutes --vendorattribute=9,minutes
-O -t offline --test=offline
-S -t short --test=short
-s -t short -C --test=short --captive
-X -t long --test=long
-x -t long -C --test=long --captive
-A -X --abort
NOW A COMMAND-LINE OPTION (-i N, --interval N) =======> -C N Set checktime CMD LINE: -i N
-f usage attributes -f
-M ADD Email addresses -m ADD
-m -3 Email mode -M diminishing -M test
-m -2 Email mode -M daily -M test
-m -1 Email mode -M once -M test
If no -M is given, this is the DEFAULT =====> -m 0 Email mode -M once
-m 1 Email mode -M once
-m 2 Email mode -M daily
-m 3 Email mode -M diminishing
New feature (see man page) =====> -M exec SCRIPT
-i N Ignore -i N
-I N Ignore -I N
# Comment #
\ Line continuation \
-------------------------------------------------------------------------------------------------------------------
Changes to smartd options:
----------------------------------------------------------------------------------------------------------
5.0 short 5.0 long 5.1 short 5.1 long
option option option option
----------------------------------------------------------------------------------------------------------
-h, -? --help -h, -? --help
-V --version, --copyright, --license -V --version, --copyright, --license
-X --debug -d --debug
-i N --interval=N
-D --showdirectives
-r --report=TYPE
----------------------------------------------------------------------------------------------------------
sm5/TODO deleted 100644 → 0
+ 0
− 73
View file @ ff0c70f4
TODO list for smartmontools:
Home page of code is: http://smartmontools.sourceforge.net
Copyright (C) 2002-3 Bruce Allen <smartmontools-support@lists.sourceforge.net>
$Id: TODO,v 1.36 2003/04/14 22:32:02 guidog Exp $
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2, or (at your option) any later
version.
You should have received a copy of the GNU General Public License (for
example COPYING); if not, write to the Free Software Foundation, Inc., 675
Mass Ave, Cambridge, MA 02139, USA.
This code was originally developed as a Senior Thesis by Michael Cornwell
at the Concurrent Systems Laboratory (now part of the Storage Systems
Research Center), Jack Baskin School of Engineering, University of
California, Santa Cruz. http://ssrc.soe.ucsc.edu/.
Testing
-------
Test with SCSI, FireWire, USB, and SATA devices. Doug Gilbert is now
doing some of this.
Extensions
----------
Produce version for ATA/ATAPI-6 (support for extended error logs)
Produce version for ATA/ATAPI-7
smartctl:
---------
Handle extended error and self-test logs gracefully. Can someone tell
me a disk that supports more than ATA log pages 1 and 6? I need to
get a disk so I can test this functionality, when I add it.
Perhaps modify the -q option (quiet mode) so that it only warns of ATA
errors if they have (say) taken place in the last 168 hours (week).
Parse and print more attribute flag meanings (IBM ones, eg performance
etc).
smartd:
-------
Perhaps change <nomailer> special argument to -m to have also
<nomailer_fork> which would actually work with -M exec to run the
executable/script in the background rather than in the foreground.
But let's wait for someone to request this. At that point we should
probably use fork/exec rather than system().
Perhaps change smartd to look in /proc/ide and /proc/scsi to see what
exists? If something doesn't exit then don't try to open it? This
should probably be the default option if there is no configuration
file.
Add ability to monitor "worst" value from attributes (sometimes it
gets larger!) and to monitor the threshold value (sometimes it
changes!).
General Fixes
-------------
Fix lots of syntax like if (a != 0). This is now pretty much confined
to the SCSI-only parts of the code.
Use consistent error codes in exit() calls
sm5/VERSION deleted 100644 → 0
+ 0
− 1
View file @ ff0c70f4
11
sm5/WARNINGS deleted 100644 → 0
+ 0
− 16
View file @ ff0c70f4
The following are controllers/drives where there have been reports of
serious problems (eg system lockup):
SYSTEM: Dell servers using AACRAID (SCSI)
PROBLEM: Locked up, needed to be rebooted
REPORTER: drew@eastvan.bc.ca
LINK: http://sourceforge.net/mailarchive/forum.php?thread_id=1311313&forum_id=12495
SYSTEM: Box with Promise 20265 IDE-controller (pdc202xx-driver) and > 2.4.18 kernel with ide-taskfile support
PROBLEM: Smartctl locks system solid when used on /dev/hd[ef].
REPORTER: Georg Acher <acher@in.tum.de>
LINK: http://sourceforge.net/mailarchive/forum.php?thread_id=1457979&forum_id=12495
NOTE: Lockup doesn't happen with 2.4.18 kernel, and doesn't affect /dev/hd[a-d]
This appears to be a problem with the pdc202xx-driver and has been reported
to the pcdx maintainers. If you enable the the Promise-BIOS (ATA100-BIOS) then
everything will work fine. But if you disable it, then the machine will hang.
sm5/add deleted 100755 → 0
+ 0
− 8
View file @ ff0c70f4
#!/bin/bash
#
# This is a utility called in the Makefile. It's used together with
# the file "counter" to automatically increment release numbers.
#
a=`cat VERSION`
let a+=1
echo $a
sm5/atacmds.c deleted 100644 → 0
+ 0
− 1530
View file @ ff0c70f4
This diff is collapsed.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment

AEI Privacy Policy Imprint