Hi all
I have written a small script that pulls the content of the toolserver home page
<http://toolserver.org/> from our wiki. It's not live yet, but you can test it
at <http://toolserver.org/newindex.php>. The page's content is maintained on
<https://wiki.toolserver.org/view/Toolserver:Homepage> which can be edited by
admins. I hope this will make it easier to maintain the home page's content.
I think the same system can be applied to other pages we might want to maintain
in the wiki but present independantly.
Any comments and ideas are welcome, of course.
-- daniel
Hello all,
yesterday at highnoon the master-db-servers were switched because of an huge
schema-update. Because we have only one cluster of db-servers at the moment we
couldn't do the schema-update the same way like the foundation (the foundation
stops one of their slaves, does the schema-update, waits, start it again,
stops another slave, does the schema-update and so on until all slaves are
updated, and declare one slave as new master, runs the schema-update on the
old master = no downtime) and so it took several hours until the schema-update
was done and we could switch to the new master-servers.
I deleted the view on the logging-table during the update to speed the update
up and killed several long-running queries too tonight.
The update was finish before I wake-uped, and I just finished the
masterswitch, restarted replication and recreated the logging-tables (see
maintaince-log for details). So in a few hours everything should be normal
again.
Happy Corpus Christi (it's an holiday here :)).
Sincerly,
DaB.
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
please remember that 'nice' is not a magical fix for programs that use too much
CPU. if a program uses a lot of CPU, it should be reniced; but that doesn't
mean that you can use as much CPU as you like as long as you renice it.
if you write a tool that uses 50% CPU constantly, you are using 6.25% of the
total available CPU on the Toolserver for yourself. if everyone did this, we
could only support 16 users before running out of CPU. we have a lot more than
16 users, so please be considerate, and monitor your CPU use.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkow9O0ACgkQIXd7fCuc5vIgFQCgjrrJVnKGFEwOV+aPNXkXPzJI
KUEAoI7GF7FixCyGq8cQhXOnTZFldeBO
=tJcy
-----END PGP SIGNATURE-----
Hi all
Just a quick update on the new servers: they are installed now, but need some
more setup. This should be complete by next week, or maybe the week after.
Regards,
Daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
during today new Toolserver hardware will be installed. there is a possibility
that this will cause some downtime.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkoqM8oACgkQIXd7fCuc5vLVvgCeMghf+fjTTWTVQJ9Sb+9/S3N8
NtQAnAvp/KkK0ud5hMW//HTVPGzUqaZU
=jdf4
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
a new Python, version 2.6.2, is now available on stable. this is *not* the
default Python; it is installed in /opt/ts/python/2.6, and to use it, you
should write something like this at the top of your script:
#! /opt/ts/python/2.6/bin/python
all previously-installed modules are also available with the new Python. the
problem with $PYTHONPATH is also fixed, so there is no longer any need to set
that to use any modules.
i recommend all projects which use Python change to 2.6, as any new module
requests will only be built for this version.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkon8BAACgkQIXd7fCuc5vLO8wCfcYznII2Wouz77b9VNxjRm+Wr
JJEAnRHnnQxaE9iHKKhcHSB/upVlXjwh
=OpZb
-----END PGP SIGNATURE-----