Greetings,
So my inbox is getting loaded with messages from chkspace telling me I am low on space. I'm at 6% usage with 46Gigs of space available. What is it checking for, and what threshhold do I need to meet in order to shot this watchdog up? It would seem 46Gigs is plenty, and if it is looking at percentage, it should be happy with 94% available.
It's not based on percentage, but rather whatever value is set in SCFG->File Options->Min Bytes Free Disk Space (less than double this value will trigger chkspace to send a notification).The Value in there now is 100M Since I have 45Gigs it should not be triggering, right?
This value was changed from kilobytes to bytes in v3.20 and chkspace.js was
recently updated accordingly. Are you using the latest chkspace.js?
I just looked at the code and it says it is v 1.8, why would the version be included with the git pull?I just looked at the code on gitlab.synchro.net, that version number is in the newest too, but there were some differences between my copy and what was in the git repo, so I downloaded it and swapped it out, I will see if that fixes the issue.
Re: chkspace complaining
By: Digital Man to Fratm on Tue Feb 21 2023 10:17:52
It's not based on percentage, but rather whatever value is set in SCFG->File Options->Min Bytes Free Disk Space (less than double this value will trigger chkspace to send a notification).The Value in there now is 100M Since I have 45Gigs it should not be triggering, right?
This value was changed from kilobytes to bytes in v3.20 and chkspace.js was
recently updated accordingly. Are you using the latest chkspace.js?
I should be, I pulled lated from git on the 13th of March, when I started setting this board up (my bbs is new.)
I just looked at the code and it says it is v 1.8, why would the version be included with the git pull?
Re: chkspace complaining
By: Fratm to Digital Man on Tue Feb 21 2023 16:45:22
I just looked at the code and it says it is v 1.8, why would the version be included with the git pull?I just looked at the code on gitlab.synchro.net, that version number is in the newest too, but there were some differences between my copy and what was in the git repo, so I downloaded it and swapped it out, I will see if that fixes the issue.
You should be doing a "git pull" (or similar) to update *all* your exec/* files, not just downloading this one single file.
Fratm wrote to Digital Man <=-
You should be doing a "git pull" (or similar) to update *all* your exec/* files, not just downloading this one single file.
Yes, I understand how git works, only been a sysadmin for 30 year
;) this was a quick and dirty test to see if that was the issue.
I didn't want to wait for a backup to run before I could test
it. Sometimes you break the rules to test shit out before you go
to production.
Thanks, and by the way, that was the issue.
Fratm wrote to Digital Man <=-
You should be doing a "git pull" (or similar) to update *all* your exec/* files, not just downloading this one single file.
Yes, I understand how git works, only been a sysadmin for 30 year
;) this was a quick and dirty test to see if that was the issue.
So, as a 30-year sysadmin, when it didn't work you figured the best
approach was to ask "why?", instead of doing it properly (doing a full
git update)? Hmmmmm...
I didn't want to wait for a backup to run before I could test
it. Sometimes you break the rules to test shit out before you go
to production.
Any *good* 30-year sysadmin wouldn't do that.
Thanks, and by the way, that was the issue.
What a surprise!
So, as a 30-year sysadmin, when it didn't work you figured the best
approach was to ask "why?", instead of doing it properly (doing a full
git update)? Hmmmmm...
Any *good* 30-year sysadmin wouldn't do that.
What a surprise!
Digital Man wrote to Gamgee <=-
You should be doing a "git pull" (or similar) to update *all* your exec/* files, not just downloading this one single file.
Yes, I understand how git works, only been a sysadmin for 30 year
;) this was a quick and dirty test to see if that was the issue.
So, as a 30-year sysadmin, when it didn't work you figured the best
approach was to ask "why?", instead of doing it properly (doing a full
git update)? Hmmmmm...
I think you're taking things out of context here Gamgee. Fratm
didn't do a partial update and then ask "why?" (something wasn't
working as expected). I just wanted to make sure they were aware
of the suggested update practice, and they are. We're all good.
Fratm wrote to Gamgee <=-
Re: Re: chkspace complaining
By: Gamgee to Fratm on Wed Feb 22 2023 14:23:00
So, as a 30-year sysadmin, when it didn't work you figured the best
approach was to ask "why?", instead of doing it properly (doing a full
git update)? Hmmmmm...
Any *good* 30-year sysadmin wouldn't do that.
What a surprise!
Kind of acting dickish here, arn't you?
Yes, I was... I apologize for that.
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 513 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 11:39:40 |
| Calls: | 8,287 |
| Files: | 15,517 |
| Messages: | 928,475 |