We've been receiving messages from this domain at unblock(a)toolserver.org
and they appear to be related to this:
<http://www.reddit.com/r/WTF/comments/l44r1/i_just_got_this_email_at_work_i_…>.
Viral advertising for some film. In reality, it's a message with a
crapload of images attached serving no purpose for us.
Can we just block this whole domain from sending mail to toolserver
accounts? It's a nuisance, and the messages are quite large.
--
Chris Howie
http://www.chrishowie.comhttp://en.wikipedia.org/wiki/User:Crazycomputers
If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/
PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5
------------------------------------------------------------------------
IMPORTANT INFORMATION/DISCLAIMER
This document should be read only by those persons to whom it is
addressed. If you have received this message it was obviously addressed
to you and therefore you can read it.
Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.
This overrides any disclaimer or statement of confidentiality that may
be included on your message.
Hello all,
yesterday Merlissimo and I successfully tested the installation of the SGE-
version for the toolserver. The last step is now to install the new version on
the live-system. For that, the SGE-service needs to stop completely on the
cluster, the old version has to be removed and the new one has to be
installed. We plan to to this on
Thursday 5. July between 17:30 and 22:30 UTC.
During this time no SGE will work. There will be no restarting (and no
migration) of stopped things after the update.
After the update is done, we will start to use the 2 Linux-boxes for tools too
(I will send details than).
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
I was taking a look at our dumps in user-store and none of them are
compressed, and I was socked about that. I know a lot of people use
pywikipedia to parse the dumps, and I know it can handle the bz2 files. any
reason we dont just make them all bz2?
John
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all!
I have a bunch of cronie jobs calling qcronsub for several times
with very similar settings (just the language of the wiki used
changes). In total there are 5 jobs - regurarly (about ever 2nd
day) one of those jobs does not get executed and it is always the
same one. I do not get any error mail. Any idea?
Thanks a lot and greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/a+QYACgkQAXWvBxzBrDD5VQCgox3+fPvOxE1CLry5pdA7AMx8
bDQAnjfAsdLAcykRA5j8lyicyVdk8xYC
=UeJJ
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello everybody!
I experience a behaviour with SGE that I cannot understand.
Due to logging my scripts output I redirect stdout and stderr.
When running the script from console (e.g. on willow) all
write actions to stderr are passed as they are, but runned
through qcronsub (SGE) results in all writes splitted up at
newlines '\n' as if there was some kind of auto-flush in
background? Changing the usage of param 'j' in SGE did not
help. I am using python. Is there something in qcronsub that
has in influence to this? Any idea?
Thanks a lot and greetings!
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/XmR4ACgkQAXWvBxzBrDCkJgCdFXFTxWbkHn4RR8s9/RBrouzj
Jz0AmwT+Jo4bYwjm+0nybGu5o+Vq+iaK
=YYoN
-----END PGP SIGNATURE-----
Hello all,
the resources on the TS are free, but limited; so we all have to use the
resources fair. Some limits (like memory-usage) are set and controlled by the
system, but others are not and it is in the responsibility of every single
user to make sure to not mis- or overuse resources.
So it is for example NOT a good idea to run 200 processes in parallel to get
more CPU-resources than you would normally get. And it is not a good idea to
use a amount of memory which is just below the slayer-daemon-limit without any
purpose.
Sincerely,
DaB.
P.S: It is totally in the rules to disable a user-account because of resource-
misusing.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello admins!
I opened TS-1360 [1] quite some time ago. Would it be possible to
install those libs or is there any serious issue? The bot using
this is now ready-to-use and should be runned from TS now.
[1] https://jira.toolserver.org/browse/TS-1360
Thanks a lot for your effort and time!
Greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/XmRQACgkQAXWvBxzBrDByEACgqVKs7f6e7AvU4yZET6UHuel9
NpQAoJzAtK4o0rCv1xxksRY+phG3aGoT
=pzAw
-----END PGP SIGNATURE-----
Hello all,
I was asked by various Wikimedia-projects about details of the new no-
interwiki-bots rule; I will try to clarify some parts of it in this mail.
For first: The default interpretation of the rule is: no interwiki-bots. The
rule forbids the running of any interwiki-bot on the toolserver, if there is
no exception that permits the running.
The most important exception is the MMP interwikibot, which is lead by
Toto Azéro at the moment. The MMP is allowed to run several instances of
interwiki-bots and should cover every wikimedia-project in a fair manner.
Until rules are work out there will be no addings of other users to the MMP
(it would be great if the TS-users would work out the rules).
Another exception is the creation of a better interwiki-bot and the test-
running of it; an example is the new bot by Merlissimo. The test has to happen
in a MMP. Of course running the newest pythonwikibot for "testing" is NOT
subject of this exception (as long as it not the pywikipedia-MMP).
The last exception is the non-continuous-mode: That's NOT "Only 1 time per
week/day/hour".
Let's give a example what is covered by this exception: You are working in the
Italian Wikipedia and notice that an interwiki-link in an article points to
the wrong article in the English Wikipedia. You correct the interwiki-link,
but there a dozen of articles in other languages where the link is still wrong
– much boring work for a human. Here is it ok to run a interwiki-bot on the
toolserver to fix this fast.
Another example would be the correcting of hundreds of articles because a
Wikipedia-subproject re-organized the name-structure of a article-group.
What I had in mind as I declared this exception is, that the number of
articles the bot will correct is finite and the run-time of the bot is somehow
short.
What is not an exception:
*Running a bot in screen instead by cron or SGE
*Running a bot only "some time when my home-computer sleeps"
*Running a bot because "my Wikipedia is special"
There may be other valid exception or reasons to run a interwiki-bot; if you
plan to do this: open a JIRA-ticket and the roots will look at it (every TS-
user can leave a comment for course).
If there a further questions please ask on the ML or in the IRC.
Sincerely,
DaB.
P.S: You an substitute "interwiki" with "interlanguage" in this mail.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hello all,
at Thursday, 26th June, between 11:30 and 16:30 UTC we will have a general
maintenance-window.
The main-reason for the maintenance-window is to install Solaris-updates. We
will reboot the Solaris-boxes after the updates are done – this INCLUDES
willow so please ensure that you have no open files anywhere on the cluster.
The reboots will be announced on the server 15mins before they happen, so you
will have a warning. In the past some reboot-cron-scripts were not executed
after a reboot so you should check that when the maintenance-window is over.
Another topic will be the update of JIRA and fisheye, so these services will be
away for some time during the maintenance-window.
Sincerely,
DaB.
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885