> That would not surprise me, since as I said, we've been having this
> problem for quite a while.
This is quite hilarious to read. Golem was causing a large proportion
of the previous problems with MySQL, and you didn't kn
ode more openly even retroactively.
Very very free licenses (MIT/X11 or WTFPL, for example) can be revoked.
Fahad Sadah
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guid
It's easier for the admins to maintain
Fahad Sadah
2009/12/28 Pietrodn
> Il giorno 28/dic/2009, alle ore 18.08, River Tarnell ha scritto:
>
> > With this in mind, it might make sense to dispose of the Linux login
> server entirely, and convert it to Solaris. But before
Yeah, Merry Christmas
Fahad Sadah
2009/12/24 Platonides
> emijrp escribió:
> > Hi people;
> >
> > I wish you all a Merry Christmas and a Happy Toolserver New Year. I hope
> > we will develop many useful tools in the next year (remember small
> > langu
It needs to ask for a registered Freenode IRC nickname, and verify it
(obviously can't be done in JS)
Fahad Sadah
2009/12/6 Soxred93
> For what it's worth, I have just written a JavaScript cloak
> generator:
> http://toolserver.org/~soxred93/ttestjs/<http://toolserver.o
Please file a request in JIRA
Fahad Sadah
2009/12/5 Laszlo Kozma
> -- Forwarded message --
> From: Laszlo Kozma
> Date: Sat, Dec 5, 2009 at 8:11 PM
> Subject: Re: [Toolserver-announce] [Toolserver-l] Account-Extending
> December
> To: "DaB."
>
&
Friday 13th? Let's hope nothing goes wrong.
Fahad Sadah
2009/11/11 Simon Walker
> -- Forwarded message --
> From: River Tarnell
> Date: 2009/11/10
> Subject: [Toolserver-l] NFS maintenance, Friday 13th November
> To: toolserver-annou...@lists.wikimedia.or
Could parse hostname --fqdn
Fahad Sadah
2009/9/2 River Tarnell
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Darren R. Hardy:
> > I use this in my shell scripties:
>
> > if [ "`hostname --domain 2>/dev/null`" = "toolserver.org" ]; then
2009/8/27 Henrik Hodne :
> On 27. aug. 2009, at 10.14, Leszek Krupinski wrote:
>
>> On Thu, Aug 27, 2009 at 10:06 AM, Henrik Hodne
>> wrote:
Out of interest, how would these limited rights be implemented?
>>>
>>> I would guess that the easiest way would be some kind of daemon
>>> running as r
> does this seem like something that would be helpful? and, if we
> introduced it, would anyone be interested in such privileges? (we would
> probably require a good knowledge of Unix and at least some experience
> with system administration.)
I am interested. I have plenty of experience with Un
How does one volunteer to become a toolserver admin, or, if there are
too many security/trust problems, any other helpful job?
Fahad Sadah
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo
nt
>>>
> [...]
>
> New style, middle posting? :)
>
> ___
> Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/toolserver-l
> Posting guidelines for this list:
> https://wiki.toolserver.org
Would lighttpd/nginx be any better? I've had good experience with those.
Fahad Sadah
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
> ...If the roots know about a planed downtime
Please consider making this file 666, so anyone can update the status,
wiki-style?
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
> the s1 server (rosemary) has a faulty motherboard which is causing
> system crashes. we will replace the part next week; until then, access
> to s1 will be intermittently offline.
Was this the cause of the increasing replag?
Fa
s1 has finished reimporting, according to River.
Fahad Sadah
___
Toolserver-l mailing list
Toolserver-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Especially with those three Sun servers you plan to buy.
Fahad Sadah
2009/8/2 River Tarnell
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wolfgang ten Weges:
> > Since it's the case, people only using tools that does not need DB
> > replication could g
ly paste a private key
> somewhere, and it's impossible to guess. even if it was leaked, the user
> would also have to leak the passphrase.
>
I doubt many people here use passphrases
Kerberos was just an example, btw. I was jus
Gmail automatically writes above the quoted text.
Fahad Sadah
2009/8/1 Pietrodn
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Il giorno 01/ago/09, alle ore 16:21, Henrik Hodne ha scritto:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
Kerberos authentication. Easier than pubkeys, and more secure.
Fahad Sadah
2009/7/29 John at Darkstar
> Perhaps there could be some kind of central management of some kind.
>
> One thing is distribution of the open databases. It should not be
> necessary to set up replication
Perhaps it could be made into a DNS round-robin?
Fahad Sadah
2009/7/21 River Tarnell
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> hi,
>
> in the past we provided the login.toolserver.org alias, which pointed at
> the
> login server. we have decided to depre
I wıll when I'm back ın England (1st August). Easıer than wrıtıng my own [?]
Fahad Sadah
2009/7/27 Magnus Manske
> On Sun, Jul 26, 2009 at 5:34 PM, River
> Tarnell wrote:
> > at the moment, there is no advantage to using a multi-maintainer tool;
> however,
> >
22 matches
Mail list logo
