README 2.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. pam_setquota — PAM module to set or modify disk quotas on session start
  2. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  3. DESCRIPTION
  4. pam_setquota is a PAM module to set or modify a disk quota at session start
  5. This makes quotas usable with central user databases, such as MySQL or LDAP.
  6. OPTIONS
  7. fs=/home
  8. The device file or mountpoint the policy applies to. Defaults to the
  9. filesystem containing the users home directory.
  10. overwrite=0
  11. Overwrite an existing quota. Note: Enabling this will remove the ability
  12. for the admin to manually configure different quotas for users for a
  13. filesystem with edquota(8). (Defaults to 0)
  14. debug=0
  15. Enable debugging. A value of 1 outputs the old and new quota on a device. A
  16. value of 2 also prints out the matched and found filesystems should fs be
  17. unset. (Defaults to 0)
  18. startuid=1000
  19. Describe the start of the UID range the policy is applied to. (Defaults to
  20. UID_MIN from login.defs or the uidmin value defined at compile-time if
  21. UID_MIN is undefined.)
  22. enduid=0
  23. Describe the end of the UID range the policy is applied to. Setting enduid=
  24. 0 results in an open-ended UID range (i.e. all uids greater than startuid
  25. are included). (Defaults to 0)
  26. bsoftlimit=19000
  27. Soft limit for disk quota blocks, as defined by quotactl(2). Note:
  28. bsoftlimit and bhardlimit must be set at the same time!
  29. bhardlimit=20000
  30. Hard limit for disk quota blocks, as defined by quotactl(2). Note:
  31. bsoftlimit and bhardlimit must be set at the same time!
  32. isoftlimit=3000
  33. Soft limit for inodes, as defined by quotactl(2). Note: isoftlimit and
  34. ihardlimit must be set at the same time!
  35. ihardlimit=4000
  36. Hard limit for inodes, as defined by quotactl(2). Note: isoftlimit and
  37. ihardlimit must be set at the same time!
  38. EXAMPLES
  39. A single invocation of `pam_setquota` applies a specific policy to a UID range.
  40. Applying different policies to specific UID ranges is done by invoking
  41. pam_setquota more than once. The last matching entry defines the resulting
  42. quota.
  43. session required pam_setquota.so bsoftlimit=1000 bhardlimit=2000 isoftlimit=1000 ihardlimit=2000 startuid=1000 enduid=0 fs=/home
  44. session required pam_setquota.so bsoftlimit=19000 bhardlimit=20000 isoftlimit=3000 ihardlimit=4000 startuid=2001 enduid=3000 fs=/dev/sda1
  45. session required pam_setquota.so bsoftlimit=19000 bhardlimit=20000 isoftlimit=3000 ihardlimit=4000 startuid=3001 enduid=4000 fs=/dev/sda1 overwrite=1
  46. AUTHOR
  47. pam_setquota was originally written by Ruslan Savchenko <savrus@mexmat.net>.
  48. Further modifications were made by Shane Tzen <shane@ict.usc.edu>, Sven Hartge
  49. <sven@svenhartge.de> and Keller Fuchs <kellerfuchs@hashbang.sh>.