replaced all ${stamp} with [$(stamp)]

LICENSE

@@ -0,0 +1,126 @@
+GNU GENERAL PUBLIC LICENSE
+Version 3, 29 June 2007
+Copyright © 2007 Free Software Foundation, Inc. <http s ://fsf.org/>
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+Preamble
+The GNU General Public License is a free, copyleft license for software and other kinds of works.
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. 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 them 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 prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
+For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. 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.
+Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
+For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
+Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
+Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
+The precise terms and conditions for copying, distribution and modification follow.
+TERMS AND CONDITIONS
+   0. Definitions.
+   "This License" refers to version 3 of the GNU General Public License.
+   "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+   "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.
+   To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+   A "covered work" means either the unmodified Program or a work based on the Program.
+   To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+   To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+   An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+   1. Source Code.
+   The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.
+   A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+   The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+   The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
+   The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+   The Corresponding Source for a work in source code form is that same work.
+   2. Basic Permissions.
+   All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+   You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+   Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+   3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+   No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+   When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+   4. Conveying Verbatim Copies.
+   You may convey 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; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+   You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+   5. Conveying Modified Source Versions.
+   You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+      a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+      b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".
+      c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+      d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+   A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+   6. Conveying Non-Source Forms.
+   You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+      a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+      b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+      c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+      d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+      e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+   A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+   A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+   "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+   If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+   The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+   Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+   7. Additional Terms.
+   "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+   When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+   Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+      a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+      b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+      c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+      d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+      e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+      f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+   All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+   If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+   Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+   8. Termination.
+   You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+   However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+   Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+   Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+   9. Acceptance Not Required for Having Copies.
+   You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+   10. Automatic Licensing of Downstream Recipients.
+   Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
+   An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+   You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+   11. Patents.
+   A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".
+   A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+   Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+   In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+   If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+   If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+   A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+   Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+   12. No Surrender of Others' Freedom.
+   If 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 convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+   13. Use with the GNU Affero General Public License.
+   Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
+   14. Revised Versions of this License.
+   The Free Software Foundation may publish revised and/or new versions of the GNU 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 that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
+   If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+   Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+   15. Disclaimer of Warranty.
+   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.
+   16. Limitation of Liability.
+   IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 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.
+   17. Interpretation of Sections 15 and 16.
+   If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. 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 state 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) <year> <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 3 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, see <http s ://www.gnu.org/licenses/>.
+Also add information on how to contact you by electronic and paper mail.
+If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
+<program> Copyright (C) <year> <name of author>
+This program 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, your program's commands might be different; for a GUI interface, you would use an "about box".
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http s ://www.gnu.org/licenses/>.
+The GNU 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. But first, please read <http s ://www.gnu.org/philosophy/why-not-lgpl.html>.

README.md

@@ -1,2 +1,540 @@
-# nextcloud13
+# NextCloud Backup Using borgbackup <!-- omit in toc -->
 
