---
name: "st_snapshot.hourly"
section: "1"
platform: "linux"
package: "systraq"
version: "20201231-5"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/st_snapshot.hourly"
---

# st\_snapshot.hourly(1)

wrapper for st\_snapshot

## NAME

st\_snapshot.hourly - wrapper for st\_snapshot

## SYNOPSIS

**st\_snapshot.hourly**

## DESCRIPTION

**st\_snapshot.hourly** is a wrapper for **st\_snapshot**. **st\_snapshot.hourly** is to be run from cron.

It checks existence of the files /etc/systraq/i\_want\_a\_broken\_systraq and /etc/systraq/systraq\_is\_unconfigured . The file i\_want\_a\_broken\_systraq typically is empty; if it exists, **st\_snapshot.hourly** exits immediately. Existence of this file "breaks" systraq: systraq will no longer warn when system configuration files changes, but will remain silent. If systraq\_is\_unconfigured exists, its contents are displayed and **st\_snapshot.hourly** exits. The file systraq\_is\_unconfigured typically holds instructions on how to configure systraq, an example systraq\_is\_unconfigured file is shipped with the systraq tarball. If both files are missing, **st\_snapshot** is called with appropriate arguments, either in "root" or in "public"-mode, depending on the ST\_MODE environment variable.

Since the systraq tarball behaves sanely on a fresh default install, systraq\_is\_unconfigured is *not* installed by default. However, people preparing systraq binary packages typically can make good use of this file.

When systraq is installed from tarball the systraq cronjobs are not enabled. One typically enables them *after* having configured systraq, especially after the **st\_snapshot** listfiles snapshot\_pub.list, snapshot\_pub.homelist, snapshot\_root.list and snapshot\_root.homelist in /etc/systraq are created. However, binary systraq packages typically enable the cronjobs without enforcing one-fits-all listfiles on the user.

## ENVIRONMENT

ST\_MODE

If set to "root", run st\_snapshot in root-mode.

ST\_SUM

Command for calculating file checksums. E.g. sha256sum, sha512sum, sha384sum, sha224sum or sha1sum. If unset, sha256sum is used. If unset and sha256sum is not found on the system while md5sum is found, md5sum is used and a warning is printed. Else, the script prints an error message and exits. ST\_SUM is passed to and used by st\_snapshot.

## FILES

/etc/systraq/i\_want\_a\_broken\_systraq, /etc/systraq/systraq\_is\_unconfigured.

## SEE ALSO

st\_snapshot (1), The systraq Manual.

## VERSION

20201231

## AUTHOR

**Joost van Baal-Ilić** \<joostvb-systraq-20151105@mdcc.cx\>

Author.

## COPYRIGHT

Copyright © 2001-2020 Joost van Baal-Ilić\

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation.