Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

update-smart-drivedb(8) [linux man page]

UPDATE-SMART-DRIVEDB(8)                                       SMART Monitoring Tools                                       UPDATE-SMART-DRIVEDB(8)

NAME
update-smart-drivedb - update smartmontools drive database SYNOPSIS
update-smart-drivedb [OPTIONS] [DESTFILE] DESCRIPTION
[This man page is generated for the Linux version of smartmontools. It does not contain info specific to other platforms.] update-smart-drivedb updates /var/lib/smartmontools/drivedb/drivedb.h or DESTFILE from smartmontools SVN repository. It tries to download first from the current branch and then from trunk. The tools used for downloading are either curl(1), wget(1), lynx(1), or svn(1). The old file is kept if the downloaded file is identical (ignoring the differences in Id string) otherwise it is moved to drivedb.h.old. OPTIONS
-s SMARTCTL Use the smartctl(8) executable at path SMARTCTL for drive database syntax check. The form '-s -' disables the syntax check. The default is /usr/sbin/smartctl. -t TOOL Use TOOL for download. TOOL is one of: curl wget lynx svn. The default is the first one found in PATH. -u LOCATION Use URL of LOCATION for download. LOCATION is one of: sf (Sourceforge code browser via HTTPS), svn (SVN repository via HTTPS), svni (SVN repository via HTTP), trac (Trac code browser via HTTPS). The default is svn. --cacert FILE Use CA certificates from FILE to verify the peer. --capath DIR Use CA certificate files from DIR to verify the peer. --insecure Don't abort download if certificate verification fails. This option is also required if a HTTP URL is selected with '-u' option. --dryrun Print download commands only. -v Verbose output. EXAMPLES
# update-smart-drivedb /var/lib/smartmontools/drivedb/drivedb.h updated from branches/RELEASE_6_6_DRIVEDB EXIT STATUS
The exit status is 0 if the database has been successfully updated. If an error occurs the exit status is 1. FILES
/usr/sbin/update-smart-drivedb full path of this script. /usr/sbin/smartctl used to check syntax of new drive database. /var/lib/smartmontools/drivedb/drivedb.h current drive database. /var/lib/smartmontools/drivedb/drivedb.h.old previous drive database. /var/lib/smartmontools/drivedb/drivedb.h.error new drive database if rejected due to syntax errors. /var/lib/smartmontools/drivedb/drivedb.h.lastcheck empty file created if downloaded file was identical. AUTHORS
Christian Franke. This manual page was originally written by Hannes von Haugwitz <hannes@vonhaugwitz.com>. REPORTING BUGS
To submit a bug report, create a ticket in smartmontools wiki: <http://www.smartmontools.org/>. Alternatively send the info to the smartmontools support mailing list: <https://lists.sourceforge.net/lists/listinfo/smartmontools-support>. SEE ALSO
smartctl(8), smartd(8). PACKAGE VERSION
smartmontools-6.6 2016-05-31 r4324 $Id: update-smart-drivedb.8.in 4223 2016-02-26 20:18:40Z chrfranke $ smartmontools-6.6 2016-05-31 UPDATE-SMART-DRIVEDB(8)

Check Out this Related Man Page

SCROLLKEEPER-UPDATE(8)					      System Manager's Manual					    SCROLLKEEPER-UPDATE(8)

NAME
scrollkeeper-update - identify new, modified, or removed OMF files and update the scrollkeeper databases SYNOPSIS
scrollkeeper-update [ -v ] [ -q ] [ -p database-directory ] [ -o omf-directories ] DESCRIPTION
This synchronizes the scrollkeeper database with the OMF directory. It searches the scrollkeeper OMF directory to identify if any files were added, removed, or modified and updates its internal database files to reflect any changes. This utility is generally executed as the last step of installation, after the OMF file is copied into place. It is also typically the last step of uninstallation, after the OMF file is removed. Using this, an administrator can easily manually install and uninstall docu- ments into the database. It can also be run to guarantee the database is fully up-to-date. Note that because scrollkeeper-update is normally run during installation and its output is typically seen by users, non-critical warnings and errors such as those caused by invalid metadata are written to the log file instead of to the terminal. Developers should use the log file to identify any problems. OPTIONS
-v Be verbose: Say which scrollkeeper-install and scrollkeeper-uninstall commands are being run to bring the database up to date. -q Run in quiet mode, suppressing output of all but the most serious warning and error messages to STDOUT. Note that most output to the log file will be unchanged. -p database-directory Use database-directory as the directory for the scrollkeeper database rather than the usual one obtained by running omf-config --pkglocalstatedir. -o omf-directories Examine the directories named in omf-directories rather than the one usual one obtained by running scrollkeeper-config --omfdir (or specified in the OMF_DIR environment variable if set). The omf-directories should be a colon-separated list of directories. ENVIRONMENT
OMF_DIR If no -o option is specified, this variable overrides the scrollkeeper-config-provided OMF directory. It should be a colon-sepa- rated list of directories. FILES
/var/lib/scrollkeeper/scrollkeeper_docs /var/lib/scrollkeeper/TOC/<docnumber> /var/lib/scrollkeeper/<locale>/scrollkeeper_cl.xml /var/lib/scrollkeeper/<locale>/scrollkeeper_extended_cl.xml /var/log/scrollkeeper.log AUTHOR
Laszlo Kovacs <laszlo.kovacs@sun.com> Dan Mueth <d-mueth@uchicago.edu> SEE ALSO
scrollkeeper-config(1), scrollkeeper-gen-seriesid(1), scrollkeeper.conf(5), scrollkeeper(7), scrollkeeper-preinstall(8), scrollkeeper- rebuilddb(8) scrollkeeper Dec 5, 2001 SCROLLKEEPER-UPDATE(8)
Man Page