I need to change some mount options for parts of the root filesystem, such as /tmp /var and /home (add nodev,nosuid and quota), but I haven't ability to make a separate partition and I have not enough RAM to mount /tmp as tmpfs. I've tried mount -o bind,noexec,nodev,nosuid /tmp /tmp, but it seems not working because after that I still can exec files from /tmp and make device nods on it. Is there other way to do that?
When sending large email to a new CentOS6 server running Postfix as the MTA, the following message is returned:
tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 5.3.4 Error: message file too big (state 18)
I found the following suggestion, but am unclear as to where it needs to be added in the main.cf
file:
This was caused by Postfix and it's limit on not only messages but mailbox sizes.
I had to add this setting in
/etc/postfix/main.cf
:
message_size_limit = 31457280
How can the maximum mail size (including attachments) be increased in Postfix?
I have following scenarios:
Single partition mounted as /, with lots of disk space.
There is a range of directories (/pg/tbs1, /pg/tbs2, /pg/tbs3 and so on), and I would like to limit total size of these directories.
One option is to make some big files, and then mkfs them, and mount over loopback, and then set quota, but this makes expansion a bit problematic.
Is there any other way to make the quota work per directory?
My host's backup server gives me my usage information in the following format:
Disk quotas for user vps**** (uid 1234): Filesystem blocks quota limit grace files quota limit grace /dev/mapper/backup3-backup3 6094452 2147483648 2147483648 365672 0 0
I've searched, including in man pages, but I can't figure out how to read the output. What do each of these columns mean? IIRC, my quota should be 10 GB.
I think this is one area that is a pain for every sysadmin.
Users don't really know how much storage space they are using, and don't take the time to manage what is stored there, or how long it stays around.
What policies does your company implement to keep networked disk space under control?