hello,
after a broken mailer caused hemlock to be CBL-listed, i have
disallowed outgoing SMTP (port 25) connections. if you want to send
mail, you should use /usr/lib/sendmail (like a normal UNIX program), or
speak SMTP to localhost (which is allowed and will accept your mail).
- river.
hello,
disk quotas will be reinstated shortly. the default per-user soft quota will
be 256MB. the hard quota will be 512MB. the grace period will be one
week.
this works as follows: your disk space usage should be below 256MB.
however, if you temporarily need more space, you can use more, up
Misza13:
What about automatic notifications/warnings of excessive usage?
Will they be set up as well or should we write our own scripts?
there will be some sort of automatic notification, both on login and by
mail.
- river.
signature.asc
Description: Digital signature
hello,
it's now possible to connect to a database server using names of the
form database-p.db.ts.wikimedia.org, for example:
enwiki-p.db.ts.wikimedia.org
roa-rupwiki-p.db.ts.wikimedia.org
these resolve to the database server holding that database. the sql-s*
aliases still work as well.
hello,
i wrote a short script: sql. now you can run sql enwiki_p on the
command line and it'll automatically connect you to the right database.
- river.
signature.asc
Description: OpenPGP digital signature
___
Toolserver-l mailing list
hello,
a replicated commonswiki_p is now available on yarrow (sql-s1/sql-s3) as
well as zedler (sql-s2).
- river.
signature.asc
Description: OpenPGP digital signature
___
Toolserver-l mailing list
Toolserver-l@lists.wikimedia.org
Sean Whitton:
My only tool that uses MySQL properly is coughing and throwing my
hastily scribbled error code from the status file that s2 is down.
What's wrong with it?
it's not down. WARN is only a warning (which you could display to your
users, if you like), not an error.
- river.
so it's fairly common that users want to host larger projects on the
toolserver, but for various reasons we haven't been comfortable doing that on
hemlock. i thought about this a bit, and came up with this:
http://meta.wikimedia.org/wiki/Toolserver/Special_projects
if you're interested, or
The Fearow:
Would this be an on application system where
you are allowed more than the standard memory/processor/etc limits?
yes, although obviously there are still limits based on available hardware.
Also,
to double check, this would be running a lot of intensive stuff and such?
not
Kalan:
Is it the problem only with large projects like that one requiring
Asterisk, while all other stuff will remain on hemlock?
anything that's currently allowed on hemlock would stay there.
- river.
pgpVqeNyV9IWq.pgp
Description: PGP signature
River Tarnell:
user databases will become read only tonight UTC while they are migrated to
a different server.
this is now finished.
- river.
pgpTU6u4h0I75.pgp
Description: PGP signature
___
Toolserver-l mailing list
Toolserver-l
hello,
1: JIRA and FishEye have moved to:
- https://jira.ts.wikimedia.org/
- https://fisheye.ts.wikimedia.org/
2: as an experiment i've set up a Confluence install at
http://confluence.ts.wikimedia.org (SSL also available). i don't know if
anyone's interested in using this for their
Kalan:
Could you change url's from /view/Page_name to traditional
/wiki/Page_name ?
that would give URLs like http://wiki.ts.wikimedia.org/wiki/Foo - i don't
really like the double repetition of wiki. i fixed the broken redirect,
though.
- river.
pgpjQtWwltrww.pgp
Nikola Smolenski:
Could you make translations of the former welcome page available somewhere
so that they could also be put on the wiki?
http://tools.wikimedia.de/startsite/
- river.
signature.asc
Description: This is a digitally signed message part.
Iradigalesc:
I can't confirm my email; The address is correct but I don't received any
mail when I registered my user at the wiki. Anyone had the same problem?
sorry, sendmail wasn't running. mail should be working now.
- river.
signature.asc
Description: This is a digitally signed
Simetrical:
Not unless you disappear for a while and your tools break, that is?
the correct way to solve this is to not have important tools owned by one
person, but by a set of maintainers.
- river
signature.asc
Description: This is a digitally signed message part.
Mohd Tarmizi:
What kind of content is allowed to be hosted at the httpd? Are
copyrighted materials OK?
of course, as long as you have permission to distribute them, and they follow
the rules (http://meta.wikimedia.org/wiki/Toolserver/Rules).
- river.
signature.asc
Description: This
Sean Whitton:
How about a web-based form that can do SELECTs?
it'll cause too much load, because people will run stupid or broken queries.
- river.
signature.asc
Description: This is a digitally signed message part.
___
Toolserver-l mailing
VasilievVV:
It uses LDAP, see http://wiki.ts.wikimedia.org/view/Special:Version.
the backend is LDAP, we also use a piece of middleware called Crowd
http://www.atlassian.com/software/crowd/.
- river.
signature.asc
Description: This is a digitally signed message part.
hello,
i'd like to enable creation of LDAP users from MediaWiki, but i need new LDAP
users to become members of some existing LDAP (not MediaWiki) groups. it
would be nice if this was possible :) (or maybe it is already, but i missed
the option.)
- river.
signature.asc
River Tarnell:
[snip]
sorry, this was meant to go to a different list.
- river.
signature.asc
Description: This is a digitally signed message part.
___
Toolserver-l mailing list
Toolserver-l@lists.wikimedia.org
http://lists.wikimedia.org
hello,
to justify buying a stable server, we need people willing to use it. so, if
anyone is interested in maintaining stable tools, please add your name
somewhere (i suggest [[m:Toolserver/Stable server/Candidates]] as a good
place). the initial proposal suggested at least two maintainers
James Hare:
stable as in stable versions?
http://meta.wikimedia.org/wiki/Toolserver/Stable_server
- river.
A: Because it disrupts the natural flow of conversation.
Q: Why is top-posting bad?
signature.asc
Description: This is a digitally signed message part.
i have borrowed ragweed from Wikimedia to do testing of the stable server on
(e.g. figuring out how things are going to work). so, if you're interested
in testing it, and have a candidate project, let me know...
- river.
signature.asc
Description: This is a digitally signed message
so not many people seem interested in moving their projects to the stable
server. are the requirements too strict, or do people just not see the need?
- river.
signature.asc
Description: This is a digitally signed message part.
___
Purodha:
Then I found that there is a user page in confluence which
displays an e-mail address of mine, which I thought I had entered
only in order to retieve a forgotten password, if need be.
It does show the e-mail address, even while I am logged out.
That means, the e-mail address is being
E:
I see that when looking at the wiki a few days ago, it said that the tool
we submit to the stable server will not be maintained by us, rather a
developer (of some kind).
the idea is that one of the developers would be the original owner of the
tool.
- river.
signature.asc
hello,
we have bought the domain toolserver.org with a view to using it for the
toolserver, e.g. http://toolserver.org/~username/. if anyone has any
comments (for/against), please say now.
- river.
signature.asc
Description: This is a digitally signed message part.
hello,
there will be some downtime Tuesday morning as changes are being made to
the knams network. the toolserver IPs will also change during this time.
- river.
___
Toolserver-l mailing list
Toolserver-l@lists.wikimedia.org
[EMAIL PROTECTED] wrote:
Presuming it's going to be widely used, we might as well plan it here --
anybody else have structural suggestions for the tool?
at the risk of starting a language argument, i'm against doing it in
PHP. i'd suggest Python:
* Lots of people know it (although perhaps
[EMAIL PROTECTED] wrote:
2) Can we, from the above list, also say which tools are the most
useful (ie. without which some projects would just break, I am
especially thinking Commons here)
possibly someone could, but not me ;)
We could probably get 10,000 lines of the
Mohd Tarmizi wrote:
I'm interested in providing a translation. I assume that the
translation files is in i18n/? What's i18n.properties? I've never seen
that kind of file (I'm not a Java programmer).
this is a Java properties file; when used for translation, it's quite
similar to MediaWiki
Kalan wrote:
This is not enough. 'Editstats for User' has do be more narrow
why?
and bars should be not higher than 15px, not 100px like now
i don't understand; the bars are 18px high at the moment, not 100px.
are you sure you're not viewing a cached version? what is the URL to
the image
Huji wrote:
But anonymous checkout doesn't let us to commit changes, does it?
no, because we don't want just anyone being able to commit ;-)
if you like, i can add you as a maintainer for it (experience with J2EE
would be a good prerequisite...)
- river.
signature.asc
Description:
hello,
some extended maintenance is currently taking place on the NFS server
for /home, so hemlock is offline. this shouldn't take more than a few
hours. i'll post a full explanation when it's finished.
- river.
signature.asc
Description: OpenPGP digital signature
Davide:
D Is there a method to limit the memory that a process have? So i am not
D rerunning it once every day?
you can't give a process less memory than it needs, it'll stop
working. in this case, i suggest asking the pywikipedia developers to
make their programs use a bit less memory.
-
Osama KM:
OK I'm learning C# at the moment ,and I guess running my C# bot on Windows is
OK too better (than Mono on Linux)
no, this shouldn't make any difference as far as i know. many people
run .NET programs under mono with no problems. (that is, after all,
one of the main purposes of .NET.)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brianna Laugher:
BL On 06/02/2008, River Tarnell [EMAIL PROTECTED] wrote:
any other comments? (please, avoid comments about why we
should/shouldn't use Windows.)
BL Why?
because the purpose is not to discuss whether we should do it, but
whether
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
once a month or so, someone complains that suddenly, ssh won't let
them log in. usually, this is because they made their home directory
world writable.
i have no idea what would possess someone to do this (since, among
other things, it would let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
anyone who has used hemlock to generate cryptographic keys (e.g. SSL
certificates or SSH keys), or used keys generated elsewhere on
hemlock, should be aware of this Debian security advisory:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Garrett:
Indeed. Server admin log says a tool was run to check for vulnerable
keys, and those users who had vulnerable keys were contacted
personally by Brion.
no, this was for the subversion server. Wikimedia admins don't touch the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl F?rstenberg:
but surely, can't all the keys people are using for logging in been
compromized?
i'm not sure what you're asking here. as far as i understand the problem,
using an SSH key to log into an affected server does not compromise the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Peeks:
I've copied dowkd.pl to /tmp on hemlock for those who'd rather copy it from
there than download a 4MB file over and over again :).
i'll reply to the rest of this mail later, but for now i'll just point out
that if you run random
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
per [0], i have disabled the authorized_keys of users with affected keys.
if you can no longer log into hemlock, you should contact [EMAIL PROTECTED]
and provide a new public key, generated on a system which is not using the
affected version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
to be clear: just because your key wasn't detected as broken doesn't mean it
isn't - the tool can only detect most broken keys, not all of them. if your
key was generated on an affected Debian or Ubuntu system, you still need to
regenerate it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
toolserver.org can now be used for SSH logins (login.toolserver.org), URLs
(http://toolserver.org/~username/), and email ([EMAIL PROTECTED]).
moving of other services (e.g. JIRA) will happen later.
- river.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Collins:
At any time in the near future will the old ts.wikimedia.de and
tools.wikimedia.de (or whatever they really are) become invalidated?
tools.wikimedia.de will always be valid, but it will probably turn into a
redirect to the new domain.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcin Cieslak:
What about http://stable.ts.wikimedia.org/editcount/ ?
http://lists.wikimedia.org/pipermail/toolserver-l/2008-April/001328.html -
scroll
down to '3. new stable server'.
- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bertrand GRONDIN:
Why don't I receive this warning message.
this message is displayed every time you log in.
- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (SunOS)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre Karwath:
Yes, I've seen them many times ;-) But I still do not know what I can do
to extend my account.
you don't need to do anything unless someone tells you to. since DaB has been
very busy with other things recently, he hasn't had time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Landscheidt:
when I go to
URI:https://journal.toolserver.org/toolserver/entry/on_tools_and_memory_use,
fill out the form, answer the simple math question and ei-
ther press Preview or Post, I get again to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Walker:
I spoke up about it a few days ago in the IRC channel, but I'm not sure
anyone noticed.
there's a problem with JIRA stopping to respond to clients since the upgrade
(probably related to why it's quite slow) - i'm talking to support at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Schwen:
So people who use user-crontabs must check the hostname now?
i don't understand what you mean. crontabs are not shared between servers. so
just install the crontab on the server you want it to run on.
- river.
-BEGIN
hi,
PHP on hemlock has been changed to use switchboard (a FastCGI PHP wrapper)
instead of CGI php. unless any major problems are uncovered, this change will
be permanent.
if you notice anything strange about PHP since the change, please let me know.
- river.
James R.:
Trying to access one of the many PHP files in my public_html (e.g.
http://toolserver.org/~e/bots.php) is spitting out a 500 Internal Server
Error.
this seems fine now, probably a temporary problem.
- river.
___
Toolserver-l
bayo:
* if the login.toolserver.org use 443 for ssh it can work ;
port 443 is for SSL HTTP (https), it can't be used for SSH.
you should check if the proxy supports the CONNECT method, or else can function
as a SOCKS proxy. if not, you probably won't be able to use SSH from there.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Platonides:
Wouldn't be preferably to have a daemon on the toolserver downloading
each new dump (or dumps marked as someone is interested) ?
automatically download all dumps is going to use all available disk space very
quickly.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Misza13:
1. By ask a root (to create a new repo) you mean grabbing one on IRC or
does one need to file a JIRA request?
either would probably work.
2. After it's created, will fisheye use it automatically instead of
~/subversion or does it have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kalan:
2008/7/23 River Tarnell [EMAIL PROTECTED]:
The second way seems to rely on AddHandler for .php files. I
sometimes use rewrite rules to hide the ugly-looking file extension
completely, does the described .htaccess in public_html affect them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohd Tarmizi:
Sometimes stable is not as stable as you think. ;)
this is not a problem with the server, but with the tool.
- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (SunOS)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Semenik:
I sent the information requested by DaB to create my toolserver
account to [EMAIL PROTECTED], but apparently mail server @wikimedia.org hates
me - Brion
didn't receive my email some time ago. So, can I send the information
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
it is now possible to run FastCGI programs in languages other than PHP (for
example, Perl or Python) on hemlock. to do this, simply create a standard
FastCGI application, and name it whatever.fcgi. the program does not need to
be inside
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
on Monday, 25th August, between 5:00 and 7:00 UTC, maintenance will be
performed on the stable server web server. this is expected to take less than
10 minutes, during which the web server will be unavailable.
- river.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
this maintenance was completed successfully. this update is expected to
resolve any remaining FastCGI Protocol Error issues; if you see one of these
errors, but the script itself is fine, please report it. (you might get this
error for a broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
between 05:00 and 07:00 UTC on Monday, 1st September, maintenance will be
performed on the stable server caching proxy (cache.stable.toolserver.org).
this will involve a restart of the proxy server, which will be unavailable
during this time (if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
regarding recent internal server errors on slow scripts: i have installed a
modified mod_fastcgi on hemlock which seems to have reduced this problem a bit.
please, check if your slow scripts still produce so many errors.
- river.
(PS:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Thiele:
My tools work fine, but not having rewrite rules breaks some stuff. No big
things, but annoying. I hope, that rewrite rules will be supported before
using this server.
it's unlikely that RewriteRules will be supported,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
White Cat:
I thought the hardware failure was on a wikimedia server.
no, as i explained, the hardware failure was on the switch. both Wikimedia and
Toolserver systems are connected to this switch.
- river.
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Walker:
What happened to redundancy?
i'm not sure what you're asking here; there has never been any redundancy for
host network connections, or for toolserver database replicas, so nothing
happened to that - it wasn't there in the first place.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Walker:
I was actually talking about connecting the servers to the net down
different routes, ie multiple linecards
an additional linecard is still several k$, money which could be better spent
on more servers, i think.
over the next few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
so the test version of the reports tool is now live at
http://stable.toolserver.org/reptest/. the basic framework is in place, but
the user interface needs work, and there are no useful reports yet.
Wuzur (W) has offered to improve the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
there is currently a problem on stable where the web server sometimes stops
responding to requests for a period of time. i am working on resolving the
issue now; in the meantime, there may be some service interruption for users.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
River Tarnell:
there is currently a problem on stable where the web server sometimes stops
responding to requests for a period of time.
this should be fixed for the moment. (more work needed to find the actual
cause...)
- river
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(this mail only applies to people with projects on the stable toolserver.)
hi,
i have revised the maintenance schedule for the stable server. the new
schedule provides no additional downtime windows, but reduces the amount of
downtime compared to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
on Monday 29th, 5AM - 7AM UTC vandale.toolserver.org will be rebooted for
maintenance. this will affect the toolserver web appliations (JIRA, MediaWiki,
etc). no other services will be affected. the expected time for this
maintenance is less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
maintenance will be done on the above servers on Monday, 6th October between
5-7AM UTC. each server will be unavailable for the duration of the
maintenance, which should be less than one hour in total.
- river.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
with the maintenance on Monday, the old stable server (stable.ts.wikimedia.org)
will be shut down. old URLs will turn into redirects to the new server.
files still present on old stable will be kept, but if you have files there you
want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
today we experienced a 6-second power failure at SARA, the colocation facility
where the toolserver is hosted. this affected both us and Wikimedia (who
provide our hosting there).
this affected all servers except willow (stable), which was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mauro Girotto:
I need to make a dump of page table (enwiki db) but I'm having a
problem. I use the mysqldump utility:
mysqldump --skip-lock-tables -u user -p -h sql-s1 enwiki_p page dump.sql
dump.sql contains only the table structure, no data.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryan A. P. Pendleton:
For the most part, this makes it possible to use a remote table that you
have access to in SQL commands in the same way one might normally use a
local one.
except that it's _much_ slower than local databases. too slow for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
s2 is now replicating again. assuming there are no more problems, it should
be up-to-date within 24 hours.
- river.
-BEGIN PGP SIGNATURE-
iEYEARECAAYFAkkB94UACgkQIXd7fCuc5vI2yACbBhkiHq10QX8fmxOLu3JPbF9L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
it's now possible to access phpMyAdmin without an SSH tunnel to hemlock. the
new URL is https://phpmyadmin.toolserver.org. you will need to authenticate
with your toolserver username and LDAP password (*not* MySQL password) to
access
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i understand some people have had problems with the 'dictionary word match'
check when setting/changing their LDAP password. i've disabled this check now.
it still requires one character from at least three of: upper, lower, digit,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kalan:
where can I obtain/create one?
https://wiki.toolserver.org/view/LDAP
- river.
-BEGIN PGP SIGNATURE-
iD8DBQFJFhb8IXd7fCuc5vIRAvTGAJ9o/SgYTLqhKpJOvtgwde6xxN5CygCeMzBG
Nh37/yYHY3cWkgIDNQiG3Ig=
=KBy3
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
in one week i plan to enable the new web server on hemlock. this will
hopefully solve the problems people are seeing with long-running scripts.
until then, people should test their sites with the new server. you can do
this by using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilmari Karonen:
That may well be what's happening, but if so, it's a bug in MySQL. Note
that both of the queries have identical WHERE clauses. Given that said
WHERE clauses match no rows, there's really no reason why any other part
of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
the new web server is now live. please report any problems.
- river.
-BEGIN PGP SIGNATURE-
iD8DBQFJNP4fIXd7fCuc5vIRAlVuAKCz1GHzbOWzrxE53gEA3hz9rhmOIQCfafiJ
SYnq82DKyDx8w5QZVJnPN4U=
=Boik
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
the next expiration date for toolserver accounts is 23rd December, 2008. if
you want to keep your account past this date, you should send a mail to
[EMAIL PROTECTED], with toolserver expiration in the
subject, and your account name in the body
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
River Tarnell:
Subject: [Toolserver-announce] account renewel
of course, this should say renewal.
- river.
-BEGIN PGP SIGNATURE-
iD8DBQFJNbKBIXd7fCuc5vIRAnEVAKCih/SVJnKrg0pyAmWrSvJASuf4XgCgmCYb
TUBatyM1cRB/+WHfSQSYeEg=
=2j4u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gutza:
I'm basically looking for a solution which would allow the community of
ro.wiki to get involved in this in a rather lax manner, so I would
ideally want as few formalities as possible. Therefore, from an access
perspective there should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
seth:
1. How do I run perl scripts on the toolserver?
i assume from the subject you're talking about Perl CGI scripts. either put
them in ~/public_html/cgi-bin, or put them in ~/public_html and name them with
a .cgi extension. in either case they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Kinzler:
I tried another one, too, but
bash: cd: /var/log/apache2/: Permission denied
We no longer use apache, we are using ZWS now.
it's likely he was looking on nightshade here, which does run apache, but as
it holds no user tools,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Thiele:
I changed one of my scripts to use FastCGI PHP. Therefore I renamed it to
*.phpf. This is described in [1].
this page is obsolete; PHP has been using FastCGI by default for the last few
months. i removed the content of the page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
below is the list of accounts which will be extended past the expiration date.
if your account is not listed, you should ensure you followed the directions in
the previous announcement. if you sent mail and yet your account is not
listed, you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
River Tarnell:
below is the list of accounts which will be extended past the expiration date.
to clarify: this is the list of accounts which *will* be extended, and will
*not* expire. if your name is on the list, you do not need to do anything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan,
please read: https://jira.toolserver.org/browse/TS-170
you'll probably find you get a faster response to tickets if you can open them
in English rather than German. i understand not all of our users are native
English speakers, but both of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
at some point between these two dates (exact date isn't yet known), Wikimedia
will performance maintenance at the knams hosting facility, where the
Toolserver is hosted. this will involve downtime for all servers as we will be
moving to a new rack.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Luca:
I can't connect to https://phpmyadmin.toolserver.org/. Why?
should be fixed now.
- river.
-BEGIN PGP SIGNATURE-
iD8DBQFJTkBEIXd7fCuc5vIRAuDSAJ0f+RoaWvdhiBKwCGsLNy4BTd7kBwCfZcpG
qvUktHhM9ENp0SstuEidc+c=
=NcJW
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bertrand GRONDIN:
Please, extend my account : grondin
as well
well, i did, but next time *please* follow the instructions, because it makes
things a lot easier on the admin side (and the toolserver is very short on
admin time at the moment).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wikimedia will performance maintenance at the knams hosting facility, where
the Toolserver is hosted. [...] the total outage period will be several
hours.
this maintenance will be taking place on the 28th, i.e. today.
- river.
-BEGIN
1 - 100 of 531 matches
Mail list logo
