Hi. I'm jon.404, a Unix/Linux/Database/Openstack/Kubernetes Administrator, AWS/GCP/Azure Engineer, mathematics enthusiast, and amateur philosopher. This is where I rant about that which upsets me, laugh about that which amuses me, and jabber about that which holds my interest most: *nix.
The unix philosophy is not strong in this one.
Posted 11-16-2012 at 01:03 PM by rocket357
I took my RHCSA test today (non-official pre-test). I finished all ~20 objectives in 30 minutes, minus one objective regarding quotas. Hrmmm...can't seem to recall the quota init command (and I've never really used Linux quotas before...this may get interesting). No worries, man -k to the rescue!
man -k quota
Well, ok, there are the commands for managing quotas, checking quotas, reporting on quotas, etc...but no "set up quotas". See, when I try to run any quota commands, I get "Could not find aquota.user on this filesystem" (something to that effect, and I'm a bit too paranoid to blindly "touch aquota.user", and I'm trying to keep this realistic to what the actual test will be like, so no googling! At this point I'm still holding out hope, though I know Linux man pages are severely lacking compared to OpenBSD man pages), so I man -k aquota and hold my breath...
Same list. Hrmmm.
man -K quota? No dice.
man -K aquota? Still no joy.
Ok, bruteforce time (because, you know, that's the one algorithm that is guaranteed to work?). man -K quota, read each man page from top to bottom. Ahh, quotacheck! Wait, quota...*check*? So I use "quotacheck" to create the files? Really?
I wonder if I could run "service httpd check" to create a default apache config...hrmmm. Didn't work.
What if I run "make check" to create binaries? Not happening.
Maybe we should rename "init" to "check"? Linus likely would not agree...but it does "sorta" make sense...check if the first process exists, and if not, create it?
Maybe the PostgreSQL project could rename initdb to checkdb?
No, I know...we should rename "fork" (you know, since it creates something) to "check". "Har har, I set off teh checkbomb in ur serverz"
Sigh.
man -k quota
Well, ok, there are the commands for managing quotas, checking quotas, reporting on quotas, etc...but no "set up quotas". See, when I try to run any quota commands, I get "Could not find aquota.user on this filesystem" (something to that effect, and I'm a bit too paranoid to blindly "touch aquota.user", and I'm trying to keep this realistic to what the actual test will be like, so no googling! At this point I'm still holding out hope, though I know Linux man pages are severely lacking compared to OpenBSD man pages), so I man -k aquota and hold my breath...
Same list. Hrmmm.
man -K quota? No dice.
man -K aquota? Still no joy.
Ok, bruteforce time (because, you know, that's the one algorithm that is guaranteed to work?). man -K quota, read each man page from top to bottom. Ahh, quotacheck! Wait, quota...*check*? So I use "quotacheck" to create the files? Really?
I wonder if I could run "service httpd check" to create a default apache config...hrmmm. Didn't work.
What if I run "make check" to create binaries? Not happening.
Maybe we should rename "init" to "check"? Linus likely would not agree...but it does "sorta" make sense...check if the first process exists, and if not, create it?
Maybe the PostgreSQL project could rename initdb to checkdb?
No, I know...we should rename "fork" (you know, since it creates something) to "check". "Har har, I set off teh checkbomb in ur serverz"
Sigh.
Total Comments 0