05.08.2013 Views

[PDF] Parallels Server 5 Bare Metal

[PDF] Parallels Server 5 Bare Metal

[PDF] Parallels Server 5 Bare Metal

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Managing Resources<br />

Turning On and Off Second-Level Quotas for a Container<br />

The parameter that controls the second-level disk quotas is QUOTAUGIDLIMIT in the Container<br />

configuration file. By default, the value of this parameter is zero and this corresponds to disabled<br />

per-user and per-group quotas.<br />

If you assign a non-zero value to the QUOTAUGIDLIMIT parameter, this action brings about the<br />

two following results:<br />

1 Second-level (per-user and per-group) disk quotas are enabled for the given Container.<br />

2 The value that you assign to this parameter will be the limit for the number of file owners and<br />

groups of this Container, including Linux system users. Notice that you will theoretically be able<br />

to create extra users of this Container, but if the number of file owners inside the Container has<br />

already reached the limit, these users will not be able to own files.<br />

Enabling per-user and per-group quotas for a Container requires restarting the Container. The<br />

value for it should be carefully chosen; the bigger value you set, the bigger kernel memory overhead<br />

this Container creates. This value must be greater than or equal to the number of entries in the<br />

Container /etc/passwd and /etc/group files. Taking into account that a newly created Red<br />

Hat Linux-based Container has about 80 entries in total, the typical value would be 100. However,<br />

for Containers with a large number of users, this value should be increased.<br />

When managing the QUOTAUGIDLIMIT parameter, keep in mind the following:<br />

• If you delete a registered user but some files with their ID continue residing inside your<br />

Container, the current number of ugids (user and group identities) inside the Container will not<br />

decrease.<br />

• If you copy an archive containing files with user and group IDs not registered inside your<br />

Container, the number of ugids inside the Container will increase by the number of these new<br />

IDs.<br />

The session below turns on second-level quotas for Container 101:<br />

# pctl set 101 --quotaugidlimit 100 --save<br />

Unable to apply new quota values: ugid quota not initialized<br />

Saved parameters for Container 101<br />

# pctl restart 101<br />

Stopping Container ...<br />

Container was stopped<br />

Container is unmounted<br />

Starting Container ...<br />

Container is mounted<br />

Adding IP address(es): 192.168.1.101<br />

Hostname for Container set: ct101<br />

Container start in progress...<br />

120

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!