Allow a specific cache directory or no cache #5

Open
Seb35 wants to merge 1 commits from Seb35/check_expire:issue-4 into master
First-time contributor

As said in #4, depending on the env var set, the cache directory is:

  • "$XDG_CACHE_HOME/ianardap" or
  • "$HOME/.ianardapcaches" or
  • none
    In the last case, the warning is something like:
google.com OK: expires in 2096 days, 11:38:03.674495. (WARNING: no cache file used, please set environement variable XDG_CACHE_HOME or HOME)

If I understand correctly the monitoring-plugins specs, it does not seem forbidden to display such warning, even if unusual.

NB: two tests in tests.yaml fail independently of this change, because nic.ar has no more timeout in the given timeout of 1s (6th test), and .re now has an RDAP server (4th test).

As said in #4, depending on the env var set, the cache directory is: * "$XDG_CACHE_HOME/ianardap" or * "$HOME/.ianardapcaches" or * none In the last case, the warning is something like: ``` google.com OK: expires in 2096 days, 11:38:03.674495. (WARNING: no cache file used, please set environement variable XDG_CACHE_HOME or HOME) ``` If I understand correctly the [monitoring-plugins specs](https://www.monitoring-plugins.org/doc/guidelines.html#AEN33), it does not seem forbidden to display such warning, even if unusual. NB: two tests in tests.yaml fail independently of this change, because nic.ar has no more timeout in the given timeout of 1s (6th test), and .re now has an RDAP server (4th test).
Seb35 force-pushed issue-4 from 09eeabfcba to 0b10e8d563 2022-12-18 19:10:08 +01:00 Compare
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b Seb35-issue-4 master
git pull issue-4

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff Seb35-issue-4
git push origin master
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bortzmeyer/check_expire#5
No description provided.