+This script automates backing up your NextCloud installation using borgbackup
+and a remote ssh-capable storage system.  I suggest using rsync.net since they
+have great speeds and a special pricing structure for borgbackup/attic users
+([details here](https://www.rsync.net/products/attic.html)).
+
+This script automates the following tasks:
+
+- Optionally copies a 503 error page to your webserver so users know when your
+  server is unavailable due to backups being performed. The 503 file is removed
+  when the backup is completed so users can login again
+- Dumps the NextCloud mySQL database and adds it to the backup
+- Handles entering and exiting NextCloud's maintenance mode to 'lock' accounts
+  so changes are not made during the backup process
+- Allows you to specify additional files you want backed up
+- Allows you to specify files/directories to exclude from your backups (e.g.
+  previews)
+- Runs 'borg prune' to make sure you are trimming old backups on your schedule
+- Creates a clear, easy to parse log file so you can keep an eye on your backups
+  and any errors/warnings
+
+## Contents <!-- omit in toc -->
+- [Installation/copying](#installationcopying)
+- [Environment notes](#environment-notes)
+- [Why this script must be run as root](#why-this-script-must-be-run-as-root)
+- [Script parameters](#script-parameters)
+    - [Required parameters](#required-parameters)
+        - [NextCloud data directory: -d _/path/to/data/_](#nextcloud-data-directory--d-_pathtodata_)
+        - [NextCloud webroot: -n _/path/to/nextcloud/_](#nextcloud-webroot--n-_pathtonextcloud_)
+        - [webuser account: -w _accountName_](#webuser-account--w-_accountname_)
+    - [Optional parameters](#optional-parameters)
+        - [Path to 503 error page: -5 _/path/to/filename.html_](#path-to-503-error-page--5-_pathtofilenamehtml_)
+        - [Path to borg details file: -b _/path/to/filename.file_](#path-to-borg-details-file--b-_pathtofilenamefile_)
+        - [Desired log file location: -l _/path/to/filename.file_](#desired-log-file-location--l-_pathtofilenamefile_)
+        - [Path to SQL details file: -s _/path/to/filename.file_](#path-to-sql-details-file--s-_pathtofilenamefile_)
+        - [Verbose output from borg: -v (no arguments)](#verbose-output-from-borg--v-no-arguments)
+        - [Path to webroot: -w _/path/to/webroot/_](#path-to-webroot--w-_pathtowebroot_)
+- [Borg details file](#borg-details-file)
+    - [Protect your borg details file](#protect-your-borg-details-file)
+    - [borg specific entries (lines 1-4)](#borg-specific-entries-lines-1-4)
+    - [additional files/directories to backup](#additional-filesdirectories-to-backup)
+    - [exclusion patterns](#exclusion-patterns)
+    - [prune timeframe options](#prune-timeframe-options)
+    - [borg remote location](#borg-remote-location)
+    - [Examples](#examples)
+- [SQL details file](#sql-details-file)
+    - [Protect your sql details file](#protect-your-sql-details-file)
+- [503 functionality](#503-functionality)
+    - [Conditional forwarding by your webserver](#conditional-forwarding-by-your-webserver)
+        - [NGINX](#nginx)
+        - [Apache](#apache)
+        - [Disabling 503 functionality altogether](#disabling-503-functionality-altogether)
+- [Scheduling: Cron](#scheduling-cron)
+- [The log file](#the-log-file)
+    - [Using Logwatch](#using-logwatch)
+    - [Remember to rotate your logs](#remember-to-rotate-your-logs)
+- [Final notes](#final-notes)
+
+## Installation/copying
+
+Once you've either cloned this git or downloaded the release file, simply copy
+the *'NCscripts'* folder to wherever you like.  I suggest putting it in your
+*'/root'* directory since the root user must execute the script.  If you edit
+the 503.html, nc_borg.details and nc_sql.details files in place, then you don't
+have to specify their locations when running the script.
+
+Remember to make the script executable!
+
+```Bash
+chmod +x backup.sh
+```
+
+In addition, you can rename the script file to anything you like.  The log file
+will use that same name by default when naming itself and any mention of this
+file in the logs will automatically use whatever name you choose to give it.
+
+## Environment notes
+
+The script is designed to be easy to use but still be flexible enough to
+accommodate a wide range of NextCloud setups.  I have tested it with NextCloud
+13 and 14 using a standard LEMP setup (Debian Stretch, NGINX, mariaDB & PHP7).
+The script accepts several parameters to provide it with the settings it
+requires to function.  In addition, it reads external plain-text files for SQL
+and borg settings so you don't have to weed through the script code to supply
+things like passwords.
+
+## Why this script must be run as root
+
+This script must be run by the root user and will exit with an error if you try
+running it otherwise.  This is because NextCloud's OCC command (needed to put
+NextCloud into maintenance mode) must be run as the web-user account and only
+the root account can switch users without needing to stop and ask for
+permission/passwords.
+
+## Script parameters
+
+You can run the script with the *'-?'* parameter to access the built-in help
+which explains the parameters.  However, the following is a more detailed
+explanation of each parameter and how to use them.
+**Note that any parameters needing a directory (webroot, nextcloud root, etc.)
+can be entered with or without the trailing '/' since it's stripped by the script
+anyways.**
+
+General usage:
+
+```Bash
+/path/to/script/scriptname.sh -parameter argument -parameter argument ...
+```
+
+### Required parameters
+
+#### NextCloud data directory: -d _/path/to/data/_
+
+This is the full path to the location where NextCloud actually stores data.  In
+a setup such as I recommend on my blog at
+[https://mytechiethoughts.com](https://www.mytechiethoughts.com), you would be
+using an entry such as *'/var/nc_data'*.  This directory and all subdirectories
+are automatically included in the backup.
+
+#### NextCloud webroot: -n _/path/to/nextcloud/_
+
+This is the directory in which NextCloud's php and html files are located.  It
+is generally somewhere under your webroot directory.  This is required so the
+script can find the 'OCC' command to invoke maintenance mode.
+
+#### webuser account: -w _accountName_
+
+This is the account that NextCloud runs under via your webserver.  This is
+almost always *'www-data'*.  You would have to check your NGINX/Apache config to
+be sure.  'OCC' will not run as any other user thus, the script cannot
+enter/exit maintenance mode without knowing which user to emulate.
+
+### Optional parameters
+
+#### Path to 503 error page: -5 _/path/to/filename.html_
+
+The path to an html file for the script to copy to your webroot during the
+backup process.  This file can be scanned by your webserver and a 503 error can
+be issued to users letting them know that your NextCloud is 'temporarily
+unavailable' while being backed up.  A sample 503 page is included for you.
+
+If you remove the default file or the one you specify is missing, a warning will
+be issued by the script but, it will continue executing.  More details on the
+503 notification can be found later in the [503 functionality](#503-functionality) section of this
+document.\
+**Default: _scriptpath/503.html_**
+
+#### Path to borg details file: -b _/path/to/filename.file_
+
+This is a text file that lays out various borg options such as repo name,
+password, additional files to include, exclusion patters, etc.  A sample file is
+included for your reference.  More details, including the *required order* of
+entries can be found later in this document in the [borg details file](#borg-details-file)
+section.\
+**Default: _scriptpath/nc_borg.details_**
+
+#### Desired log file location: -l _/path/to/filename.file_
+
+If you have a particular place and filename you'd like this script to use for
+it's log, then you can specify it using this parameter.  I would recommend
+*'/var/log/backup.log'*. By default, the script will name the log file
+*scriptname*.log and will save it in the same directory as the script itself.\
+**Default: _scriptpath/scriptname.log_**
+
+#### Path to SQL details file: -s _/path/to/filename.file_
+
+This is a text file containing the details needed to connect to NextCloud's SQL
+database.  More information about the *required order* of entries can be found
+later in this document in the [sql details file](#sql-details-file) section.\
+**Default: _scriptpath/nc_sql.details_**
+
+#### Verbose output from borg: -v (no arguments)
+
+By default, the script will ask borg to generate summary only output and record
+that in the script's log file.  If you are running the backup for the first time
+or are troubleshooting, you may want a detailed output of all files and their
+changed/unchanged/excluded status from borg.  In that case, specify the -v
+switch. **Note: This will make your log file very large very quickly since EVERY
+file being backed up is written to the log.**
+
+#### Path to webroot: -w _/path/to/webroot/_
+
+This is the path to the directory your webserver is using as it's default root.
+In other words, this is the directory that contains the html files served when
+someone browses to your server.  Depending on your setup, this might be the same
+as your NextCloud webroot.
+
+This is used exclusively for 503 functionality since the script has to know
+where to copy the 503 file.  If you don't want to use this functionality, you
+can omit this parameter and the script will issue a warning and move on.  More
+details can be found in the [503 functionality](#503-functionality) section later in this
+document.
+
+## Borg details file
+
+This file contains all the data needed to access your borg remote data repo.
+Each line must contain specific information in a specific order or *needs to be
+blank if that data is not required*.  The sample file includes this data and
+example entries.  The file must have the following information in the following
+order:
+
+    1. path to borg base directory **(required)**
+    2. path to ssh private key for repo **(required)**
+    3. connection string to remote repo **(required)**
+    4. password for ssh key/repo **(required)**
+    5. path to file listing additional files/directories to backup
+    6. path to file containing borg-specific exclusion patterns
+    7. prune timeframe options
+    8. location of borg remote instance
+
+### Protect your borg details file
+
+This file contains information on how to access and decrypt your borg repo,
+therefore, you **must** protect it.  You should lock it out for everyone but
+your root user. Putting it in your root folder is not enough!  Run the following
+commands to restrict access to the root user only (assuming filename is
+*'nc_borg.details'*):
+
+```Bash
+chown root:root nc_borg.details   # make root the owner
+chmod 600 nc_borg.details   # restrict access to root only (read/write)
+```
+
+### borg specific entries (lines 1-4)
+
+If you need help with these options, then you should consult the borg
+documentation or search my blog at
+[https://mytechiethoughts.com](https://mytechiethoughts.com) for borg. This is
+especially true if you want to understand why an SSH key and passphrase are
+preferred and why just a passphrase on it's own presents problems automating
+borg backups.
+
+### additional files/directories to backup
+
+This points to a plain-text file listing additional files and directories you'd
+like borg to include in the backup.  The sample file, *'xtraLocations.borg'*
+contains the most likely files you'd want to include assuming you're using a
+standard setup like it outline in my blog.
+
+The following would include all files in the home folder for users *'foo'* and
+*'bar'* and any conf files in *'/etc/someProgram'*:
+
+```Bash
+/home/foo/
+/home/bar/
+/etc/someProgram/*.conf
+```
+
+You can leave this line blank to tell borg to only backup your NextCloud data
+directory and the SQL dump.  However, this is pretty unusual since you would not
+be including any configuration files, webserver configurations, etc.  If you
+omit this line, the script will log a warning to remind you of this unusual
+situation.
+
+### exclusion patterns
+
+This points to a plain-text file containing borg-specific patterns describing
+what files you'd like borg to ignore during the backup.  The sample file,
+*'excludeLocations.borg'* contains a list of directories to exclude assuming a
+standard NextCloud install -- the previews directory and the cache directory.
+You need to run *'borg help patterns'* for help on how to specify any additional
+exclusion patterns since the format is not standard BASH format and only
+sometimes uses standard regex.
+
+If you leave this line blank, the script will note it is not processing any
+exclusions and will proceed with backing up all files specified.
+
+### prune timeframe options
+
+Here you can let borg prune know how you want to manage your backup history.
+Consult the borg documentation and then copy the relevant options directly into
+this line including any spaces, etc.  The example file contains the following as
+a staring point:
+
+```Ini
+--keep-within=7d --keep-daily=30 --keep-weekly=12 --keep-monthly=-1
+```
+
+This would tell borg prune to keep ALL backups made for any reason within the
+last 7 days, keep 30 days worth of daily backups, 12 weeks of end-of-week
+backups and then an infinite amount of end-of-month backups.
+
+### borg remote location
+
+If you're using rsync, then just have this say *'borg1'*.  If you are using
+another provider, you'll have to reference their locally installed copy of borg
+relative to your home directory.  You can also leave this blank if your provider
+does not run borg locally but your backups/restores will be slower.
+
+### Examples
+
+Repo in directory *'NCBackup'*, all fields including pointers to additional
+files to backup, exclusion patterns and a remote borg path.  Prune: keep all
+backups made in the last 14 days.
+
+```Ini
+/var/borgbackup
+/var/borgbackup/SSHprivate.key
+myuser@usw-s001.rsync.net:NCBackup/
+myPaSsWoRd
+/root/NCscripts/xtraLocations.borg
+/root/NCscripts/excludeLocations.borg
+--keep-within=14d
+borg1
+```
+
+Repo in directory *'myBackup'*, no exclusions, keep 14 days end-of-day, 52 weeks
+end-of-week
+
+```Ini
+/var/borgbackup
+/root/keys/rsyncPrivate.key
+myuser@usw-s001.rsync.net:myBackup/
+PaSsWoRd
+/var/borgbackup/include.list
+
+--keep-daily=14 --keep-weekly=52
+borg1
+```
+
+Repo in directory *'backup'*, no extra file locations, no exclusions, no remote
+borg installation. Keep last 30 backups.
+
+```Ini
+/root/.borg
+/root/.borg/private.key
+username@server.tld:backup/
+pAsSw0rD
+
+
+--keep-within=30d
+
+```
+
+**Notice that the blank lines are very important!**
+
+## SQL details file
+
+This file contains all the information needed to access your NextCloud SQL
+database in order to dump it's contents into a file that can be easily
+backed-up. Each line must contain specific information in a specific order.  The
+sample file includes this data and example entries.  The file must have the
+following information in the following order (**all entries required**):
+
+    1. name of machine hosting mySQL (usually localhost)
+    2. name of authorized user
+    3. password for above user
+    4. name of NextCloud database
+
+For example:
+
+```Ini
+localhost
+nextcloud
+pAsSwOrD
+nextcloudDB
+```
+
+### Protect your sql details file
+
+This file contains information on how to access your SQL installation therefore,
+you **must** protect it.  You should lock it out for all users except root.
+Putting it in your root folder is not enough!  Run the following commands to
+restrict access to the root user only (assuming filename is *'nc_sql.details'*):
+
+```Bash
+chown root:root nc_sql.details   # make root the owner
+chmod 600 nc_sql.details   # restrict access to root only (read/write)
+```
+
+## 503 functionality
+
+This script includes an entire section dedicated to copying an html file to act
+as an error 503 notification page.  Error 503 is by definition "service
+temporarily unavailable" which is exactly the case for your NextCloud server
+during a backup since it is in maintenance mode and no logins are permitted.
+
+The script copies whatever file is defined by the *'-5'* parameter (or the
+default located at *'scriptpath/503.html'*) to whatever path is defined as the
+'webroot' by the *'-w'* parameter.  This means that if you omit the *'-w'*
+parameter, the script will necessarily skip this entire process and just issue a
+warning to let you know about it.
+
+### Conditional forwarding by your webserver
+
+The script copying the file to the webroot is the easy part.  Your webserver has
+to look for the presence of that file and generate a 503 error in order for the
+magic to happen.  To do that, you have to include an instruction to that effect
+in your default server definition and/or your NextCloud virtual server
+definition file depending on your setup.
+
+#### NGINX
+
+You can copy the following code into the relevant server definition(s) on an
+NGINX server:
+
+```Perl
+server {
+    ...
+    if (-f /usr/share/nginx/html/503.html) {
+        return 503;
+    }
+...
+    error_page 503 @backup
+    location @backup {
+        root /usr/share/nginx/html;
+        rewrite ^(.*)$ /503.html break;
+    }
+}
+```
+
+This tells NGINX that if it finds the file *'503.html'* at the path
+*'/usr/share/nginx/html'* (webroot) then return an error code 503.  When it
+encounters an error 503, rewrite any url to *'domain.tld/503.html'* and thus,
+display the custom 503 error page.  On the other hand, if it can't find 503.html
+at the path specified (i.e. the script has deleted it because the backup is
+completed), then go about business as usual.
+
+#### Apache
+
+I don't use apache for anything, ever... so I'm not sure how exactly you'd do
+this but I think you'd have to use something like:
+
+```Perl
+RewriteEngine On
+RewriteCond %{ENV:REDIRECT_STATUS} !=503
+RewriteCond "/var/www/503.html" -f
+RewriteRule ^ - [R=503,L]
+...
+ErrorDocument 503 /503.html
+...
+```
+
+Let me know if that works and I'll update this document accordingly.  Like I
+said, I don't use Apache so I can't really test it very easily.
+
+#### Disabling 503 functionality altogether
+
+If you don't want to use the 503 functionality for whatever reason and don't
+want your log file junked up with warnings about it, then find the section of
+the script file that starts with *'--- Begin 503 section ---'* and either
+comment all the lines (put a *'#'* at the beginning of each line) or delete all
+the lines until you get to *'--- End 503 section ---'*.
+
+## Scheduling: Cron
+
+After running this script at least once manually to test your settings, you
+should schedule it to run automatically so things stay backed up.  This is
+easiest with a simple cron job.
+
+1. Open root's crontab:
+
+    ```Bash
+    sudo crontab -e
+    ```
+
+2. Add your script command line and set the time. I'm assuming your script is
+   located at *'/root/NCscripts'*, all files are at their default locations and
+   you want to run your backup at 1:07am daily.
+
+    ```Bash
+    7 1 * * * /root/NCscripts/backup.sh -d /var/nc_data -n /usr/share/nginx/html/nextcloud -u www-data -l /var/log/backup.log -w /usr/share/nginx/html > /dev/null 2>&1
+    ```
+
+    The last part redirects all output to 'null' and forwards any errors to
+    'null' also.  You don't need output because the script creates a wonderfully
+    detailed log file that you can review :-)
+3. Save the file and exit.
+4. Confirm by listing the root user's crontab:
+
+    ```Bash
+    sudo crontab -l
+    ```
+
+## The log file
+
+The script creates a very detailed log file of all major operations along with
+any errors and warnings.  Everything is timestamped so you can see how long
+things take and when any errors took place.  The script includes debugging
+notes such as where temp files are located, where it's looking for data, whether
+it created/moved/copied files, etc.  All major operations are tagged *'-- [INFO]
+message here --'*.  Similarily, warnings are tagged *'-- [WARNING] message here
+(code: xxxx) --'* and errors are tagged *'-- [ERROR] message here (code: xxx)
+--'*.  Successful operations generate a *'-- [SUCCESS] message here --'* stamp.
+
+Sections of the script are all colour-coded to make viewing it easier.  This
+means you should use something like *'cat backup.log | more'* or *'tail -n
+numberOfLines backup.log'* to view the file since the ansi colour codes
+would make it difficult to read in nano or vi.
+
+This tagging makes it easy for you to set up a log screening program to make
+keeping an eye on your backup results easier.  If you plan on using Logwatch
+(highly recommended, great program!) then I've done the work for you...
+
+### Using Logwatch
+
+Log-group, conf and service files are included so that you can easily setup
+Logwatch to monitor the script's log file and report at your desired detail
+level as follows:
+
+    1. 0: Summary of total success, warnings & errors only
+    2. 1-4: Actual success, error & warning messages
+    3. 5: Same as above, but includes info messages
+    4. 6+: Dumps entire raw log file including debugging messages
+
+A detailed breakdown of the files and all options are included in a separate
+readme in the *'/etc/logwatch'* folder of this git archive.
+
+If you don't really care how it works, then you can just copy the
+*/etc/logwatch* folder to the appropriate Logwatch configuration directory for
+your system.  The file directory layout in this git archive is already correct
+for Debian/Ubuntu systems.  You will have to update the log-group file to
+reflect the path to your script's log file.
+### Remember to rotate your logs
+
+The log file generated by this script is fairly detailed so it can grow quite
+large over time.  This is especially true if you are using verbose output from
+borg for any troubleshooting or for compliance/auditing.  I've included a sample
+commented logrotate config file in this git archive at *'/etc/logrotate.d'*
+which you can modify and drop into that same directory on your Debian/Ubuntu
+system.  If you are using another log rotating solution, then please remember to
+configure it so that your log files don't get overwhelmingly large should you
+need to parse them if something goes wrong with your backups.
+
+## Final notes
+
+I think that's everything. If I've forgotten to document something, please let
+me know. I know this readme is long but, I hate how much stuff for linux and
+open-source programs/scripts in general are so poorly documented especially for
+newbies and I didn't want to make that same mistake.
+
+I don't script too often and I'm a horrible programmer, so if you see anything
+that can be/should be improved, please let me know or submit your changes!  I
+love learning new ways of doing things and getting feedback, so suggestions and
+comments are more than welcome.
+
+If this has helped you out, then please visit my blog at
+[https://mytechiethoughts.com](https://mytechiethoughts.com) where I solve
+problems like this all the time on a shoe-string or zero budget.  Thanks!

etc/logwatch/readme.md

@@ -0,0 +1,290 @@
+# Using Logwatch to monitor backup script <!-- omit in toc -->
+
+The backup script's log file has been set up so that utilities like Logwatch can
+easily parse it.  In order to make that happen, a LogFile Group file, Service
+and Script have to be created for Logwatch to generate reports.  The correct
+(general) directory structure has been created in this git archive already.
+Below are the details of each file.
+
+## Contents <!-- omit in toc -->
+
+- [LogFile Group file (/etc/logwatch/conf/logfiles/backup.conf)](#logfile-group-file-etclogwatchconflogfilesbackupconf)
+    - [Log file location](#log-file-location)
+    - [Archive location and name format](#archive-location-and-name-format)
+    - [External script for timestamp processing](#external-script-for-timestamp-processing)
+- [Service definition file (/etc/logwatch/conf/services/backup.conf)](#service-definition-file-etclogwatchconfservicesbackupconf)
+    - [LogFile Group file definition](#logfile-group-file-definition)
+    - [Report title](#report-title)
+    - [Detail level](#detail-level)
+- [Service script (/etc/logwatch/scripts/services/backup)](#service-script-etclogwatchscriptsservicesbackup)
+    - [Detail levels](#detail-levels)
+- [Timestamp processing script (/etc/logwatch/scripts/shared/sqfullstampanywhere)](#timestamp-processing-script-etclogwatchscriptssharedsqfullstampanywhere)
+    - [The time format specification](#the-time-format-specification)
+    - [The search REGEX](#the-search-regex)
+- [Testing](#testing)
+- [Final thoughts](#final-thoughts)
+
+## LogFile Group file (/etc/logwatch/conf/logfiles/backup.conf)
+
+### Log file location
+
+Update this as needed to point to the location and name of the log file
+generated by the backup script.  Remember, by default, the log file is created
+in the same directory as the script itself.
+
+```Ini
+LogFile = /path/to/your/backup.log
+...
+```
+
+Best practices suggest you use the *-l*
+flag to change this location to something like */var/log/backup.log*, for
+example.  In that case, the entry would look like:
+
+```Ini
+LogFile = /var/log/backup.log
+...
+```
+
+### Archive location and name format
+
+If you want Logwatch to process old (archived) log files generated by something
+like *Logrotate*, then you have to specify the location and file name format of
+those files.  I've included the generalized compressed format of such rotated
+files as the default in the script.  Suppose you store your log files in the
+recommended location (*/var/log/*) and are using *Logrotate* with compression
+enabled, the archive line would look like:
+
+```Ini
+...
+Archive = /var/log/backup.log.?.gz
+...
+```
+
+This would tell Logwatch, when the archive option is set to true, that your
+*backup.log* files are archived as: *backup.log.1.gz*, *backup.log.2.gz*, etc.
+and are all located in */var/log/*.
+
+**Note: This line is totally optional and only used if you set the archive
+option in Logwatch to true (default).  You can comment/delete this line if you
+wish.**
+
+### External script for timestamp processing
+
+Since the log file uses a non-standard (according to Logwatch) method of
+datestamping, a custom filter had to be created.  See the
+[relevant](#timestamp-processing-script-etclogwatchscriptssharedsqfullstampanywhere)
+section of this document for more information.
+
+The script file is called with an *\** before the filename.
+
+```Ini
+...
+*sqFullStampAnywhere
+...
+```
+
+If you change the name of this file, you will have to change this line.
+Remember that whatever you type here as a name is converted to all-lowercase
+so your filename should be all lowercase also.
+
+## Service definition file (/etc/logwatch/conf/services/backup.conf)
+
+### LogFile Group file definition
+
+The service file needs to know what group of log files it is responsible for
+processing.  This MUST match the name of your *LogFile Group file*:
+
+```Ini
+LogFile = backup
+...
+```
+
+If you change your LogFile Group filename, then update it here too without the
+*.conf* extension.
+
+### Report title
+
+The Logwatch output file (html or text) is divided into sections.  You can
+define the title to be anything that has meaning for you.  I have arbitrarily
+chosen *"System and NextCloud Backup"* but you can change it to anything you want by
+modifying the line:
+
+```Ini
+...
+Title = "System and NextCloud Backup"
+```
+
+### Detail level
+
+If you want to set the *detail* level of this service differently from your
+other services (which will use the *--detail* switch value or the value in your
+*logwatch.conf*), then you can define that level here.  By default, it appears
+like this in the service configuration file:
+
+```Ini
+...
+# Override the detail level for this service
+# Remember the levels are: 0, 1-4, 5, 6+
+# Detail = 0
+```
+
+Simply change it to the value you want enforced.  For example, here I'm setting
+it to output level 5 regardless of whatever settings everything else is using.
+
+```Ini
+# Override the detail level for this service
+# Remember the levels are: 0, 1-4, 5, 6+
+Detail = 5
+```
+
+## Service script (/etc/logwatch/scripts/services/backup)
+
+Logwatch calls any script with a name that **matches the service name**.  You'll
+notice that I just named everything *backup* to keep things simple.  You can
+change this to whatever you want, however.  If you changed the service name to
+*"NCbackup*.conf", for example, you would have to rename this script file to
+"*NCbackup*" with no extension.  Note: The script is a PERL file (note the
+shebang) but it can be written in any language.
+
+In essence, Logwatch just spits out the log file(s) defined in the LogFile Group
+file as standard input (STDIN) for the script and then takes whatever is output
+(STDOUT) from the script to assemble into it's report.
+
+### Detail levels
+
+The script supports four (4) detail levels as follows:
+
+- **Level 0: Summary output only**
+  - This will display an aggregate total of certain logged elements.  It will
+    display the total number successful script executions (SQL dump OK, borg
+    backup OK and borg prune OK), total generated warnings and total errors
+    encountered that stopped the normal execution of the script.  All totals are
+    relative to the reporting period Logwatch is using (--range parameter).
+
+    **This is the recommended reporting level.**  It does not take up much space
+    and is quick to read.  If you notice warnings and/or errors, you should
+    consult the full logs.
+- **Levels 1-4: Critical messages**
+  - This uses the data which is summarized by Level 0 but outputs the actual
+    messages in the log file.  For example, you will see the actual text of the
+    errors logged instead of just a total number of errors.  This level of
+    reporting is useful when *initially* monitoring the script's operation since
+    you can see the actual text of any generated warnings/errors.
+- **Level 5: Verbose (debugging) output**
+  - Like the previous level, this outputs the actual messages found in the log
+    file.  However, it also includes *[INFO] tags* which contain logged
+    operational messages such as created temporary directories, entering/exiting
+    maintenance mode, what source files are being used to determine extra file
+    inclusions/exclusions, etc. This level of reporting is useful in diagnosing
+    why errors are occurring or if you just want more insight into how the
+    script works.
+
+    **This level of output will make your Logwatch reports longer and consume
+    more of your time to review. You should not use this level day-to-day.**
+- **Levels 6+: Complete log file dump**
+  - Any number greater than 5 passed as a detail level will trigger the script
+    to dump the entire log file out to Logwatch line-by-line.  This is useful
+    only if you are debugging an issue and cannot get access to the actual raw
+    log file itself.  The actual log file is colour-coded which makes it much
+    easier to read for debugging purposes.
+
+    **Use this detail level only when you need to see the entire log file and
+    cannot otherwise access the log file.**
+
+## Timestamp processing script (/etc/logwatch/scripts/shared/sqfullstampanywhere)
+
+This is basically a modified version of the '*applyeurodate*' script that comes
+with Logwatch.  It had to be modified to search within [square brackets] and to
+accept characters coming before the stamp (i.e. ANSI colour codes).  If you
+change the '**stamp**' variable in the backup script to update the timestamp to
+your liking (which to totally fine!) then you'll probably have to update this
+file.  There are two lines you need to modify to suit your new '**stamp**'
+variable.
+
+### The time format specification
+
+'*$SearchDate*' is the variable used in the PERL script to do exactly what it
+says, search for the date stamp.  I have it set up to look for the format
+'*year-month-date hour:minute:second*'.  Note, we don't care about brackets or
+anything here, we're just defining the format of the date/time stamp.
+
+```Perl
+...
+$SearchDate = TimeFilter('%Y-%m-%d %H:%M:%S');
+...
+```
+
+If you changed the '**stamp**' variable so it was formatted as '*month/day/year
+hour:minute*' (ex: '*[09/27/2018 18:38]*') then you'd update the **$SearchDate**
+variable as follows (note: no mention of the square brackets!):
+
+```Perl
+...
+$SearchDate = TimeFilter('%m/%d/%Y %H:%M');
+...
+```
+
+### The search REGEX
+
+The PERL script uses a '*regular expression*' (REGEX) to search within the log file for
+'*$SearchDate*'.  For the default datestamp, this specification looks like:
+
+```Perl
+...
+if ($ThisLine =~ m/\[$SearchDate\] /o) {
+...
+```
+
+The REGEX appears between '*m/*' and '*/o*'.  In this case, it searches for
+'*$SearchDate*' inside [square brackets] appearing anywhere on the line.  This
+is because ANSI colour-codes often appear before the datestamp in the default
+log file.  If you have modified this so that your datestamp appears at the
+beginning of the line and in the example format in the section above (using
+slashes instead of dashes) then you'd rewrite this REGEX as follows:
+
+```Perl
+...
+if ($ThisLine =~ m/^\[$SearchDate\] /o) {
+...
+```
+
+or using regular brackets anywhere on the line:
+
+```Perl
+...
+if ($ThisLine =~ m/\($SearchDate\) /o) {
+...
+```
+
+or without any brackets but appearing at the beginning of the line:
+
+```Perl
+...
+if ($ThisLine =~ m/^$SearchDate /o) {
+...
+```
+
+## Testing
+
+Run *logwatch --help* and note the options.  You can test just this service
+locally on your screen with the following command (assuming you kept default
+names for everything):
+
+```Bash
+# Summary output, entire duration of log file
+logwatch --service backup --output stdout --format text --range all --detail 0
+
+# Minimal detail, yesterday only
+logwatch --service backup --output stdout --format text --range yesterday --detail 3
+
+# Verbose output, today only
+logwatch --service backup --output stdout --format text --range today --detail 5
+```
+
+## Final thoughts
+
+That's it!  I'm a horrible PERL programmer so if anyone can optimize/improve the
+script file used for Logwatch then please do it!  Otherwise, I hope this made
+sense and helped you integrate the backup script with Logwatch for easy
+monitoring :-)

etc/logwatch/scripts/services/backup

@@ -11,7 +11,7 @@
 
 use strict;
 
-### Get Logwatch detail level
+### Get Logwatch detail level (default to 0)
 my $detailLevel = $ENV{'LOGWATCH_DETAIL_LEVEL'} || 0;
 
 

root/NCscripts/backup.sh

@@ -12,7 +12,6 @@ lit="\e[93m"
 op="\e[39m"
 info="\e[96m"
 note="\e[95m"
-stamp="[`date +%Y-%m-%d` `date +%H:%M:%S`]"
 
 
 ### Functions ###
@@ -90,6 +89,11 @@ function scriptHelp {
     exit 1
 }
 
+### generate dynamic timestamps
+function stamp {
+    echo `date +%F" "%T`
+}
+
 ### quit -- exit the script after logging any errors, warnings, etc.
 function quit {
     # list generated warnings, if any
@@ -97,13 +101,16 @@ function quit {
         echo -e "${warn}${scriptName} generated the following warnings:" \
             "${normal}" >> "$logFile"
         for warnCode in "${exitWarn[@]}"; do
-            echo -e "${warn}-- [WARNING] ${warningExplain[$warnCode]}" \
-                "(code: ${warnCode}) --${normal}" >> "$logFile"
+            warnStamp="${warnCode%%_*}"
+            warnValue="${warnCode##*_}"
+            echo -e "${warn}${warnStamp} -- [WARNING]" \
+                "${warningExplain[$warnValue]} (code: ${warnValue}) --" \
+                "${normal}" >> "$logFile"
         done
     fi
     if [ -z "${exitError}" ]; then
         # exit cleanly
-        echo -e "${note}${stamp} --- ${scriptName} completed" \
+        echo -e "${note}[$(stamp)] --- ${scriptName} completed" \
             "---${normal}" >> "$logFile"
         exit 0
     else
@@ -111,8 +118,10 @@ function quit {
         echo -e "${err}${scriptName} generated the following errors:" \
             "${normal}" >> "$logFile"
         for errCode in "${exitError[@]}"; do
-            echo -e "${err}-- [ERROR] ${errorExplain[$errCode]}" \
-                "(code: ${errCode}) --$normal" >> "$logFile"
+            errStamp="${errCode%%_*}"
+            errValue="${errCode##*_}"
+            echo -e "${err}${errStamp}-- [ERROR] ${errorExplain[$errValue]}" \
+                "(code: ${errValue}) --${normal}" >> "$logFile"
         done
         exit 2
     fi
@@ -142,7 +151,7 @@ function checkExist {
 
 ### ncMaint - pass requested mode change type to NextCloud occ
 function ncMaint {
-    sudo -u ${webUser} php ${ncroot}/occ maintenance:mode --$1 \
+    sudo -u ${webUser} php ${ncRoot}/occ maintenance:mode --$1 \
         >> "$logFile" 2>&1
     maintResult="$?"
     return "$maintResult"
@@ -157,10 +166,10 @@ function cleanup {
     checkResult="$?"
     if [ "$checkResult" = "0" ]; then
         # directory still exists
-        exitWarn+=('111')
+        exitWarn+=("[$(stamp)]_111")
     else
         # directory removed
-        echo -e "${op}${stamp} Removed SQL temp directory${normal}" \
+        echo -e "${op}[$(stamp)] Removed SQL temp directory${normal}" \
             >> "$logFile"
     fi
 
@@ -168,21 +177,21 @@ function cleanup {
     # check value of 'clean503' to see if this is necessary (=1) otherwise, skip
     if [ "$clean503" = "1" ]; then
         # proceed with cleanup
-        echo -e "${op}${stamp} Removing 503 error page..." >> "$logFile"
+        echo -e "${op}[$(stamp)] Removing 503 error page..." >> "$logFile"
         rm -f "$webroot/$err503File" >> "$logFile" 2>&1
         # verify file is actually gone
         checkExist ff "$webroot/$err503File"
         checkResult="$?"
         if [ "$checkResult" = "0" ]; then
             # file still exists
-            exitWarn+=('5030')
+            exitWarn+=("[$(stamp)]_5030")
         else
             # file removed
-            echo -e "${info}${stamp} -- [INFO] 503 page removed from webroot" \
+            echo -e "${info}[$(stamp)] -- [INFO] 503 page removed from webroot" \
                 "--${normal}" >> "$logFile"
         fi
     else
-        echo -e "${op}${stamp} 503 error page never copied to webroot," \
+        echo -e "${op}[$(stamp)] 503 error page never copied to webroot," \
             "nothing to cleanup" >> "$logFile"
     fi
 
@@ -190,10 +199,10 @@ function cleanup {
     ncMaint off
     # check if successful
     if [ "$maintResult" = "0" ]; then
-        echo -e "${info}${stamp} -- [INFO] NextCloud now in regular" \
+        echo -e "${info}[$(stamp)] -- [INFO] NextCloud now in regular" \
                 "operating mode --${normal}" >> "$logFile"
         else
-            exitError+=('101')
+            exitError+=("[$(stamp)]_101")
             quit
     fi
 }
@@ -294,7 +303,7 @@ while getopts ':l:n:u:v5:w:s:b:d:' PARAMS; do
     case "$PARAMS" in
         l)
             # use provided location for logFile
-            logFile="${OPTARG}"
+            logFile="${OPTARG%/}"
             ;;
         n)
             # NextCloud webroot
@@ -343,7 +352,7 @@ done
 ## If not running as root, display error on console and exit
 if [ $(id -u) -ne 0 ]; then
     echo -e "\n${err}This script MUST be run as ROOT. Exiting.${normal}"
-    exit 2
+    exit 3
 fi
 
 ## Check NextCloud webroot
@@ -420,9 +429,9 @@ fi
 
 
 ### Log start of script operations
-echo -e "${note}${stamp}--- Start $scriptName execution ---${normal}" \
+echo -e "${note}[$(stamp)]--- Start $scriptName execution ---${normal}" \
     >> "$logFile"
-echo -e "${info}${stamp}-- [INFO] Log file located at ${lit}${logFile}${info}" \
+echo -e "${info}[$(stamp)]-- [INFO] Log file located at ${lit}${logFile}${info}" \
     "--${normal}" >> "$logFile"
 
 
@@ -433,7 +442,7 @@ export logFile="$logFile"
 ### Create sqlDump temporary directory and sqlDumpFile name
 sqlDumpDir=$( mktemp -d )
 sqlDumpFile="backup-`date +%Y%m%d_%H%M%S`.sql"
-echo -e "${info}${stamp} -- [INFO] mySQL dump file will be stored" \
+echo -e "${info}[$(stamp)] -- [INFO] mySQL dump file will be stored" \
     "at: ${lit}${sqlDumpDir}/${sqlDumpFile}${normal}" >> "$logFile"
 
 
@@ -446,9 +455,9 @@ echo -e "${info}${stamp} -- [INFO] mySQL dump file will be stored" \
 ## Check if webroot has been specified, if not, skip this entire section since there is nowhere to copy the 503 file.
 if [ -z "$webroot" ]; then
     # no webroot path provided
-    echo -e "${info}${stamp} -- [INFO] ${warn503} --${normal}" \
+    echo -e "${info}[$(stamp)] -- [INFO] ${warn503} --${normal}" \
         >> "$logFile"
-    exitWarn+=('5031')
+    exitWarn+=("[$(stamp)]_5031")
     clean503=0
 else
     # verify webroot actually exists
@@ -456,41 +465,41 @@ else
     checkResult="$?"
     if [ "$checkResult" = "1" ]; then
         # webroot directory specified could not be found
-        echo -e "${info}${stamp} -- [INFO] ${warn503} --${normal}" \
+        echo -e "${info}[$(stamp)] -- [INFO] ${warn503} --${normal}" \
             >> "$logFile"
-        exitWarn+=('5032')
+        exitWarn+=("{$stamp}_5032")
         clean503=0
     else
         # webroot exists
-        echo -e "${op}${stamp} Using webroot: ${lit}${webroot}${normal}" \
+        echo -e "${op}[$(stamp)] Using webroot: ${lit}${webroot}${normal}" \
             >> "$logFile"
         # Verify 503 file existance at given path
         checkExist ff "$err503Path"
         checkResult="$?"
         if [ "$checkResult" = "1" ]; then
             # 503 file could not be found
-            echo -e "${info}${stamp} -- [INFO] ${warn503} --${normal}" \
+            echo -e "${info}[$(stamp)] -- [INFO] ${warn503} --${normal}" \
                 >> "$logFile"
-            exitWarn+=('5033')
+            exitWarn+=("[$(stamp)]_5033")
             clean503=0
         else
             # 503 file exists and webroot is valid. Let's copy it!
-            echo -e "${op}${stamp} ${err503File} found at ${lit}${err503Path}" \
+            echo -e "${op}[$(stamp)] ${err503File} found at ${lit}${err503Path}" \
                 "${normal}" >> "$logFile"
-            echo -e "${op}${stamp} Copying 503 error page to webroot..." \
+            echo -e "${op}[$(stamp)] Copying 503 error page to webroot..." \
                 "${normal}" >> "$logFile"
             cp "${err503Path}" "$webroot/" >> "$logFile" 2>&1
             copyResult="$?"
             # verify copy was successful
                 if [ "$copyResult" = "1" ]; then
                     # copy was unsuccessful
-                    echo -e "${info}${stamp} -- [INFO] ${warn503} --${normal}" \
+                    echo -e "${info}[$(stamp)] -- [INFO] ${warn503} --${normal}" \
                         >> "$logFile"
-                    exitWarn+=('5035')
+                    exitWarn+=("[$(stamp)]_5035")
                     clean503=0
                 else
                 # copy was successful
-                echo -e "${info}${stamp} -- [INFO] 503 error page" \
+                echo -e "${info}[$(stamp)] -- [INFO] 503 error page" \
                     "successfully copied to webroot --${normal}" >> "$logFile"
                 clean503=1
                 fi
@@ -505,10 +514,10 @@ fi
 ncMaint on
 # check if successful
 if [ "$maintResult" = "0" ]; then
-    echo -e "${info}${stamp} -- [INFO] NextCloud now in maintenance mode --" \
+    echo -e "${info}[$(stamp)] -- [INFO] NextCloud now in maintenance mode --" \
         "${normal}" >> "$logFile"
 else
-    exitError+=('100')
+    exitError+=("[$(stamp)]_100")
     cleanup
     quit
 fi
@@ -519,23 +528,23 @@ mapfile -t sqlParams < "$sqlDetails"
 
 
 ### Dump SQL
-echo -e "${op}${stamp} Dumping NextCloud SQL database...${normal}" >> "$logFile"
+echo -e "${op}[$(stamp)] Dumping NextCloud SQL database...${normal}" >> "$logFile"
 mysqldump --single-transaction -h"${sqlParams[0]}" -u"${sqlParams[1]}" \
     -p"${sqlParams[2]}" "${sqlParams[3]}" > "${sqlDumpDir}/${sqlDumpFile}" \
     2>> "$logFile"
 # verify
 dumpResult="$?"
 if [ "$dumpResult" = "0" ]; then
-    echo -e "${ok}${stamp} -- [SUCCESS] SQL dumped successfully --${normal}" \
+    echo -e "${ok}[$(stamp)] -- [SUCCESS] SQL dumped successfully --${normal}" \
         >> "$logFile"
 else
-    exitError+=('200')
+    exitError+=("[$(stamp)]_200")
     cleanup
     quit
 fi
 
 ### Call borgbackup to copy actual files
-echo -e "${op}${stamp} Pre-backup tasks completed, calling borgbackup..." \
+echo -e "${op}[$(stamp)] Pre-backup tasks completed, calling borgbackup..." \
     "${normal}" >> "$logFile"
 
 ## Get borgbackup settings and repo details
@@ -544,10 +553,10 @@ mapfile -t borgConfig < "$borgDetails"
 ## check if any required borg configuration variables in defintion file are
 ## empty and exit with error, otherwise, map array items to variables
 # check: borg base directory
-echo -e "${op}${stamp} Verifying supplied borg configuration variables..." \
+echo -e "${op}[$(stamp)] Verifying supplied borg configuration variables..." \
     "${normal}" >> "$logFile"
 if [ -z "${borgConfig[0]}" ]; then
-    exitError+=('210')
+    exitError+=("[$(stamp)]_210")
     cleanup
     quit
 else
@@ -556,16 +565,16 @@ else
     checkResult="$?"
     if [ "$checkResult" = "1" ]; then
         # borg base directory specified could not be found
-        exitError+=('210')
+        exitError+=("[$(stamp)]_210")
         cleanup
         quit
     fi
-    echo -e "${op}${stamp} Borg base dir... OK${normal}" >> "$logFile"
+    echo -e "${op}[$(stamp)] Borg base dir... OK${normal}" >> "$logFile"
     export BORG_BASE_DIR="${borgConfig[0]%/}"
 fi
 # check: path to SSH keyfile
 if [ -z "${borgConfig[1]}" ]; then
-    exitError+=('211')
+    exitError+=("[$(stamp)]_211")
     cleanup
     quit
 else
@@ -573,28 +582,28 @@ else
     checkResult="$?"
     if [ "$checkResult" = 1 ]; then
         # SSH keyfile specified could not be found
-        exitError+=('211')
+        exitError+=("[$(stamp)]_211")
         cleanup
         quit
     fi
-    echo -e "${op}${stamp} Borg SSH key... OK${normal}" >> "$logFile"
+    echo -e "${op}[$(stamp)] Borg SSH key... OK${normal}" >> "$logFile"
     export BORG_RSH="ssh -i ${borgConfig[1]}"
 fi
 # check: name of borg repo
 if [ -z "${borgConfig[2]}" ]; then
-    exitError+=('212')
+    exitError+=("[$(stamp)]_212")
     cleanup
     quit
 else
-    echo -e "${op}${stamp} Borg REPO name... OK${normal}" >> "$logFile"
+    echo -e "${op}[$(stamp)] Borg REPO name... OK${normal}" >> "$logFile"
     export BORG_REPO="${borgConfig[2]}"
 fi
 # repo password
 if [ -n "${borgConfig[3]}" ]; then
-    echo -e "${op}${stamp} Borg SSH/REPO password... OK${normal}" >> "$logFile"
+    echo -e "${op}[$(stamp)] Borg SSH/REPO password... OK${normal}" >> "$logFile"
     export BORG_PASSPHRASE="${borgConfig[3]}"
 else
-    exitWarn+=('2111')
+    exitWarn+=("[$(stamp)]_2111")
     # if the password was omitted by mistake, export a dummy password so borg
     # fails with an error instead of sitting and waiting for input
     export BORG_PASSPHRASE="DummyPasswordSoBorgFails"
@@ -607,31 +616,31 @@ borgExclude="${borgConfig[5]}"
 borgPrune="${borgConfig[6]}"
 # export: borg remote path (if not blank)
 if [ -n "${borgConfig[7]}" ]; then
-    echo -e "${op}${stamp} Borg REMOTE path... OK${normal}" >> "$logFile"
+    echo -e "${op}[$(stamp)] Borg REMOTE path... OK${normal}" >> "$logFile"
     export BORG_REMOTE_PATH="${borgConfig[7]}"
 else
-    exitWarn+=('2112')
+    exitWarn+=("[$(stamp)]_2112")
 fi
 
 ## If borgXtra exists, map contents to an array variable
 if [ -n "$borgXtra" ]; then
-    echo -e "${op}${stamp} Processing referenced extra files list for" \
+    echo -e "${op}[$(stamp)] Processing referenced extra files list for" \
         "borgbackup to include in backup${normal}" >> "$logFile"
     checkExist ff "$borgXtra"
     checkResult="$?"
     if [ "$checkResult" = "0" ]; then
-        echo -e "${op}${stamp} Found ${lit}${borgXtra}${normal}" >> "$logFile"
+        echo -e "${op}[$(stamp)] Found ${lit}${borgXtra}${normal}" >> "$logFile"
         mapfile -t xtraFiles < "$borgXtra"
-        echo -e "${op}${stamp} Processed extra files list for inclusion in" \
+        echo -e "${op}[$(stamp)] Processed extra files list for inclusion in" \
             "borgbackup${normal}" >> "$logFile"
     else
-        exitWarn+=('2113')
+        exitWarn+=("[$(stamp)]_2113")
     fi
 else
     # no extra locations specified
-    echo -e "${op}${stamp} No additional locations specified for backup." \
+    echo -e "${op}[$(stamp)] No additional locations specified for backup." \
         "Only NextCloud data files will be backed up${normal}" >> "$logFile"
-    exitWarn+=('2116')
+    exitWarn+=("[$(stamp)]_2116")
 fi
 
 ## Check if borgExclude exists since borg will throw an error if it's missing
@@ -639,16 +648,16 @@ if [ -n "$borgExclude" ]; then
     checkExist ff "$borgExclude"
     checkResult="$?"
     if [ "$checkResult" = "0" ]; then
-            echo -e "${op}${stamp} Found ${lit}${borgExclude}${normal}" \
+            echo -e "${op}[$(stamp)] Found ${lit}${borgExclude}${normal}" \
                 >> "$logFile"
     else
         # file not found, unset the variable so it's like it was not specified
         # in the first place and continue with backup
         unset borgExclude
-        exitWarn+=('2114')
+        exitWarn+=("[$(stamp)]_2114")
     fi
 else
-    echo -e "${op}${stamp} Exclusion pattern file not specified." \
+    echo -e "${op}[$(stamp)] Exclusion pattern file not specified." \
         "No exclusions will be processed${normal}" >> "$logFile"
 fi
 
@@ -659,13 +668,13 @@ fi
 ## the 'noexec' option for security.  Thus, we will use/create a 'tmp' folder
 ## within the BORG_BASE_DIR and instruct python to use that instead of /tmp
 # check if BORG_BASE_DIR/tmp exists, if not, create it
-echo -e "${op}${stamp} Checking for tmp directory at ${lit}${BORG_BASE_DIR}" \
+echo -e "${op}[$(stamp)] Checking for tmp directory at ${lit}${BORG_BASE_DIR}" \
     "${normal}" >> "$logFile"
 checkExist fd "$BORG_BASE_DIR/tmp"
 checkResult="$?"
 if [ "$checkResult" = "1" ]; then
     # folder not found
-    echo -e "${op}${stamp} tmp folder not found... creating${lit}" \
+    echo -e "${op}[$(stamp)] tmp folder not found... creating${lit}" \
         "${BORG_BASE_DIR}/tmp${normal}" >> "$logFile"
     mkdir "$BORG_BASE_DIR/tmp" 2>> "$logFile"
     # verify folder created
@@ -673,17 +682,17 @@ if [ "$checkResult" = "1" ]; then
     checkResult="$?"
     if [ "$checkResult" = "0" ]; then
         # folder exists
-        echo -e "${op}${stamp} tmp folder created within borg base directory" \
+        echo -e "${op}[$(stamp)] tmp folder created within borg base directory" \
             "${normal}" >> "$logFile"
     else
         # problem creating folder and script will exit
-        exitError+=('215')
+        exitError+=("[$(stamp)]_215")
         cleanup
         quit
     fi
 else
     # folder found
-    echo -e "${op}${stamp} tmp folder found within borg base directory" \
+    echo -e "${op}[$(stamp)] tmp folder found within borg base directory" \
         "${normal}" >> "$logFile"
 fi
 # export TMPDIR environment variable
@@ -694,7 +703,7 @@ export TMPDIR="${BORG_BASE_DIR}/tmp"
 # commandline depends on whether borgExclude is empty or not
 if [ -z "$borgExclude" ]; then
     # borgExclude is empty
-    echo -e "${info}${stamp} --[INFO] Executing borg without exclusions --" \
+    echo -e "${info}[$(stamp)] --[INFO] Executing borg without exclusions --" \
         "${normal}" >> "$logFile"
     borg --show-rc create ${borgCreateParams} ::`date +%Y-%m-%d_%H%M%S` \
         ${xtraFiles[@]} \
@@ -702,7 +711,7 @@ if [ -z "$borgExclude" ]; then
         2>> "$logFile"
 else
     # borgExclude is not empty
-    echo -e "${info}${stamp} --[INFO] Executing borg with exclusions --" \
+    echo -e "${info}[$(stamp)] --[INFO] Executing borg with exclusions --" \
         "${normal}" >> "$logFile"
     borg --show-rc create ${borgCreateParams} --exclude-from ${borgExclude} \
         ::`date +%Y-%m-%d_%H%M%S` \
@@ -714,54 +723,54 @@ fi
 ## Check status of borg operation
 borgResult="$?"
 if [ "$borgResult" -eq 0 ]; then
-    echo -e "${ok}${stamp} -- [SUCCESS] Borg backup completed successfully --" \
+    echo -e "${ok}[$(stamp)] -- [SUCCESS] Borg backup completed successfully --" \
         "${normal}" >> "$logFile"
 elif [ "$borgResult" -eq 1 ]; then
-    exitWarn+=('2200')
+    exitWarn+=("[$(stamp)]_2200")
 elif [ "$borgResult" -ge 2 ]; then
-    exitError+=('220')
+    exitError+=("[$(stamp)]_220")
     cleanup
     quit
 else
-    exitWarn+=('2201')
+    exitWarn+=("[$(stamp)]_2201")
 fi
 
 ## Generate and execute borg prune
 # command depends on whether or not parameters have been defined
 if [ -n "$borgPrune" ]; then
     # parameters defined
-    echo -e "${info}${stamp} --[INFO] Executing borg prune operation --" \
+    echo -e "${info}[$(stamp)] --[INFO] Executing borg prune operation --" \
         "${normal}" >> "$logFile"
     borg prune --show-rc -v ${borgPruneParams} ${borgPrune} \
         2>> "$logFile"
     # check return-status
     pruneResult="$?"
     if [ "$pruneResult" -eq 0 ]; then
-        echo -e "${ok}${stamp} -- [SUCCESS] Borg prune completed successfully" \
+        echo -e "${ok}[$(stamp)] -- [SUCCESS] Borg prune completed successfully" \
             "--${normal}" >> "$logFile"
     elif [ "$pruneResult" -eq 1 ]; then
-        exitWarn+=('2210')
+        exitWarn+=("[$(stamp)]_2210")
     elif [ "$pruneResult" -ge 2 ]; then
-        exitError+=('221')
+        exitError+=("[$(stamp)]_221")
     else
-        exitWarn+=('2212')
+        exitWarn+=("[$(stamp)]_2212")
     fi
 else
     # parameters not defined... skip pruning
-    exitWarn+=('2115')
+    exitWarn+=("[$(stamp)]_2115")
 fi
 
 
 ### borgbackup completed
-echo -e "${op}${stamp} Borgbackup completed... begin cleanup" \
+echo -e "${op}[$(stamp)] Borgbackup completed... begin cleanup" \
     "${normal}" >> "$logFile"
 
 
 ### Exit script
-echo -e "${bold}${op}${stamp} ***Normal exit process***${normal}" \
+echo -e "${bold}${op}[$(stamp)] ***Normal exit process***${normal}" \
     >> "$logFile"
 cleanup
-echo -e "${bold}${ok}${stamp} -- [SUCCESS] All processes completed" \
+echo -e "${bold}${ok}[$(stamp)] -- [SUCCESS] All processes completed" \
     "successfully --${normal}" >> "$logFile"
 quit
 

root/NCscripts/xtraLocations.borg

@@ -22,6 +22,7 @@
 /etc/fail2ban/jail.d/
 /root/.bashrc
 /root/NCscripts/
+/root/.ssh/
 /etc/mysql/my.cnf
 /etc/nginx/
 /etc/php/7.0/cli/php.ini