Project

General

Profile

Actions

Bug #13479

open

RAM-Disk sizes are still verified when it's inactive

Added by Flole Systems 3 months ago. Updated 16 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Configuration Backend
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

When you disable/don't enable the RAM-Disk feature and then set insane limits it complains:

Combined size of /tmp and /var RAM disks would exceed available kernel memory.

It should not do that as it's not enabled, so whatever settings are entered there shouldn't matter.

In my case I always had the limits set to 4096 for both and the feature disabled. Now I tried to change something on the page and it started to complain. Also maybe someone wants to disable the RAM-Disk and temporarily run the device with less RAM without changing the limits so they can easily be set back to normal when more RAM is installed again.

Actions #1

Updated by Jim Pingle about 2 months ago

  • Plus Target Version changed from 22.11 to 23.01
Actions #2

Updated by Jim Pingle 16 days ago

  • Assignee set to Jim Pingle
Actions #3

Updated by Jim Pingle 16 days ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Flole Systems 16 days ago

Not entirely sure if this is a good idea as #13508 suggests that the check can be removed entirely as it's no longer coupled to kernel memory at all. It would be weird to write in the release notes first that it got fixed and then that it got removed entirely.

Actions #5

Updated by Jim Pingle 16 days ago

That's a separate issue, I'm taking things one at at time. While we evaluate the other, it's still safe to remove this check when it's not necessary.

Actions

Also available in: Atom PDF