-
Notifications
You must be signed in to change notification settings - Fork 759
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
default /var MFS can be too small for updates #243
Comments
fichtner
added a commit
that referenced
this issue
Jul 8, 2015
Remove the size settings for those mount points as a preparation, because tmpfs does not need an upper bound. Hardcode everything now, replace mfs with tmpfs in an upcoming commit.
fichtner
added a commit
that referenced
this issue
Jul 8, 2015
|
squid doesn't run / can't write into log with this -- I wonder if the old code had the same issue? |
fichtner
added a commit
that referenced
this issue
Jul 10, 2015
Remove the size settings for those mount points as a preparation, because tmpfs does not need an upper bound. Hardcode everything now, replace mfs with tmpfs in an upcoming commit.
fichtner
added a commit
that referenced
this issue
Jul 10, 2015
fichtner
added a commit
that referenced
this issue
Jul 10, 2015
fichtner
added a commit
that referenced
this issue
Jul 10, 2015
fichtner
added a commit
that referenced
this issue
Jul 10, 2015
|
Shipped!!1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Move /tmp and /var MFS to tmpfs so that we don't have to specify upper memory bounds anymore.
The text was updated successfully, but these errors were encountered: