File health-checker-1.12+git20241105.2e2832f15742.ob... of Package health-checker

Overview Repositories Revisions Requests Users Attributes Meta

File health-checker-1.12+git20241105.2e2832f15742.obscpio of Package health-checker (Revision 28265b1fc829241a6dd252d4aff1ec55)

Currently displaying revision 28265b1fc829241a6dd252d4aff1ec55 , Show latest

07070100000000000081A40000000000000000000000016729D084000001E2000000000000000000000000000000000000003800000000health-checker-1.12+git20241105.2e2832f15742/.gitignoreMakefile.in
/autom4te.cache
/aclocal.m4
/compile
/configure
/depcomp
/install-sh
/missing
/stamp-h1
# files generated by configure
.deps
.libs
Makefile
config.h
*.o
*.lo
*.la
*.a
*~
*.rej
*.orig
core
config.log
config.status
test-driver
test-suite.log
check-output.*
health-checker-*.tar.*
man/health-checker.8
man/health-checker.index.html
man/health-checker.index.xml
man/health-checker.service.8
man/*.html
man/*.pyc
sbin/health-checker
man/__pycache__/
man/health-checker.8.xml
07070100000001000081A40000000000000000000000016729D0840000467E000000000000000000000000000000000000003500000000health-checker-1.12+git20241105.2e2832f15742/COPYING                    GNU GENERAL PUBLIC LICENSE
                       Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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 Lesser 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.

{description}
    Copyright (C) {year}  {fullname}

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.,
    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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) year 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 Lesser General
Public License instead of this License.
07070100000002000081A40000000000000000000000016729D08400003D85000000000000000000000000000000000000003500000000health-checker-1.12+git20241105.2e2832f15742/INSTALLInstallation Instructions
*************************

Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.  This file is offered as-is,
without warranty of any kind.

Basic Installation
==================

Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package.  The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.  Some packages provide this
`INSTALL' file but do not implement all of the features documented
below.  The lack of an optional feature in a given package is not
necessarily a bug.  More recommendations for GNU packages can be found
in *note Makefile Conventions: (standards)Makefile Conventions.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').

It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring.  Caching is
disabled by default to prevent problems with accidental use of stale
cache files.

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'.  You need `configure.ac' if
you want to change it or regenerate `configure' using a newer version
of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.

Running `configure' might take a while.  While running, it prints
     some messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Optionally, type `make check' to run any self-tests that come with
     the package, generally using the just-built uninstalled binaries.

4. Type `make install' to install the programs and any data files and
     documentation.  When installing into a prefix owned by root, it is
     recommended that the package be configured and built as a regular
     user, and only the `make install' phase executed with root
     privileges.

5. Optionally, type `make installcheck' to repeat any self-tests, but
     this time using the binaries in their final installed location.
     This target does not install anything.  Running this target as a
     regular user, particularly if the prior `make install' required
     root privileges, verifies that the installation completed
     correctly.

6. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

7. Often, you can also type `make uninstall' to remove the installed
     files again.  In practice, not all packages have tested that
     uninstallation works correctly, even though it is required by the
     GNU Coding Standards.

8. Some packages, particularly those that use Automake, provide `make
     distcheck', which can by used by developers to test that all other
     targets like `make install' and `make uninstall' work correctly.
     This target is generally not run by end users.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  Run `./configure --help'
for details on some of the pertinent environment variables.

You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment.  Here
is an example:

./configure CC=c99 CFLAGS=-g LIBS=-lposix

*Note Defining Variables::, for more details.

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you can use GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.  This
is known as a "VPATH" build.

With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory.  After you have
installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.

On MacOS X 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
"universal" binaries--by specifying multiple `-arch' options to the
compiler but only a single `-arch' option to the preprocessor.  Like
this:

./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
                 CPP="gcc -E" CXXCPP="g++ -E"

This is not guaranteed to produce working output in all cases, you
may have to build one architecture at a time and combine the results
using the `lipo' tool if you have problems.

Installation Names
==================

By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc.  You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX', where PREFIX must be an
absolute file name.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.

In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.  In general, the
default for these options is expressed in terms of `${prefix}', so that
specifying just `--prefix' will affect all of the other directory
specifications that were not explicitly provided.

The most portable way to affect installation locations is to pass the
correct locations to `configure'; however, many packages provide one or
both of the following shortcuts of passing variable assignments to the
`make install' command line to change installation locations without
having to reconfigure or recompile.

The first method involves providing an override variable for each
affected directory.  For example, `make install
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
`${prefix}'.  Any directories that were specified during `configure',
but not in terms of `${prefix}', must each be overridden at install
time for the entire installation to be relocated.  The approach of
makefile variable overrides for each directory variable is required by
the GNU Coding Standards, and ideally causes no recompilation.
However, some platforms have known limitations with the semantics of
shared libraries that end up requiring recompilation when using this
method, particularly noticeable in packages that use GNU Libtool.

The second method involves providing the `DESTDIR' variable.  For
example, `make install DESTDIR=/alternate/directory' will prepend
`/alternate/directory' before all installation names.  The approach of
`DESTDIR' overrides is not required by the GNU Coding Standards, and
does not work on platforms that have drive letters.  On the other hand,
it does better at avoiding recompilation issues, and works well even
when some directory options were not specified in terms of `${prefix}'
at `configure' time.

Optional Features
=================

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Some packages offer the ability to configure how verbose the
execution of `make' will be.  For these packages, running `./configure
--enable-silent-rules' sets the default to minimal output, which can be
overridden with `make V=1'; while running `./configure
--disable-silent-rules' sets the default to verbose, which can be
overridden with `make V=0'.

Particular systems
==================

On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
CC is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:

./configure CC="cc -Ae -D_XOPEN_SOURCE=500"

and if that doesn't work, install pre-built binaries of GCC for HP-UX.

HP-UX `make' updates targets which have the same time stamps as
their prerequisites, which makes it generally unusable when shipped
generated files such as `configure' are involved.  Use GNU `make'
instead.

On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
a workaround.  If GNU CC is not installed, it is therefore recommended
to try

./configure CC="cc"

and if that doesn't work, try

./configure CC="cc -nodtk"

On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
directory contains several dysfunctional programs; working variants of
these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
in your `PATH', put it _after_ `/usr/bin'.

On Haiku, software installed for all users goes in `/boot/common',
not `/usr/local'.  It is recommended to use the following options:

./configure --prefix=/boot/common

Specifying the System Type
==========================

There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on.  Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:

CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

OS
     KERNEL-OS

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.

If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.

If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.

Sharing Defaults
================

If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Defining Variables
==================

Variables not defined in a site shell script can be set in the
environment passed to `configure'.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'.  For example:

./configure CC=/usr/local2/bin/gcc

causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).

Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf limitation.  Until the limitation is lifted, you can use
this workaround:

CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash

`configure' Invocation
======================

`configure' recognizes the following options to control how it
operates.

`--help'
`-h'
     Print a summary of all of the options to `configure', and exit.

`--help=short'
`--help=recursive'
     Print a summary of the options unique to this package's
     `configure', and exit.  The `short' variant lists options used
     only in the top level, while the `recursive' variant lists options
     also present in any nested packages.

`--version'
`-V'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`--cache-file=FILE'
     Enable the cache: use and save the results of the tests in FILE,
     traditionally `config.cache'.  FILE defaults to `/dev/null' to
     disable caching.

`--config-cache'
`-C'
     Alias for `--cache-file=config.cache'.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--prefix=DIR'
     Use DIR as the installation prefix.  *note Installation Names::
     for more details, including other options available for fine-tuning
     the installation locations.

`--no-create'
`-n'
     Run the configure checks, but stop before creating any output
     files.

`configure' also accepts some other, not widely useful, options.  Run
`configure --help' for more details.
07070100000003000081A40000000000000000000000016729D0840000013E000000000000000000000000000000000000003900000000health-checker-1.12+git20241105.2e2832f15742/Makefile.am#
# Copyright (c) 2017 Thorsten Kukuk, Germany
#
# Author: Thorsten Kukuk <kukuk@suse.de>
#
AUTOMAKE_OPTIONS = 1.6 foreign check-news dist-xz
#
SUBDIRS = sbin man systemd plugins dracut grub

CLEANFILES = *~

M4_FILES = m4/jh_path_xml_catalog.m4

EXTRA_DIST = $(M4_FILES) README.md autogen.sh

ACLOCAL_AMFLAGS = -I m4
07070100000004000081A40000000000000000000000016729D08400000CFE000000000000000000000000000000000000003200000000health-checker-1.12+git20241105.2e2832f15742/NEWShealth-checker NEWS -- history of user-visible changes.

Version 1.12
* Improve RPM database consistency check: Use rpm command directly to
  prevent blocking when there is no zypper database yet or when the
  admin intentionally broke dependencies
* Implement missing stop argument for RPM database consistency plugin
* Fixes typo in GRUB plugin so that the detection always used the
  fallback file
* Drop crio, etcd and kubelet plugins because the corresponding products
  are EOL

Version 1.11
* Add RPM database consistency plugin
* Messages are printed with a severity prefix now
* Fix various typos
* Add missing rule for health-checker.service.8
* Remove HTML output of man pages (the man pages are rendered by a
  common service on manpages.opensuse.org now)

Version 1.10
* Fix Btrfs subvolume check if subvol starts with '-'

Version 1.9
* Fix failing subvolume mount checks with certain characters in mount
  point [gh#openSUSE/health-checker#14].

Version 1.8
* Don't rely on t-u's good states in GRUB
  With the introduction of the "apply" command in transactional-update the
  snapshot id's cannnot be reused any more. Due to that store the snapshot
  number separately now, too.

Version 1.7
* Before rollback make sure /.snapshots is mounted rw
* Fix typos and spelling errors. Note: in case an application is parsing
  the output it will need to adopt to the new strings.

Version 1.6
* Adapt rd.retry to also trigger initqueue timeout tasks
  [gh#kubic-project/health-checker#11]
* Reboot system and let the GRUB health-checker part try to find a
  working initrd if root file system could not be mounted - instead of
  ending up in an emergency shell
* Correctly declare Bash scripts as such

Version 1.5
* Added /usr/local/libexec/health-checker for user defined plugins.

Version 1.4
* Add checks for /tmp and systemd-logind
* Transition system into emergency mode on repeated failures to prevent
  random jobs from modifying the broken system
* Build system cleanup

Version 1.3.4
* Really fix plugindir replacement in configure.ac script

Version 1.3.3
* Fix plugindir replacement in configure.ac script
* Use Python 3 for building documentation

Version 1.3.2
* Use pkgconf to determine installation directories

Version 1.3.1
* Support multiple menuentries in GRUB configuration
  [gh#kubic-project/health-checker#5]

Version 1.3
* Support /var on non-root device for reading health data
* Avoid GRUB error message if env_block is not set [boo#1151072]
* Don't show message on manual emergency shell invocation
* Fix handling when booting a non-default snapshot

Version 1.2.3
* Fix name of crio RPM

Version 1.2.2
* Fix naming in systemd units

Version 1.2.1
* Fix telemetrics payload in success case

Version 1.2
* Add hooks for telemetrics events

Version 1.1
* Add checks for kubelet and crio

Version 1.0
* Skip health checker if emergency shell started by user
* Add GRUB2 fallback handling
* Adapt to new unified /var directory.
* Get basic version of rollback from initrd working

Version 0.5
* Fix logger arguments

Version 0.4
* Add script to verify btrfs subvolume mounts

Version 0.3
* First code for dracut module added
* Wrote documentation

Version 0.2
* Add plugins for etcd, rebootmgr, overlayfs for /etc

Version 0.1
* Initial release
07070100000005000081A40000000000000000000000016729D084000006F6000000000000000000000000000000000000003700000000health-checker-1.12+git20241105.2e2832f15742/README.md# health-checker

Check the state of a openSUSE MicroOS system after a reboot.

## How does this work?

`health-checker` will be called by a systemd service during the boot
process. All services, which should be checked, needs to be listed in the
'After' section.

The `health-checker` script will call several plugins. Every plugin is
responsible to check a special service or condition. For this, the plugin is
called with the option *check*. If this fails, the plugin will exit with the
return value `1`, else `0`.
If everyting was fine, the script will create a
`/var/lib/misc/health-check.state` file with the number of the current,
working btrfs subvolume with the root filesystem.
If a plugin reports an error condition, the `health-checker` script will take
following actions:

1. If the current btrfs root subvolume is not identical with the last known
   working snapshot, an automatic rollback to that snapshot is made. Normally,
   if the current btrfs subvolume is not identical to the last working one,
   this means an update was made, and this update did never boot correctly.
2. If the current btrfs subvolume did already boot successful in the past, the
   problem is most likely a temporary problem. In this case, we try to reboot
   the machine again. `/var/lib/misc/health-check.rebooted` will be created
   with the current time.
3. If the current btrfs snapshot did already boot successful in the past and
   if we did try already to solve the problem with a reboot, it doesn't make
   sense to reboot again. To give the admin the chance and possibility to fix
   the problem, all plugins will be called with the option *stop*. At the
   end, the machine should still run, so that an admin can login, but no
   service should run, so that nothing can break.
07070100000006000081ED0000000000000000000000016729D08400000096000000000000000000000000000000000000003800000000health-checker-1.12+git20241105.2e2832f15742/autogen.sh#!/bin/sh -x

rm -fv ltmain.sh config.sub config.guess config.h.in
aclocal -I m4
automake --add-missing --copy --force
autoreconf
chmod 755 configure
07070100000007000081A40000000000000000000000016729D084000004F7000000000000000000000000000000000000003A00000000health-checker-1.12+git20241105.2e2832f15742/configure.acdnl Process this file with autoconf to produce a configure script.
AC_INIT(health-checker, 1.12)
AM_INIT_AUTOMAKE
AC_PREFIX_DEFAULT(/usr)

AC_SUBST(PACKAGE)
AC_SUBST(VERSION)

PKG_CHECK_VAR([systemdsystemunitdir], [systemd], [systemdsystemunitdir], [],
	[AC_MSG_ERROR([Could not determine value for 'systemdsystemunitdir' - is the 'systemd.pc' file installed?])])
PKG_CHECK_VAR([dracutmodulesdir], [dracut], [dracutmodulesdir], [],
	[AC_MSG_ERROR([Could not determine value for 'dracutmodulesdir' - is the 'dracut.pc' file installed?])])

AC_PROG_INSTALL
AC_PROG_LN_S

dnl
dnl Check for xsltproc
dnl
enable_man=yes
AC_PATH_PROG([XSLTPROC], [xsltproc])
if test -z "$XSLTPROC"; then
     enable_man=no
fi
AC_PATH_PROG([XMLLINT], [xmllint],[/bin/true])
dnl check for DocBook DTD and stylesheets in the local catalog.
JH_CHECK_XML_CATALOG([-//OASIS//DTD DocBook XML V4.3//EN],
                [DocBook XML DTD V4.3], [], enable_man=no)
JH_CHECK_XML_CATALOG([http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl],
                [DocBook XSL Stylesheets], [], enable_man=no)
AM_CONDITIONAL(ENABLE_REGENERATE_MAN, test x$enable_man != xno)

AC_OUTPUT([Makefile sbin/Makefile man/Makefile systemd/Makefile \
	plugins/Makefile dracut/Makefile grub/Makefile])
07070100000008000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003400000000health-checker-1.12+git20241105.2e2832f15742/dracut07070100000009000081A40000000000000000000000016729D084000000C3000000000000000000000000000000000000004000000000health-checker-1.12+git20241105.2e2832f15742/dracut/Makefile.am#
# Copyright (c) 2017 Thorsten Kukuk <kukuk@suse.de>
#

modulesdir = $(dracutmodulesdir)/50health-checker

modules_SCRIPTS = health-checker-emergency.sh module-setup.sh

EXTRA_DIST = $(SCRIPTS)
0707010000000A000081ED0000000000000000000000016729D08400000CD8000000000000000000000000000000000000005000000000health-checker-1.12+git20241105.2e2832f15742/dracut/health-checker-emergency.sh#!/bin/bash

# if we enter emergency mode, do:
# - if it's not even possible to mount the root file system reboot and try to
#   recover using grub
# otherwise:
# - on first boot after update, rollback to old snapshot
# - if it is not the first boot, reboot
# - if reboot does not help, log this
#

HC_ROOT_MOUNT="/run/health-checker"
STATE_FILE="${HC_ROOT_MOUNT}/var/lib/misc/health-check.state"
REBOOTED_STATE="${HC_ROOT_MOUNT}/var/lib/misc/health-check.rebooted"

BTRFS_ID=0

set_btrfs_id()
{
    BTRFS_ID=`btrfs subvolume get-default "${HC_ROOT_MOUNT}" | awk '{print $2}'`
}

umount_and_reboot()
{
  if findmnt "${HC_ROOT_MOUNT}" > /dev/null; then
    umount --recursive "${HC_ROOT_MOUNT}"
  fi
  systemctl reboot --force
}

clear_and_reboot()
{
  # Try to clear the health_checker flag variable in GRUB environment variable
  # block
  echo "Clearing GRUB health_checker_flag"
  grub2-editenv - set health_checker_flag=0

umount /run/health-checker
  systemctl reboot --force
}

try_grub_recovery()
{
  warn "WARN: Trying recovery via GRUB2 snapshot mechanism."
  umount_and_reboot
}

rollback()
{
    . ${STATE_FILE}
    btrfs subvolume set-default ${LAST_WORKING_BTRFS_ID} "${HC_ROOT_MOUNT}"
    if [ $? -ne 0 ]; then
        warn "ERROR: btrfs set-default $BTRFS_ID failed!"
        return 1
    fi
}

error_decission()
{
    if [ ! -f ${STATE_FILE} ]; then
        # No state file, no successful boot, start emergency shell
	info "INFO: No successful previous boot."
        return 0
    fi

. ${STATE_FILE}

set_btrfs_id

if [ ${LAST_WORKING_BTRFS_ID} -ne ${BTRFS_ID} ]; then
      warn "WARN: Machine didn't come up correctly, doing a rollback."
      rollback
      if [ $? -eq 0 ]; then
        clear_and_reboot
      fi
  elif [ ! -f ${REBOOTED_STATE} ]; then
      warn "WARN: Machine didn't come up correctly, trying a reboot."
      echo `date "+%Y-%m-%d %H:%M"` > ${REBOOTED_STATE}
      clear_and_reboot
  else
      warn "WARN: Machine didn't come up correctly, starting emergency shell."
      return 0
  fi
}

info "Health Checker Emergency Mode"

# Make sure we know root device
[ -z "$root" ] && root=$(getarg root=)

if getargbool 0 rd.break; then
  true # manual invocation of emergency shell, doing nothing
elif [ -n "$root" -a -z "${root%%block:*}" ]; then

info "root device: ${root}"

local my_root="${root#block:}"

info "my_root device: ${my_root}"

# Try to mount health-checker data
  mkdir -p "${HC_ROOT_MOUNT}"
  if mount "${my_root}" "${HC_ROOT_MOUNT}"; then
    info "my_root mounted successfully"
    state_dev_cands=("/var/lib/misc" "/var")
    for cand in "${state_dev_cands[@]}"; do
      findmnt --first-only --direction backward --noheadings --tab-file "${HC_ROOT_MOUNT}/etc/fstab" "${cand}" | while read _m _d _t _o; do
        mkdir -p "${HC_ROOT_MOUNT}/${cand}"
        mount -t ${_t} -o ${_o} ${_d} "${HC_ROOT_MOUNT}/${cand}"
      done
    done
  else
    warn "WARN: Mounting root device failed."
    try_grub_recovery
  fi

# Try to recover somehow
  if [ -e "${HC_ROOT_MOUNT}/var/lib/misc" ]; then
    error_decission
    umount --recursive "${HC_ROOT_MOUNT}" ||:
  else
    warn "WARN: Mounting health-checker data failed."
    try_grub_recovery
  fi
else
  warn "WARN: No root device found."
  try_grub_recovery
fi
0707010000000B000081ED0000000000000000000000016729D0840000011C000000000000000000000000000000000000004400000000health-checker-1.12+git20241105.2e2832f15742/dracut/module-setup.sh#!/bin/bash

# called by dracut
check() {
    require_binaries logger date || return 1
}

# called by dracut
depends() {
    echo drm
}

# called by dracut
install() {
    inst_hook emergency 90 "$moddir"/health-checker-emergency.sh

inst_multiple date btrfs awk grub2-editenv
}

0707010000000C000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003200000000health-checker-1.12+git20241105.2e2832f15742/grub0707010000000D000081ED0000000000000000000000016729D084000007CE000000000000000000000000000000000000004200000000health-checker-1.12+git20241105.2e2832f15742/grub/05_health_check#!/bin/sh
set -e

cat << EOF
# Only consider showing a fallback entry on the top level menu
if [ -z "\${chosen}" -a -z "\${boot_once}" ]; then
  # If flag is set on boot the last start seems to have failed - the flag
  # should have been cleared by userspace
  if [ "\${health_checker_flag}" -ge 1 ]; then
    # Reset flag; it will be set again by a supported menu entry.
    # This prevents getting stuck in a loop when booting an entry that
    # doesn't support this flag yet.
    health_checker_flag=0
    if [ "\${env_block}" ] ; then
      save_env -f "\${env_block}" health_checker_flag
    fi
    # Try to mount /var/lib/misc from know subvolume locations
    btrfs-mount-subvol (\${root}) /var /@/var
    btrfs-mount-subvol (\${root}) /var/lib/misc /@/var/lib/misc

if [ -e /var/lib/misc/health-check.state ]; then
      source /var/lib/misc/health-check.state
      if [ -n \${LAST_WORKING_SNAPSHOT} ]; then
        LAST_WORKING_SNAPSHOTS=\${LAST_WORKING_SNAPSHOT}
      fi
    fi

# Backwards compatibility (for state file created with old
    # health-checker versions):
    # Due to boo#1048088 btrfs-list-subvols currently doesn't give a list of
    # subvolumes, so it's not possible to map
    # /var/lib/misc/health-check.state to a snapshot directory; use
    # transactional-update state file as a workaround.
    if [ -z \${LAST_WORKING_SNAPSHOTS} -a -e /var/lib/misc/transactional-update.state ]; then
      source /var/lib/misc/transactional-update.state
    fi

if [ -n "\${LAST_WORKING_SNAPSHOTS}" ]; then
      btrfs-mount-subvol (\$root) /.snapshots @/.snapshots
      for snapshot in \${LAST_WORKING_SNAPSHOTS}; do
        if [ -e "/.snapshots/\${snapshot}/grub-snapshot.cfg" ]; then
          menuentry "Previous boot failed; booting snapshot \${snapshot}" { true; }
          source /.snapshots/\${snapshot}/grub-snapshot.cfg
          menuentry "________________" { true; }
          set default=1
          break
        fi;
      done
    fi
  fi
fi
EOF
0707010000000E000081ED0000000000000000000000016729D084000005D9000000000000000000000000000000000000004900000000health-checker-1.12+git20241105.2e2832f15742/grub/83_health_check_marker#!/bin/bash
set -e

# GRUB's grub2_mkconfig script currently has some serious limitations, one of 
# them being not providing a way to modify anything done by previous scripts;
# unfortunately health_checker requires additional commands to be executed
# when selecting a boot entry (which is usually created by 10_linux), so as a
# horrible workaround the temporary output will be modified by a sed script.
#
# Will only work if output is redirected to a file (which should be the case
# in all automated cases), but not when the user is calling grub2-mkconfig by
# hand without redirection.

cfgfile="`readlink /proc/$$/fd/1`"
if [ -f "$cfgfile" ]; then
  lines_to_add='\n'
  lines_to_add+='\thealth_checker_flag=1\n'
  lines_to_add+='\tif [ "${env_block}" ] ; then\n'
  lines_to_add+='\t\tsave_env -f "${env_block}" health_checker_flag\n'
  lines_to_add+='\tfi'

# The cp expression below will copy the new contents into the opened file;
  # the original process would not notice that and will continue writing from
  # the last position. To avoid that add the append flag to stdout to make sure
  # every write operation appends to the file.
  dd oflag=append count=0 status=none

sed 's/^$menuentry .*$/\1'"${lines_to_add}"'/' "$cfgfile" > "$cfgfile".health_checker
  cp "$cfgfile".health_checker "$cfgfile"
  rm "$cfgfile".health_checker
fi

cat << EOF
# Prevent infinite waiting for disk if drivers in initrd are broken
extra_cmdline="\${extra_cmdline} rd.timeout=60 rd.retry=45"
EOF

0707010000000F000081A40000000000000000000000016729D084000000B1000000000000000000000000000000000000003E00000000health-checker-1.12+git20241105.2e2832f15742/grub/Makefile.am#
# Copyright (c) 2018 Ignaz Forster <iforster@suse.com>
#

modulesdir = $(sysconfdir)/grub.d

modules_SCRIPTS = 05_health_check 83_health_check_marker

EXTRA_DIST = $(SCRIPTS)
07070100000010000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003000000000health-checker-1.12+git20241105.2e2832f15742/m407070100000011000081A40000000000000000000000016729D0840000068F000000000000000000000000000000000000004700000000health-checker-1.12+git20241105.2e2832f15742/m4/jh_path_xml_catalog.m4# Checks the location of the XML Catalog
# Usage:
#   JH_PATH_XML_CATALOG([ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
# Defines XMLCATALOG and XML_CATALOG_FILE substitutions
AC_DEFUN([JH_PATH_XML_CATALOG],
[
  # check for the presence of the XML catalog
  AC_ARG_WITH([xml-catalog],
              AC_HELP_STRING([--with-xml-catalog=CATALOG],
                             [path to xml catalog to use]),,
              [with_xml_catalog=/etc/xml/catalog])
  jh_found_xmlcatalog=true
  XML_CATALOG_FILE="$with_xml_catalog"
  AC_SUBST([XML_CATALOG_FILE])
  AC_MSG_CHECKING([for XML catalog ($XML_CATALOG_FILE)])
  if test -f "$XML_CATALOG_FILE"; then
    AC_MSG_RESULT([found])
  else
    jh_found_xmlcatalog=false
    AC_MSG_RESULT([not found])
  fi

# check for the xmlcatalog program
  AC_PATH_PROG(XMLCATALOG, xmlcatalog, no)
  if test "x$XMLCATALOG" = xno; then
    jh_found_xmlcatalog=false
  fi

if $jh_found_xmlcatalog; then
    ifelse([$1],,[:],[$1])
  else
    ifelse([$2],,[AC_MSG_ERROR([could not find XML catalog])],[$2])
  fi
])

# Checks if a particular URI appears in the XML catalog
# Usage:
#   JH_CHECK_XML_CATALOG(URI, [FRIENDLY-NAME], [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
AC_DEFUN([JH_CHECK_XML_CATALOG],
[
  AC_REQUIRE([JH_PATH_XML_CATALOG],[JH_PATH_XML_CATALOG(,[:])])dnl
  AC_MSG_CHECKING([for ifelse([$2],,[$1],[$2]) in XML catalog])
  if $jh_found_xmlcatalog && \
     AC_RUN_LOG([$XMLCATALOG --noout "$XML_CATALOG_FILE" "$1" >&2]); then
    AC_MSG_RESULT([found])
    ifelse([$3],,,[$3
])dnl
  else
    AC_MSG_RESULT([not found])
    ifelse([$4],,
       [AC_MSG_ERROR([could not find ifelse([$2],,[$1],[$2]) in XML catalog])],
       [$4])
  fi
])
07070100000012000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003100000000health-checker-1.12+git20241105.2e2832f15742/man07070100000013000081A40000000000000000000000016729D084000002C7000000000000000000000000000000000000003D00000000health-checker-1.12+git20241105.2e2832f15742/man/Makefile.am#
# Copyright (c) 2017 Thorsten Kukuk, Germany
#
# Author: Thorsten Kukuk <kukuk@suse.de>
#

plugindir = ${libexecdir}/health-checker

CLEANFILES = $(MANS) $(DATA) health-checker.index.xml

EXTRA_DIST = $(MANS) $(DATA) health-checker.8.xml.in

man_MANS = health-checker.8 health-checker.service.8

XMLS = health-checker.8.xml

if ENABLE_REGENERATE_MAN
health-checker.8.xml: health-checker.8.xml.in
	sed 's|@PLUGINDIR@|${plugindir}|g' $(srcdir)/health-checker.8.xml.in > health-checker.8.xml

health-checker.service.8: health-checker.8

health-checker.8: health-checker.8.xml
	$(XSLTPROC) -o $@ --path $(srcdir) --xinclude --nonet http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl $<
endif
07070100000014000081A40000000000000000000000016729D08400000FCD000000000000000000000000000000000000004900000000health-checker-1.12+git20241105.2e2832f15742/man/health-checker.8.xml.in<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">

<refentry id='health-checker.8'>
  <refentryinfo>
    <title>health-checker</title>
    <productname>health-checker</productname>

<authorgroup>
      <author>
        <contrib></contrib>
        <firstname>Thorsten</firstname>
        <surname>Kukuk</surname>
        <email>kukuk@suse.de</email>
      </author>
    </authorgroup>
  </refentryinfo>

<refmeta>
    <refentrytitle>health-checker</refentrytitle>
    <manvolnum>8</manvolnum>
    <refmiscinfo class='setdesc'>health-checker</refmiscinfo>
  </refmeta>

<refnamediv id='name'>
    <refname>health-checker</refname>
    <refname>health-checker.service</refname>
    <refpurpose>Checks that all important services of a system did come up
    correctly after an update and reboot.</refpurpose>
  </refnamediv>

<refsynopsisdiv id='synopsis'>
    <cmdsynopsis>
      <command>/usr/sbin/health-checker</command>
    </cmdsynopsis>
    <cmdsynopsis>
      <command>/usr/sbin/health-checker</command>
      <arg choice='plain'>--version </arg>
    </cmdsynopsis>
    <para><filename>health-checker.service</filename></para>
  </refsynopsisdiv>

<refsect1 id='description'><title>DESCRIPTION</title>
  <para><emphasis remap='B'>health-checker</emphasis>
  checks if the system is coming up correctly during boot up.
  In case of an error, the remediation action depends on what happened before.
  If this is the first boot after a transactional update, an automatic rollback
  to the last known working snapshot is executed. If the snapshot was already
  rebooted successfully before, a reboot is tried. If this does not help,
  some sevices are shutdown and an admin has to repair the system.
  </para>
  <para>
    If the boot was successful, the current snapshot is marked as known to be
    working.
  </para>
  <para>Plugins are used for performing the tests and new plugins can be
  written. They are stored in the <filename>@PLUGINDIR@</filename>
  or /usr/local/libexec/health-checker (individual user plugins) directory
  and are executed either with the option <command>check</command> or
  <command>stop</command>.
  If called with "check", the plugin should verify that the service works and
  return 0, else 1. If one plugin returns "1", <command>health-check</command>
  will evaluate what to do. If neither a rollback or reboot is usefull, all
  plugins will be called with the "stop" option. In this case, the plugins
should shutdown the services are far as possible and usefull.
  </para>
  </refsect1>

<refsect1 id='telemetry'><title>TELEMETRY</title>
  <para>
    If <citerefentry><refentrytitle>telem-record-gen</refentrytitle><manvolnum>1</manvolnum></citerefentry>
    is installed telemetry events are created additional to logging with
    <citerefentry><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
  </para>
  </refsect1>

<refsect1 id='see_also'><title>SEE ALSO</title>
  <para><citerefentry><refentrytitle>transactional-update</refentrytitle><manvolnum>8</manvolnum></citerefentry>
  </para>
  </refsect1>

</refentry>
07070100000015000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003500000000health-checker-1.12+git20241105.2e2832f15742/plugins07070100000016000081A40000000000000000000000016729D08400000116000000000000000000000000000000000000004100000000health-checker-1.12+git20241105.2e2832f15742/plugins/Makefile.am#
# Copyright (c) 2017 Thorsten Kukuk <kukuk@suse.de>
#

plugindir = ${libexecdir}/health-checker

plugin_SCRIPTS = health-check-tester.sh etc-overlayfs.sh \
	rebootmgr.sh btrfs-subvolumes-mounted.sh \
	tmp.sh logind.sh rpmdb-consistency.sh

EXTRA_DIST = template.sh ${SCRIPTS}
07070100000017000081ED0000000000000000000000016729D084000001D4000000000000000000000000000000000000005100000000health-checker-1.12+git20241105.2e2832f15742/plugins/btrfs-subvolumes-mounted.sh#!/bin/bash

run_checks() {
    MOUNTS=$(findmnt --types btrfs --options subvol --fstab --output target --raw --noheadings)
    for i in ${MOUNTS}; do
        path=$(systemd-escape -p -- "$(echo -e ${i})")
        systemctl is-failed -q -- "${path}.mount"
        test $? -ne 1 && exit 1
    done
}

stop_services() {
    echo -n ""
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	stop_services
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
07070100000018000081ED0000000000000000000000016729D08400000163000000000000000000000000000000000000004600000000health-checker-1.12+git20241105.2e2832f15742/plugins/etc-overlayfs.sh#!/bin/bash

# Check if the overlay filesystem for /etc is working correctly

run_checks() {
    systemctl is-failed etc.mount
    test $? -ne 1 && exit 1

TMPF=$(mktemp -q /etc/test-for-read-write.XXXXXX) || exit 1
    rm ${TMPF}
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
07070100000019000081ED0000000000000000000000016729D084000001B1000000000000000000000000000000000000004C00000000health-checker-1.12+git20241105.2e2832f15742/plugins/health-check-tester.sh#!/bin/bash

#
# plugin to test basic functionality of MicroOS health checker
#

run_checks() {

# Simple check: if this is the very first boot, succeed.
# If not, fail.
   if [ -f /var/lib/misc/health-check.state ]; then
       exit 1
   else
       return 0
   fi
}

stop_services() {
    exit 1
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	stop_services
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
0707010000001A000081ED0000000000000000000000016729D08400000168000000000000000000000000000000000000003F00000000health-checker-1.12+git20241105.2e2832f15742/plugins/logind.sh#!/bin/bash

run_checks() {
    systemctl is-enabled -q systemd-logind
    test $? -ne 0 && return

systemctl is-failed -q systemd-logind
    test $? -ne 1 && exit 1
}

stop_services() {
    systemctl stop systemd-logind
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	stop_services
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
0707010000001B000081ED0000000000000000000000016729D084000001BE000000000000000000000000000000000000004200000000health-checker-1.12+git20241105.2e2832f15742/plugins/rebootmgr.sh#!/bin/bash

run_checks() {
    # ignore if rebootmgr is not enabled.
    systemctl is-enabled -q rebootmgr
    test $? -ne 0 && return

systemctl is-failed -q rebootmgr
    test $? -ne 1 && exit 1

rebootmgrctl is-active -q
    test $? -ne 0 && exit 1
}

stop_services() {
    systemctl stop rebootmgr
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	stop_services
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
0707010000001C000081ED0000000000000000000000016729D0840000011F000000000000000000000000000000000000004A00000000health-checker-1.12+git20241105.2e2832f15742/plugins/rpmdb-consistency.sh#!/bin/bash

run_checks() {
	# check rpm DB itself (need to override lock path, the default one is read-only)
	rpm -D "%_rpmlock_path /run/rpmdb" --verifydb || exit 1
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
0707010000001D000081ED0000000000000000000000016729D084000000B8000000000000000000000000000000000000004100000000health-checker-1.12+git20241105.2e2832f15742/plugins/template.sh#!/bin/bash

run_checks() {
}

stop_services() {
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	stop_services
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
0707010000001E000081ED0000000000000000000000016729D0840000014C000000000000000000000000000000000000003C00000000health-checker-1.12+git20241105.2e2832f15742/plugins/tmp.sh#!/bin/bash

# Check if tmp is mounted and writable
run_checks() {
    systemctl is-failed -q tmp.mount
    test $? -ne 1 && exit 1

TMPF=$(mktemp -q /tmp/test-for-read-write.XXXXXX) || exit 1
    rm ${TMPF}
}

case "$1" in
    check)
	run_checks
	;;
    stop)
	;;
    *)
	echo "Usage: $0 {check|stop}"
	exit 1
	;;
esac

exit 0
0707010000001F000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003200000000health-checker-1.12+git20241105.2e2832f15742/sbin07070100000020000081A40000000000000000000000016729D0840000014A000000000000000000000000000000000000003E00000000health-checker-1.12+git20241105.2e2832f15742/sbin/Makefile.am#
# Copyright (c) 2017 Thorsten Kukuk <kukuk@suse.de>
#

sbin_SCRIPTS = health-checker
CLEANFILES = $(sbin_SCRIPTS)
EXTRA_DIST = health-checker.in

plugindir = ${libexecdir}/health-checker

health-checker: health-checker.in
	sed 's|@PLUGINDIR@|${plugindir}|g' $(srcdir)/health-checker.in > health-checker
	chmod +x health-checker
07070100000021000081ED0000000000000000000000016729D08400001149000000000000000000000000000000000000004400000000health-checker-1.12+git20241105.2e2832f15742/sbin/health-checker.in#!/bin/bash

#
# Check health state of the system
#
# Check whether important services are started and running. If this is not the
# case:
# - on first boot after update, rollback to old snapshot
# - if it is not the first boot, reboot
# - if reboot does not help, stop system before further damage is done
#

STATE_FILE=/var/lib/misc/health-check.state
REBOOTED_STATE=/var/lib/misc/health-check.rebooted
PLUGINDIR=@PLUGINDIR@
USR_LOCAL_PLUGINDIR=/usr/local/libexec/health-checker
TELEM_SEVERITY=1
TELEM_PAYLOAD=""

BTRFS_ID_DEFAULT=0
SNAPSHOT_DEFAULT=""
BTRFS_ID_CURRENT=0

set_btrfs_id()
{
    BTRFS_ID_DEFAULT=`btrfs subvolume get-default / | awk '{print $2}'`
    SNAPSHOT_DEFAULT="`btrfs subvolume get-default / | cut -d ' ' -f 9-`"
    BTRFS_ID_CURRENT=`findmnt --output OPTIONS --noheadings / | sed -e 's|.*subvolid=$[0-9]\+$.*|\1|g'`
}

create_log()
{
    local SEVERITY=1

logger -s -p $1 $2

# Create severity and payload for telemetrics if available
    case $1 in
	user.emerg)
	    SEVERITY=4
	    ;;
	user.crit)
	    SEVERITY=3
	    ;;
	user.alert)
	    SEVERITY=2
	    ;;
	*)
	    SEVERITY=1
	    ;;
    esac

if [ $SEVERITY -gt $TELEM_SEVERITY ]; then
	TELEM_SEVERITY=$SEVERITY
    fi
    if [ -z "${TELEM_PAYLOAD}" ]; then
	TELEM_PAYLOAD=$2
    else
	TELEM_PAYLOAD="${TELEM_PAYLOAD}\n$2"
    fi
}

telem_send_record()
{
    # Log via telemetrics if available
    if [ -x /usr/bin/telem-record-gen ]; then
        echo -e "${TELEM_PAYLOAD}" | /usr/bin/telem-record-gen -s $TELEM_SEVERITY -c "org.opensuse/health/boot"
	# Communication is async, give daemon time to send data
	# before reboot
	test "$1" = "1" && sleep 2
    fi
}

save_working_snapshot()
{
    set_btrfs_id

if [ ${BTRFS_ID_DEFAULT} -eq ${BTRFS_ID_CURRENT} ]; then
	echo "LAST_WORKING_BTRFS_ID=${BTRFS_ID_DEFAULT}" > $STATE_FILE
	echo "LAST_WORKING_SNAPSHOT=${SNAPSHOT_DEFAULT}" >> $STATE_FILE
    fi
}

rollback()
{
    . ${STATE_FILE}
    mount -o remount,rw /.snapshots
    btrfs subvolume set-default ${LAST_WORKING_BTRFS_ID} /.snapshots
    if [ $? -ne 0 ]; then
        create_log user.crit "ERROR: btrfs set-default $BTRFS_ID_DEFAULT failed!"
	telem_send_payload 1
        exit 1
    fi
}

stop_services()
{
    # Stop all services
    for script in ${PLUGINDIR}/* ${USR_LOCAL_PLUGINDIR}/*; do
        if [ -f ${script} ]; then
            ${script} stop
        fi
    done
}

error_decission()
{
    if [ ! -f ${STATE_FILE} ]; then
	# No state file, no successful boot
	create_log user.emerg "Machine didn't come up correctly, stopping services"
	stop_services
	return
    fi

. ${STATE_FILE}

set_btrfs_id

if [ ${BTRFS_ID_DEFAULT} -ne ${BTRFS_ID_CURRENT} ]; then
      # Don't tamper with system if not booted into default snapshot
      create_log user.alert "Machine didn't come up correctly, trying rebooting into default snapshot"
      systemctl reboot
  elif [ ${LAST_WORKING_BTRFS_ID} -ne ${BTRFS_ID_DEFAULT} ]; then
      create_log user.alert "Machine didn't come up correctly, do a rollback"
      rollback
      if [ $? -eq 0 ]; then
	  telem_send_record 1
	  systemctl reboot
      fi
  elif [ ! -f ${REBOOTED_STATE} ]; then
      create_log user.crit "Machine didn't come up correctly, trying a reboot"
      echo `date "+%Y-%m-%d %H:%M"` > ${REBOOTED_STATE}
      telem_send_record 1
      systemctl reboot
  else
      create_log user.emerg "Machine didn't come up correctly, starting emergency shell"
      stop_services
      systemctl start emergency.target
  fi
}

# Clear GRUB flag (used to determine if system was able to boot at all)
echo "Clearing GRUB flag"
grub2-editenv - set health_checker_flag=0

echo "Starting health check"
FAILED=0;
for script in ${PLUGINDIR}/* ${USR_LOCAL_PLUGINDIR}/* ; do
   if [ -f ${script} ]; then
       ${script} check
       if [ $? -ne 0 ]; then
           create_log user.crit "ERROR: \"${script} check\" failed"
           FAILED=1
       fi
   fi
done

if [ ${FAILED} -ne 0 ]; then
    echo "Health check failed!"
    error_decission
    telem_send_record 0
    exit 1
else
    echo "Health check passed"
    # Save good working state and remove old rebooted state file
    save_working_snapshot
    if [ -f ${REBOOTED_STATE} ]; then
        create_log user.info "Health check passed after reboot"
        rm -rf ${REBOOTED_STATE}
    fi
fi

if [ -z "${TELEM_PAYLOAD}" ]; then
    TELEM_PAYLOAD="Health check passed"
fi
telem_send_record 0
exit 0
07070100000022000041ED0000000000000000000000026729D08400000000000000000000000000000000000000000000003500000000health-checker-1.12+git20241105.2e2832f15742/systemd07070100000023000081A40000000000000000000000016729D0840000009C000000000000000000000000000000000000004100000000health-checker-1.12+git20241105.2e2832f15742/systemd/Makefile.am#
# Copyright (c) 2016 Thorsten Kukuk <kukuk@suse.de>
#

systemddir = $(systemdsystemunitdir)

systemd_DATA = health-checker.service

EXTRA_DIST = $(DATA)
07070100000024000081A40000000000000000000000016729D0840000013D000000000000000000000000000000000000004C00000000health-checker-1.12+git20241105.2e2832f15742/systemd/health-checker.service[Unit]
Description=MicroOS Health Checker
After=cloud-final.service
After=crio.service
After=etcd.service
After=kubelet.service
After=rebootmgr.service
After=systemd-logind.service
Wants=local-fs.target

[Service]
Type=oneshot
ExecStart=/usr/sbin/health-checker
RemainAfterExit=yes

[Install]
WantedBy=default.target
07070100000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000B00000000TRAILER!!!137 blocks

Places

File health-checker-1.12+git20241105.2e2832f15742.obscpio of Package health-checker (Revision 28265b1fc829241a6dd252d4aff1ec55)

Places