Red Hat Bugzilla – Bug 19038
Linuxconf does not set quota
Last modified: 2007-04-18 12:29:19 EDT
Although it is possible to set default quota and user/group quota values
in linuxconf (they are obviously stored and displayed in linuxconf even
after reboot) and the filesystems are mounted correctly (with enabled
quota), they are not reported by repquota or quota. There are no changes
in quota.user or quota.group after running linuxconf.
This bug is also true for a system running the updated verions of:
Quota checking seems to work manually (using edquota).
So perhaps there is a bug in linuxconf???
I'm seeing similar problems.
The default quota (as set under File systems/Set quota defaults) appears in
/etc/quota.conf but does not seem to take effect for any new users. In fact it
may not have since a previous upgrade to RedHat 6.x from 6.0 as I've only just
noticed the problem.
From what I can tell reading man pages, etc this default quota is a feature of
linuxconf rather then the quota package and it appears that when creating a new
user or editing an existing user linuxconf is not applying the default quota.
Any feedback/info will be most appreciated. I'll also attempt to pursue this
issue in the linuxconf mailing list I'm about to subscribe to.
The problem I was having has now 'fixed itself'. Possibly by me editing and
then resetting the default quota or by creating a user with a different quota
and then deleting them.
Either way there would seem to have been a bug that has now been worked around.
LABEL support for quota was added to Linuxconf for 1.22, which could explain why
you had a problem with older linuxconf versions on RH7.0
One can't upgrade directly to linuxconf-1.24r8 because of dependencies:
error: failed dependencies:
libncurses.so.4 is needed by linuxconf-1.24r8-1
libpng.so.2 is needed by linuxconf-1.24r8-1
libstdc++-libc6.1-1.so.2 is needed by linuxconf-1.24r8-1
Redhat needs to address this with a completely patched RPM.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.