-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
first issue: sql-s1 change. we will shortly be changing s1 from yarrow to
rosemary. if you have user databases on yarrow, these will *not* be copied
over, and furthermore will be deleted when s3 is re-imported to yarrow. if you
need to keep these databases, you need to dump them *now* using mysqldump, and
either import them into the new s1 server after the change, or import them back
into yarrow when s3 is reimported.
second issue: large home directories.
the following users have home directories larger than 10GB:
12978772 drh08
15633252 sk
15753754 voj
18902342 bryan
20391211 kolossos
34753424 cbm
41874315 dschwen
55842970 daniel
the following users have home directories larger than 1GB:
1206570 emijrp
1231049 tawker
1417818 dab
1437121 flacus
1461143 erenrich
1568766 purodha
1712819 simetrical
1834572 leon
1898741 fmaunier
2026644 kalan
2049700 chabacano
2170154 misza13
2447405 danny_b
2564363 tangotango
2890444 osamak
3260012 river
3860768 vvv
5070464 tparscal
5636581 gmaxwell
7112804 werdna
a full list of home sizes is here:
<http://toolserver.org/~river/bighomes.txt>
whether or not your name is on either of the above lists, but especially if it
is, please look at what's using disk space in your home directory and clean out
any old files you no longer need (for example, log files, old dumps, etc).
don't delete anything you actually need, though.
if you need to store dumps or other large files, you can put them in the shared
user store at /mnt/user-store instead of your home directory.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmpdO8ACgkQIXd7fCuc5vIBkQCgqHSWO96VwlrBemGIVsAJ4Jar
3WoAmwWaPrXjE7ozsAiIuawdYftzH+Th
=Nylc
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
the new servers arrived today and were racked and installed. i am currently
setting up the new s1 database and should have the database imported by the end
of this week, assuming nothing goes wrong.
we won't be able to move /home to hemlock right now as planned, but we might
have an interim solution that improves the slow /home performance.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmoMgcACgkQIXd7fCuc5vLdagCeNiY4g9YcyUhcZZkAcv9lUkmh
s8kAnA5U2zB+ECNxfxXLC2AnwYdZhyqW
=ZZFy
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
with the change to the SVN server, svn:// URLs are no longer supported, meaning
legacy repositories ($HOME/subversion/) are not remotely accessible except via
svn+ssh:// (which requires authentication). these repositories have been
removed from FishEye.
if you are still using a legacy repository, and want it to be remotely
accessible, you must convert it to a new-style repository. new-style
repositories are explained here:
https://wiki.toolserver.org/view/SVN
and the conversion process is explained here:
https://wiki.toolserver.org/view/New-style_Subversion_repositories
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmj6zEACgkQIXd7fCuc5vKxpwCgq1i007vDvRgMIPVT4bpVB7mc
gzwAn1ltHGL261H3cBBMRcqxdgWwO+9L
=olN9
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
currently there are some "missing" repositories on stable. we will not be
restoring these to the previous location (/svnroot), but instead integrating
them into the SVN repositories on amaranth. therefore, if you/your project has
an SVN repository on stable, you should mail ts-admins(a)toolserver.org with this
information:
* the repository name
* the users who should have commit access (normal toolserver usernames, not
stable usernames)
additionally, you (and anyone else with commit access) will need to run
'setpass' on nightshade to set your LDAP password before you can commit.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmjeCYACgkQIXd7fCuc5vKLPgCgkzNJE4o31CMQcz+qhsy6TaIt
SM0AoLYjg/Siiy2e1A6324n21KPgEfXN
=TEBP
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
today/tomorrow, svn repositories will be moved from nightshade to amaranth.
URLs will remain the same, but you might find that you can't access SVN for up
to an hour after the move, while the DNS change propagates.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmjEjYACgkQIXd7fCuc5vIbXACfXbUjOJJO0GLm+PzFIOhLlhJE
HgEAn28evcZYtIA/lzOuiNbwf3i0sWh3
=8CoQ
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
nightshade suffered a software error and was pre-emptively rebooted to prevent
issues. at the same time the OS kernel was upgraded, which should prevent this
issue from recurring.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmeBOkACgkQIXd7fCuc5vI41gCfZYH+JUXM9eAgZwIDQKEfqOmb
VBkAn2xmfqZVSfb5pAlyoVDFJBxXLu86
=4PIh
-----END PGP SIGNATURE-----
Hello all,
I changed the default-editor from joe to nano on hemlock and nightshade. If
you like joe more then nano (like I do) so add
export EDITOR=joe
at the end of your .bashrc
The change was done because joe allways forgets the automatic \n after a line
and that cause some problems with crontabs.
Sincerly,
DaB.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
Werdna (MediaWiki developer) has volunteered his time as a Toolserver
administrator, and has been given root access. Werdna will be helping with
day-to-day operations, like responding to ts-admins mail and fixing things that
break. given how short of admin time we are, i hope this will noticably
improve admin response time for users.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmVP24ACgkQIXd7fCuc5vImVQCguIakQryV4W0NJ/ImavL93NvU
28EAoLT/O+dXpvANoOzjvjJHuFekgCH2
=V1UO
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
nightshade had a software fault at about 6:30AM UTC today and was rebooted at
3:35PM UTC to clear it.
- river.
-----BEGIN PGP SIGNATURE-----
iD8DBQFJkE7MIXd7fCuc5vIRAu7vAJ0cQeBJnkB3/pqj0RElDsqfE6nmswCffy6S
bjq8k8bm1DwNlVMTOwJe2sQ=
=lc+S
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
if you have a free moment, and are a Toolserver user, please fill out this
short survey about the Toolserver:
http://toolserver.org/~river/survey.txt
the more people who reply, the more we will know what needs to be improved.
- river.
-----BEGIN PGP SIGNATURE-----
iD8DBQFJiqm5IXd7fCuc5vIRArcsAKCMlkcMKKOtlzpjrsEMW8eYXv7LagCdFdR7
Yi3uf/sHtL4xGq67kxEJsOA=
=WjOr
-----END PGP SIGNATURE-----