Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

different size for different paths? (feature request?) #143

Open
zadigre opened this issue Jan 14, 2021 · 5 comments
Open

different size for different paths? (feature request?) #143

zadigre opened this issue Jan 14, 2021 · 5 comments

Comments

@zadigre
Copy link

zadigre commented Jan 14, 2021

beside /var/log, I also have one other folder that is managed by log2ram.
I need a little bit more space for this folder... so I set size to 512M.... but that means /var/log is also taking 512M.
is there a way to set /var/log to a smaller size while keeping my other folder to 512M?

@MegaV0lt
Copy link
Contributor

MegaV0lt commented Jan 15, 2021

Increasing size should be not problematic, since memory is only used as needed. See:
https://wiki.archlinux.org/index.php/Tmpfs#Examples

@zadigre
Copy link
Author

zadigre commented Jan 19, 2021

Increasing size should be not problematic, since memory is only used as needed. See:
https://wiki.archlinux.org/index.php/Tmpfs#Examples

yes I understand that... it's just my OCD that is ticked with I look at the free memory with the free command. 😉
but also, I've seen some swap usage... which I didn't see before even if my /var/log only had 11MB and my other path was like 60MB.
I configured log2ram with 256M instead of 512... and no swap usage so far.

@azlux
Copy link
Owner

azlux commented Jan 21, 2021

If you said you're swapping too fast, You can also check your swapiness See : https://www.howtoforge.com/tutorial/linux-swappiness/

@zadigre
Copy link
Author

zadigre commented Jan 21, 2021

oh great. thanks for the tip!
I didn't know this parameter exists.
and a quick search on google tells me that before it was at "1" on raspbian... and it was changed to the linux default "60" in 2017.

I changed it back to "1"... lets see how it goes in the next couple of days.

@thomas725
Copy link

I too would like to see this feature, even though defining too large doesn't take up more RAM than it needs, it would be nice if we could safeguard against folders that should be tiny to grow unexpectedly and clog up our RAM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants