You'll be better off splitting the usb with a jffs and a opt volume.
If I may ask, why have two partitions? I had a 2GB USB, and since the only thing it is used for is YAMon, I figured I'd just leave it as one partition...
You'll be better off splitting the usb with a jffs and a opt volume.
If I may ask, why have two partitions? I had a 2GB USB, and since the only thing it is used for is YAMon, I figured I'd just leave it as one partition...
As long as everyone is asking questions, why not mount to /opt?
I changed the day number in the config.file from 19 to 20. In the settings tab it still shows 19. I have shutdown and restarted the script a couple of times. I have also selected the reset settings button on the settings page - how do I reread the config.file to reflect the change.
That's one thing I've asked myself about being able to change the day as my ISP floats me by a day sometimes but to do what you after. Gotta clear the browser cache for the router site. In my case 192.168.1.1... or you can try ctrl+f5 which probably wont work.
Why some of that data is locally stored and supersedes the files is beyond me.
Why is the ISP reset date changing?!? If you've changed ISP's and the date moves that is understandable. I cannot fathom why it would change otherwise. Can you explain?
YAMon was not really designed to work with a frequently moving reset date... that may take some work.
Back to the question at hand: why does the JS load the reset date from the LocalStorage variable rather than the config.js?
That was a bug and I've fixed it. Give it another try (but you'll likely need to force a refresh by typing <ctrl>+F5
Al
Same ISP for years... I dont pretend to understand it and it's never by much but see ?
Also, any ideas on what I asked about how storage is handled within YAMon when the stick's near full ? Like can you add a keep x days worth of data ? Like could you code something to delete data older than x months ?
Not sure if how people store it would matter, I use the month and year option.
I changed the day number in the config.file from 19 to 20. In the settings tab it still shows 19. I have shutdown and restarted the script a couple of times. I have also selected the reset settings button on the settings page - how do I reread the config.file to reflect the change.
That's one thing I've asked myself about being able to change the day as my ISP floats me by a day sometimes but to do what you after. Gotta clear the browser cache for the router site. In my case 192.168.1.1... or you can try ctrl+f5 which probably wont work.
Why some of that data is locally stored and supersedes the files is beyond me.
Why is the ISP reset date changing?!? If you've changed ISP's and the date moves that is understandable. I cannot fathom why it would change otherwise. Can you explain?
YAMon was not really designed to work with a frequently moving reset date... that may take some work.
Back to the question at hand: why does the JS load the reset date from the LocalStorage variable rather than the config.js?
That was a bug and I've fixed it. Give it another try (but you'll likely need to force a refresh by typing <ctrl>+F5
Al
Same ISP for years... I dont pretend to understand it and it's never by much but see ?
Also, any ideas on what I asked about how storage is handled within YAMon when the stick's near full ? Like can you add a keep x days worth of data ? Like could you code something to delete data older than x months ?
Not sure if how people store it would matter, I use the month and year option.
From month to month, do you know when your next interval starts? I see no rhyme nor reason in the sequence of start dates. Unless there is a pattern, I don't know what to do to help you with this! (Suggest an ISP with a constant interval start date, perhaps?!?)
With respect to filling your USB drive. Unless you are using a minuscule thumb drive, you should not have any problems - e.g., I now have close to 1100 daily and monthly data files dating back to May 2013... they require a scant 17MB of disk space.
OTOH, the log files can be come disk hogs (esp. if _logleve<1). Those are the files that you want to clean out on a regular basis. Perhaps the contents of daily-bu too/
YAMon currently does not have the capability to purge these files. It would probably be better to run that as a chron job rather than adding it within YAMon IMHO.
I changed the day number in the config.file from 19 to 20. In the settings tab it still shows 19. I have shutdown and restarted the script a couple of times. I have also selected the reset settings button on the settings page - how do I reread the config.file to reflect the change.
That's one thing I've asked myself about being able to change the day as my ISP floats me by a day sometimes but to do what you after. Gotta clear the browser cache for the router site. In my case 192.168.1.1... or you can try ctrl+f5 which probably wont work.
Why some of that data is locally stored and supersedes the files is beyond me.
Why is the ISP reset date changing?!? If you've changed ISP's and the date moves that is understandable. I cannot fathom why it would change otherwise. Can you explain?
YAMon was not really designed to work with a frequently moving reset date... that may take some work.
Back to the question at hand: why does the JS load the reset date from the LocalStorage variable rather than the config.js?
That was a bug and I've fixed it. Give it another try (but you'll likely need to force a refresh by typing <ctrl>+F5
Al
Same ISP for years... I dont pretend to understand it and it's never by much but see ?
Also, any ideas on what I asked about how storage is handled within YAMon when the stick's near full ? Like can you add a keep x days worth of data ? Like could you code something to delete data older than x months ?
Not sure if how people store it would matter, I use the month and year option.
From month to month, do you know when your next interval starts? I see no rhyme nor reason in the sequence of start dates. Unless there is a pattern, I don't know what to do to help you with this! (Suggest an ISP with a constant interval start date, perhaps?!?)
With respect to filling your USB drive. Unless you are using a minuscule thumb drive, you should not have any problems - e.g., I now have close to 1100 daily and monthly data files dating back to May 2013... they require a scant 17MB of disk space.
OTOH, the log files can be come disk hogs (esp. if _logleve<1). Those are the files that you want to clean out on a regular basis. Perhaps the contents of daily-bu too/
YAMon currently does not have the capability to purge these files. It would probably be better to run that as a chron job rather than adding it within YAMon IMHO.
I dont see how that's possible. At one point I manages 100+ mb of space before I reset from the monthly issue you fixed.
Since my last data wipe on the 27th where I started gathering data on the 28th. My USB drive is already at 7.1mb
It's ext4 as suggested and nothing else done but plugging it to the router. _________________
Don't recall what my log level is but whatever the default of the install is, is what it's at. As for the ISP, only game in town.
But there's nothing that can be done for the billing date thing ? Even if at the end of the current cycle yamon asks for current date and if it's a neg 1. 22>21, it uses historical date to fill that missing day. Hope that makes sense. _________________
With respect to filling your USB drive. Unless you are using a minuscule thumb drive, you should not have any problems - e.g., I now have close to 1100 daily and monthly data files dating back to May 2013... they require a scant 17MB of disk space.
OTOH, the log files can be come disk hogs (esp. if _logleve<1). Those are the files that you want to clean out on a regular basis. Perhaps the contents of daily-bu too/
YAMon currently does not have the capability to purge these files. It would probably be better to run that as a chron job rather than adding it within YAMon IMHO.
I dont see how that's possible. At one point I manages 100+ mb of space before I reset from the monthly issue you fixed.
Since my last data wipe on the 27th where I started gathering data on the 28th. My USB drive is already at 7.1mb
It's ext4 as suggested and nothing else done but plugging it to the router.
I'm looking at my USB drive right now. After clearing out a *lot* of old logs, etc., my YAMon3 directory is 102MB. And, within that directory, I have:
files at the root --> 173KB
/strings --> 2KB
/includes -->28KB
/www --> 427KB
/old --> 621KB (I put all of my old versions of the main yamon script into this folder)
/daily-bu2-->5,900KB
/data-->17,140KB (and I assure you the files go back to May 2013)
/logs --> 80,000KB
NB - if _loglevel=-1, it is not unusual to see a log file for one day that is 30+MB. If that file is wrapped up into the daily-backup, the disk space gets consumed even faster.
Regardless, it would not be overly difficult to create a cron job that purges the logs on a regular basis - e.g., the following command removes all files older than 30 days with a `.log` extension:
Don't recall what my log level is but whatever the default of the install is, is what it's at. As for the ISP, only game in town.
But there's nothing that can be done for the billing date thing ? Even if at the end of the current cycle yamon asks for current date and if it's a neg 1. 22>21, it uses historical date to fill that missing day. Hope that makes sense.
Does your your ISP enforce a cap on your data usage?
If no (i.e., you have unlimited data), the billing date is not particularly relevant (other than for display purposes). However, if you do have a cap, tracking the totals relative to the start of your billing cycle is important.
YAMon has been designed to work relative to a fixed (and unchanging) start to the billing cycle... making that variable would require a *massive* change to the way that the data is organized in the bash script and accessed via the reports.
One poorly conceived notion that is coming to mind is a script to `re-arrange` the data after the fact (a tweaked version of h2m.sh perhaps)... however, unless you know in advance when the new cycles will start, it'll be impossible to automate that process. Can you get that info from your ISP?
Let me noodle on this a bit longer. Or if anyone else has an idea, chime in.
