Hi all
I'm happy to let you know that new hardware has been ordered by Wikimedia
Deutschland and will arrive probably in about two weeks. We will get two new
systems:
* A more powerful web server, to replace hemlock: Sun Fire X4150, 2x Quad-Core
Xeon, 8GB RAM, 2x73GB SAS HDD. The current web server only has two cores.
* Another database server, to be used for S1 (english wikipedia), so S1 and S3
no longer have to share a server: Sun Fire X4250, 2x Quad-Core Xeon, 32GB RAM,
16x146GB SAS RAID.
This should improve performance and give us some head space for growth. Once the
new servers arrive, S3 will be re-imported too, so we will have live data again.
Any ideas for names? To stay with the nightshade theme, how about Jurubeba and
Erubia? Or perhaps we go the "witches' weed" way, with Datura and Mandrake?
Henbane is taken, i think. Amanita sounds nice, too :)
A third server has been ordered, which will also be installed in Amsterdam, but
will not be part of the toolserver cluster. It's a storage server (X4540, 24TB
RAID) that will keep a live backup of all media files.
Cheers,
Daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Several Perl and Python modules have been upgraded on the Solaris
servers; a full list of upgrades is available at
<https://jira.toolserver.org/browse/MNT-606>.
Additionally, Perl 5.12 has been installed. This can be tested using
/usr/bin/perl5.12; if there are no problems, it will become the default
perl shortly.
Some modules are not currently available for Perl 5.12, such as RRDTool and
Graphviz. These will become available before the default is changed.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkwDP+YACgkQIXd7fCuc5vKzTQCgut3RpQEVU5PJrvGfjqH2StzK
Pz0AnA8+KAV6CZ5jEPJqkToKsrLDKM4C
=QnG/
-----END PGP SIGNATURE-----
Hello folks,
at first of June, the toolserver-accounts will expire again. If you need your
account further, please send an eMail to
ts-accounts201001(a)dabpunkt.eu
before this date. The eMail should contain your login-name in the subject and
in the body. Please do NOT send the eMail to this mailing-list; write a NEW
eMail, DON'T use the answer-function of your eMail-client (because it will
send the eMail to this mailinglist). If you send the eMail to the mailinglist,
you will get the "Can't use his/her eMail-client"-price (and some jokes from
the regulars) and NO extending.
This time, I will use our wiki to list account-names for which I got an email
for (see [1]) — please be a little bit patient after you sent me the email.
Maybe I will also send lists per mail too.
Please notice that tools of expired users will be disabled, so if you plan to
not extent your account, make sure that you transfer your tools to another ts-
user before 1. June.
We hope that this is the last time that we use email for account-extending and
that we can use something new next time.
If you have questions, please use the TS-Maillinglist.
Sincerly,
DaB.
[1] https://wiki.toolserver.org/submit/Account-Extending_2010-01
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Hi all,
I was asked for a tool (which I wrote), but re-thinking of it I'm not
totally sure it complies with toolserver's rules. Can I have your
opinion please ?
Basically, this is some sort of topic-based editcounter, which fetches
the 10 users who contributed the most on the given theme, and does put
it in a table like this[1] (for the Mascarene Islands topic in this
example).
Columns are 'username', 'editcount', 'number of distinct pages'.
Thanks in advance,
stan.
[1] http://fr.wikipedia.org/w/index.php?title=Utilisateur:HAL/Test50&oldid=5380…
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
There is a discussion on enwiki [1] which concerns bots editing while
logged out. The proposal is to block the toolserver IP range to prevent
this from happening -- however, this shouldn't be necessary since bots
should never edit while logged out.
Bot frameworks should help bot operators and authors by using an edit
assertion [2] - is anyone aware of a framework which /doesn't/ do that?
So, this is a reminder to please take care when writing scripts: check
if your framework handles this for you, and if not, be sure to write
your bot such that it edits only while logged in.
If the toolserver IP range does end up being blocked, is anyone aware of
read-only tools which would be adversely affected by the IP being
blocked? Such tools are poorly designed, and their authors should fix
them sooner rather than later, even if the block isn't placed in the end.
- -Mike
[1]
http://en.wikipedia.org/?oldid=364741979#Proposal_to_softblock_Toolserver_I…
[2] http://www.mediawiki.org/wiki/Extension:Assert_Edit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkwDPWUACgkQst0AR/DaKHtTlACfW8XWbH/Pi1Yh1ExkaHVhabLa
+y0AnRBSsHt7QYcWbUcPu4rANySCkFO2
=989j
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We have now introduced the concept of a default license for each
account. This is documented on the wiki:
<https://wiki.toolserver.org/view/Default_license>.
In the future, selecting a default license will be required at account
creation time (for new account), and at the next account renewal time
(for existing accounts). I suggest people set their license now rather
than leaving it until then.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkv6lXEACgkQIXd7fCuc5vLl0wCgvNuZiswGiH9xJg9IFZc5fkNG
wTgAn35BkatTtn4IgVjFLkZJ1YSgnaP9
=Ch03
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
It is now possible to reset your LDAP password automatically if you have
an LDAP email address set. To do this, run "resetpass".
However, this only works if you have an LDAP email address configured.
All new accounts have this by default, but older accounts may not. To
set your LDAP email address, run "setmail". This will tell you if you
have an email address set or not, and let you set one if you don't.
Once you set your LDAP email address, we recommend replacing your
.forward file like this:
$ echo USERNAME(a)toolserver.org >$HOME/.forward
This will avoid having to update your email address in two places.
There is no requirement that you set an LDAP email address. However, if
you don't, you will not be able to reset your LDAP password if you
forget it. LDAP passwords will be used for more things in the future,
including account renewals.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkv8EHwACgkQIXd7fCuc5vJIPQCgvbmzshQpPIRahgINrZR18yAF
WhYAnifSDlMafycJ9S35bbojMLCfoE0y
=F5/S
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've rewritten these two utilities to improve security. The new
versions depend on OS-specific features to work, and rather than
duplicate code (which is likely to introduce security issues), I chose
to drop Linux support. These tools are therefore only available on
Solaris login servers (e.g. willow) from now on.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkv8fBQACgkQIXd7fCuc5vKBLwCfXVNHPy9HAcgQNf2yeYK+MeXz
FL8An2168XJSBibxScH5LDexj9K61ZnU
=8dNl
-----END PGP SIGNATURE-----
Hello all,
I updated the kernel of nightshade a few minutes ago and now it needs a
reboot. So I will reboot nightshade arround 22:15 UTC. The downtime should be
quite low (few minutes) if no problems occure. You can follow the process at
[1] if you like.
Sincerly,
DaB.
[1] https://jira.toolserver.org/browse/MNT-593
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885