Ticket #558 (closed defect: fixed)
Your locker might not be in the attachtab when you run quota
| Reported by: | geofft | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Fall 2010 |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
jesstess tried running quota -v on kid-icarus and didn't see any results. It started working after running attach jesstess.
We should somehow ensure that your home directory shows up in the output of quota -v by default. The lame way is to run attach $USER at the top of the quota command (which might get confusing if you've explicitly attached something other than your actual filsys pointer at /mit/$USER).. The other lame way is to block until attach gets rewritten (#227). Maybe there's a non-lame way.
Change History
comment:2 Changed 14 years ago by jdreed
#227 is not happening anytime son. I vote we attach the user's homedir in the default dotfiles, or something. Alternatively, we could rewrite quota so it doesn't use liblocker.
comment:3 Changed 14 years ago by jdreed
So, there are a couple of solutions here:
a) attach the user's homedir in the default dotfiles
b) Run "fs lq" in /usr/lib/init/quotawarn
c) Rewrite quota so it doesn't use liblocker
That's probably the right order of simplicity, too.
comment:4 Changed 14 years ago by broder
I think attaching the user's homedir in the default dotfiles right around where we mess with $HOME is a perfectly good solution until someone gets around to dealing with #227.
comment:5 Changed 14 years ago by jdreed
- Status changed from new to proposed
Fixed in r24770/r24771; built and uploaded to proposed
This is probably a side effect of the pam_afs_session change (#136/r24443), which means that this broke pretty recently. Since people do expect to be able to run quota / quota -v, and I think OLC tells people to, I'm going to raise the priority.