Krinkle <krinklemail(a)gmail.com> wrote:

UNIX has a good infrastructure to do that already. See limit(1), setrlimit(2).  Actually Solaris (in comparison to Linux) is much more flexible in working with resource assignement for projects. What could be done is to set "soft" memory, number of processes, maximum running time of a process and other limits by default. Users, if there is a legitimate need, could raise those limits themselves (like, "I need 2GB of RAM for my PHP process to run MediaWiki unittests now"). Right now I don't see any limits on willow: willow$ ulimit -a time(seconds)        unlimited file(blocks)         unlimited data(kbytes)         unlimited stack(kbytes)        10240 coredump(blocks)     unlimited nofiles(descriptors) 256 vmemory(kbytes)      unlimited If this would be abused, "hard" limits can be introduced, which cannot be overriden by user. Also, system accounting could also be enabled (see sar(1), sar(1M)) to regularly report on all resources used by users in the system. Process accounting (see acct(1M)) also provides a valuable information about what was run by users and when. Solaris has even ready cron scripts to prepare daily reports to summarize the information and send them by email. //Saper _______________________________________________ Toolserver-l mailing list (Toolserver-l(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette

There have been arrangements with some projects that need a lot of space by nature, like mine, The WikiMiniAtlas. But loging in today for the first time I received a quota warning with an ultimatum to free space within 4.9 days. Since when is that active?

Daniel

#!/usr/bin/env python

# http://www.alecjacobson.com/weblog/?p=1039

import subprocess, re, smtplib, email.mime.text

quota = subprocess.Popen("quota -v", shell=True, stdout=subprocess.PIPE).stdout.read() size = re.findall("[\d\.]+", quota) percent = float(size[1])/float(size[2]) * 100

# if the percentage is a above some threshold then send an email if (percent > 90.): # sender's and recipient's email addresses FROM = "drtrigon(a)toolserver.org" TO = ["dr.trigon(a)surfeu.ch"] # must be a list # Create a text/plain message msg = email.mime.text.MIMEText(quota) msg['Subject'] = "!QUOTA! %.1f%%" % percent msg['From'] = FROM msg['To'] = ", ".join(TO) # Send the mail server = smtplib.SMTP("localhost") server.sendmail(FROM, TO, msg.as_string()) server.quit()

qcronsub -l h_rt=00:05:00 -l virtual_free=50M -m as -j y -b y -N maintenance $HOME/warnuserquota.py >/dev/null

Is this also supposed to solve TS-1317 [1]??

[1] https://jira.toolserver.org/browse/TS-1317

Thanks and greetings! DrTrigon

On 16.05.2012 21:31, DaB. wrote: > Hello At Wednesday 16 May 2012 21:28:30 DaB. wrote: >> There have been arrangements with some projects that need a >> lot of space by nature, like mine, The WikiMiniAtlas. But >> loging in today for the first time I received a quota >> warning with an ultimatum to free space within 4.9 days. >> Since when is that active?

> the quota-service is active since years, but to tell the true > not for everybody because there are some bugs in the system. > The roots plan to fix this on short-term-base and we will send > another mail about this in the next days; but it should not > affect you yet. But nevertheless: if you need more disc-space > for some reason: Open a jira-bug and you will (most likely) get > it.

>> Daniel

> Sincerely, DaB.

> _______________________________________________ Toolserver-l > mailing list (Toolserver-l(a)lists.wikimedia.org) > https://lists.wikimedia.org/mailman/listinfo/toolserver-l > Posting guidelines for this list: > https://wiki.toolserver.org/view/Mailing_list_etiquette

_______________________________________________ Toolserver-l mailing list (Toolserver-l(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette