don't know where
Thanks. I'd like to keep containers to a min with only 450MB of RAM
Posts by ojtindrum
-
-
Is there anyway to alter shairport config given the config file states it's autogenerated?
I'm getting pauses during playback and would like to be able to play around to try to resolve or is the only alternative to install via terminal and configure manually?
tia
-
No
see when y throw out a monosyllabic response like that folks might conclude there's no intention of including it
will it be included in future or has it been discontinued?
-
is the downloader plugin available for omv8?
-
putting a hold on cterm means you lock the version of the installed package
also (if not a dependency) can prevent a package being installed at all ime
-
I know my time doesn't mean anything
Arron I’ve zero doubt the demands on foss engineers are intense. I do not envy you your job and contrary to appearances (apparently) I very much appreciate your time.
-
That is literally the only way to remove a dependency.
Arron I asked for clarification on how to put a hold on cterm, that you've made it a dependency doesn't therefore equate my inquiry to a request to have that dependency reviewed
The dependency can be disabled in 7.6.13
Thanks, clearly I'm not the only one who'd prefer not to have cterm installed
-
You also have given me no numbers. How much ram is the increase?
With Plex running (and standard config otherwise) it idles at around 47% without cterm
with cterm it's 54%
It's not a huge deviance but with this hardware I was wanting to stay on top of keeping demands on resources to a minimum in anticipation of resource use increasing with updates
I do understand why you're reluctant to support this config
-
Is this not reasonable?
I'm not objecting but then again I wasn't asking you to code for me
what happens when a plugin is installed? omv-engined is restarted among other things like regenerating workbench files. Maybe these steps have a surge in ram
I restart between install/uninstall and can see dynamic surges therefore I wait for things to settle before assessing ram consumption
-
It is a little unfair to ask me to do all of the work.
I asked for a solution to the problem I had of being unable to apply a hold on cterm.
As for the ram use you've made it clear you don't consider it a problem and that my particular system with such limited ram is unsupported.
I've just reinstalled the plugin and my ram's just hopped back to what it was before I uninstalled it (otherwise exact same config). You may not consider that diagnostically significant but it seems pretty solid to me
-
It seems like you are asking me to support an unsupported system
Ok then.
Fair enough, ta for your time.
-
Please explain
No idea Arron, all I know is I had a stable average ram usage that increased somewhat since cterm and removal of cterm reduces it.
i guess the only option is to configure docker from the command line?
-
It is a requirement of the plugin...people kept uninstalling it and apt would uninstall the compose and kvm plugins.
Currently uninstalled on my system ant the compose plugin seems to be working fine
Why do you want it uninstalled? If it is disabled, it is causing zero problems.
Seems to have increased my ram usage (i have 512mb)
-
What does this mean?
I uninstalled cterm which was reinstalled with a compose update.
just now tried to put a hold both via dpkg and the apt tool plugin and was unable to do so
-
is there anyway to put a hold on the cterm plugin?
unable to achieve it for some reason
-
Minimizing uninstalls until the plugin is working correctly is helpful.
I had tried swapon --show when a problem first cropped up following an omv update (the one before the last (can't recall the build number)), it was reporting service not running or similar (sorry can't be more accurate it was some days past).
I'd planned to setup a fresh system so I have an sd ready to go if I have further problems so can install the beta plugin fresh without having to purge folder2ram and monitor from there.
I'll let you know if anything crops up.
-
unless you made sure to clean up every little thing about each version and reboot before installing the other version, you may be making the problems worse each time you do that.
I use apt-get purge openmediavault-flashmemory and reboot
You shouldn't be uninstalling the folder2ram plugin. The new version of the flashmemory plugin does that at the appropriate time.
As stated, I'm using the command you posted earlier in this thread
I don't want users to have to use the command line to upgrade to the zram version.
If there's an alternative I'll do that
-
I can't ask any more questions
I'm happy to test Arron, I'll reinstall when you tell me what you need to know
-
I don't know what this means.
Initially when I installed the beta, htop represented swap in use for the beta plugin.
It stopped doing that and there was a marked increase in ram for routine use. You may be right and services were woking as normal but something changed that caused htop to stop showing swap.
I've gone back and forth between the beta and the old plugin and it sure seems as though the beta's no longer working for me.
There are also errors uninstalling folder2ram, unable to stop services in use was the error from memory (though once purged the plugin shows as no longer installed).
-
The plugin is configured with these folders
Plugin config looked normal, same as when it was working.
What do you mean
htop had been showing swap in use, same as it did with the regular folder2ram plugin
