bortzmeyer/check_expire
2
1
Fork 2
Code Issues Pull Requests Projects Releases Wiki Activity

Allow a specific cache directory or no cache #5

Closed
Seb35 wants to merge 0 commits from Seb35/check_expire:issue-4 into master
pull from: Seb35/check_expire:issue-4
merge into: bortzmeyer:master
Conversation 1 Commits - Files Changed -
Seb35 commented 2022-12-18 19:01:35 +01:00
First-time contributor
Copy Link

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
bortzmeyer commented 2024-06-16 20:45:00 +02:00
Owner
Copy Link

Merged just now, thanks.

Merged just now, thanks.
bortzmeyer closed this pull request 2024-06-16 20:45:00 +02:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 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.
Delete Branch "Seb35/check_expire:issue-4"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?