Unix quota per user script

quotashell-scriptingunix

Is there any way to automate user's home folder qouta by script. I have auto useradd script, and I want to add code in script about quota for home folder of size 2 GB. For example:

edquota sally

    Disk quotas for user sally (uid 1045):
  Filesystem                   blocks       soft       hard     inodes     soft     hard

  /dev/loop0                       16       0           0          4        0        0

How to make command edqouta change value of hard limit from 0 to 2037760 by script? in other words how to modify edquota sally to automatically change value.

Best Answer

edquota is not really suitable for scripting.

quotatool handles quotas from the commandline. Easy to use in scripts. It's included in most major Linux distributions, and is also available for *BSD, Mac OSX, AIX and Solaris.

Related Solutions

Directories on Unix and Unix-like Systems – Understanding Their Meaning

For more data on the layout of Linux file-systems, look at the Filesystem Hierarchy Standard (now at version 2.3, with the beta 3.0 version deployed on most recent distros). It does explain some of where the names came from:

/bin - Binaries.
/boot - Files required for booting.
/dev - Device files.
/etc - Et cetera. The name is inherited from the earliest Unixes, which is when it became the spot to put config-files.
/home - Where home directories are kept.
/lib - Where code libraries are kept.
/media - A more modern directory, but where removable media gets mounted.
/mnt - Where temporary file-systems are mounted.
/opt - Where optional add-on software is installed. This is discrete from /usr/local/ for reasons I'll get to later.
/run - Where runtime variable data is kept.
/sbin - Where super-binaries are stored. These usually only work with root.
/srv - Stands for "serve". This directory is intended for static files that are served out. /srv/http would be for static websites, /srv/ftp for an FTP server.
/tmp - Where temporary files may be stored.
/usr - Another directory inherited from the Unixes of old, it stands for "UNIX System Resources". It does not stand for "user" (see the Debian Wiki). This directory should be sharable between hosts, and can be NFS mounted to multiple hosts safely. It can be mounted read-only safely.
/var - Another directory inherited from the Unixes of old, it stands for "variable". This is where system data that varies may be stored. Such things as spool and cache directories may be located here. If a program needs to write to the local file-system and isn't serving that data to someone directly, it'll go here.

/opt vs /usr/local

The rule of thumb I've seen is best described as:

Use /usr/local for things that would normally go into /usr, or are overriding things that are already in /usr. Use /opt for things that install all in one directory, or are otherwise special.

Linux – Check Environment Variables of a Running Process on Unix

cat /proc/<pid>/environ

If you want to have pid(s) of a given running executable you can, among a number of other possibilities, use pidof:

AlberT$ pidof sshd   
30690 6512

EDIT:

I totally quote Dennis Williamson and Teddy comments to achieve a more readable output. My solution is the following:

tr '\0' '\n' < /proc/<pid>/environ

Best Answer

Related Solutions

Directories on Unix and Unix-like Systems – Understanding Their Meaning

Linux – Check Environment Variables of a Running Process on Unix

Related Topic