You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@jimsalterjrs mhm, did you ran into actual problems? Because the smaller period interval changed due introduction of weekly snapshot types, therefore I also adapted the defaults to be near the same. So monthly_warn = 5 actually means 5 weeks old, and monthly_crit = 6 means 6 weeks old. From the code:
On December 15, 2018 8:52:40 AM Christoph Klaffl ***@***.***> wrote:
@jimsalterjrs mhm, did you ran into actual problems? Because the smaller
period interval changed due introduction of weekly snapshot types,
therefore I also adapted the defaults to be near the same. So monthly_warn
= 5 actually means 5 weeks old, and monthly_crit = 6 means 6 weeks old.
From the code:
if ($type eq 'frequently') { $smallerperiod = 1; }
elsif ($type eq 'hourly') { $smallerperiod = 60; }
elsif ($type eq 'daily') { $smallerperiod = 60*60; }
elsif ($type eq 'weekly') { $smallerperiod = 60*60*24; }
elsif ($type eq 'monthly') { $smallerperiod = 60*60*24*7; }
elsif ($type eq 'yearly') { $smallerperiod = 60*60*24*31; }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
The reason will be displayed to describe this comment to others. Learn more.
@jimsalterjrs As I was running with the patches and monitoring for over half a year without the issue, can you provide me with your time zone? Especially the corresponding symlink on your system: ls -l /etc/localtime
The reason will be displayed to describe this comment to others. Learn more.
EST. Can't give you the symlink target directly, sorry, not at that
machine... And having trouble remembering *which* machine it was, honestly.
Can you just change the monthly alarm calculation to use days in the first
place? Weeks are not a sensible unit for that IMO.
On December 15, 2018 11:17:10 Christoph Klaffl ***@***.***> wrote:
@jimsalterjrs As I was running with the patches and monitoring for over
half a year without the issue, can you provide me with your time zone?
Especially the corresponding symlink on your system:
ls -l /etc/localtime
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
The reason will be displayed to describe this comment to others. Learn more.
sure, I changed it for consistency while introducing weeklies, because all the other ones also used the next smaller interval type for the calculation.
The reason will be displayed to describe this comment to others. Learn more.
That would definitely be badass. I wholeheartedly approve of
somebody else doing this work of which you speak! =)
On 2018-12-15
20:08, Shawn Perry wrote:
Can we change it to specify the unit? Like
5w, 32d, or 1mo?
On Sat, Dec 15, 2018, 4:32 PM Christoph Klaffl
wrote:
> sure, I changed it for consistency while introducing
weeklies, because all
> the other ones also used the next smaller
interval type for the calculation.
>
> --
> You are receiving this
because you are subscribed to this thread.
> Reply to this email
directly, view it on GitHub
> ,
> or mute the thread
>
> .
>
--
You are receiving this because you were mentioned.
Reply to
The reason will be displayed to describe this comment to others. Learn more.
I will gladly give a hardy congratulations and a good job to the person that makes this happens. 😉
From: Jim Salter
Sent: Saturday, December 15, 2018 6:10 PM
To: jimsalterjrs/sanoid
Cc: Shawn Perry; Comment
Subject: Re: [jimsalterjrs/sanoid] fix broken monthly_warn monthly_crit insanoid.defaults.conf (dc4df15)
That would definitely be badass. I wholeheartedly approve of
somebody else doing this work of which you speak! =)
On 2018-12-15
20:08, Shawn Perry wrote:
Can we change it to specify the unit? Like
5w, 32d, or 1mo?
On Sat, Dec 15, 2018, 4:32 PM Christoph Klaffl
wrote:
> sure, I changed it for consistency while introducing
weeklies, because all
> the other ones also used the next smaller
interval type for the calculation.
>
> --
> You are receiving this
because you are subscribed to this thread.
> Reply to this email
directly, view it on GitHub
> ,
> or mute the thread
>
> .
>
--
You are receiving this because you were mentioned.
Reply to
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jimsalterjrs mhm, did you ran into actual problems? Because the smaller period interval changed due introduction of weekly snapshot types, therefore I also adapted the defaults to be near the same. So monthly_warn = 5 actually means 5 weeks old, and monthly_crit = 6 means 6 weeks old. From the code:
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I will investigate then.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jimsalterjrs As I was running with the patches and monitoring for over half a year without the issue, can you provide me with your time zone? Especially the corresponding symlink on your system:
ls -l /etc/localtime
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure, I changed it for consistency while introducing weeklies, because all the other ones also used the next smaller interval type for the calculation.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dc4df15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR landed #306