In user management on Linux we can actually set various access restrictions and activities that can be done. But in a VPS we usually use the entire resourcenya own and take root, so setting the default limit of template operating system even block our work later.
Well … we as users certainly have a way to see what are the limits that have been applied, stay you type this command:
ulimit
And if this message comes up afterwards:
unlimited
Be careful trapped because this does not mean completely unlimited / unlimited. Try running again but with additional parameters:
ulimit -a
It will be replied with more detailed information about Linux user limit:
core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 7972 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65536 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 7972 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Now you will know which one is really unlimited (or it can be said we can use the resources as much as our server specification) and which are still limited also how big the quota. And of course for some types of user limits there can be modified to be larger or smaller depending on your needs. Usually the most frequent errors are due to the small open file value so the process that wants to access multiple files simultaneously becomes obstructed.
