Lines Matching full:be

13 .\"    may be used to endorse or promote products derived from this software
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
52 Quotas may be set for each individual user, on any, or
62 \s-2VMUNIX\s0 that may be included when the
68 To most users, disc quotas will either be of no concern,
69 or a fact of life that cannot be avoided.
75 There are two individual possible quotas that may be
76 imposed, usually if one is, both will be.
77 A limit can be set on the amount of space a user
78 can occupy, and there may be a limit on the number
92 he will be warned.
93 The hard limit cannot be exceeded.
97 this occurs, a message will be written to the user's
99 Only one message will be output, until space occupied
105 his soft limit, he will be warned, and his login
112 particular limit that has been exceeded will be treated
114 more resources will be allocated to the user.
131 the editor be aborted without correctly writing the
132 file not only will the recent changes be lost, but
146 the file can be moved back to the filesystem
152 there are several steps necessary to be performed
155 First, the system must be configured to include
169 quotas applied needs to be made.
171 or other user files, will need to be subjected to
174 If possible, \fB/tmp\fP should usually be free of quotas.
176 Having decided on which filesystems quotas need to be
179 should be done is (way) beyond the scope of this document.
183 command can be used to actually set the limits desired upon
184 each user. Where a number of users are to be given the
186 to edquota will allow this to be easily accomplished.
189 must be informed to enforce quotas on the desired filesystems.
207 Should quotas need to be disabled, the
209 command will do that, however, should the filesystem be
210 about to be dismounted, the
217 will not be disabled if the umount would fail
222 in the quota file should be checked for consistency with
227 command can be used to accomplish this.
240 command may be used to check the usages and limits for
246 filesystem that the quotas are to be applied to.
251 choosing any other name would not be wise.
257 in it, which would be lost by copying, so it is best to
269 In most cases this information will be retained in core,
276 released data can be easily reclaimed.
308 subject to change to be considered for distribution.