Hello, all.
Can anyone tell me what sort of terrible events will transpire if I
install libemail-date-perl version 1.101-1 Etch package instead of the
1.103 version recently specified as a Koha dependency? I like to avoid
installing modules directly from CPAN, but of course avoiding breakage
is a
Good day, all. Their was a service interruption for bugs.koha.org,
koha.org, download.koha.org, etc earlier today. This was result of
either some sort of web crawler gone terribly awry or, more likely, a
malicious DoS attack. Apparently, some people apparently don't
appreciate free software.
Not r
Having managed this sort of configuration with MediaWiki, I've had
thoughts about using it for hosting Koha instances. It has a number of
advantages, including being more amenable to mod_perl. The biggest
drawback to this configuration is when applications care about the
port number on which the HT
rtual host?
Thanks,
Clay
On Tue, Nov 25, 2008 at 3:27 PM, Rick Welykochy <[EMAIL PROTECTED]> wrote:
> Clay Fouts wrote:
>
>> Having managed this sort of configuration with MediaWiki, I've had
>> thoughts about using it for hosting Koha instances. It has a number of
>>
I've installed a Plone redirection/aliasing tool on the development
site and verified that it installs cleanly. I'll deploy it on the
production server later this evening (PST) along with the two stated
aliases for the paid support page.
Clay
On Mon, May 11, 2009 at 4:41 AM, MJ Ray wrote:
> Jos
y
responses on there unless they're also forwarded to this list or
directly to me. Please feel welcome to do so.
Clay
On Tue, May 12, 2009 at 3:11 AM, MJ Ray wrote:
> Clay Fouts wrote:
>> I've installed a Plone redirection/aliasing tool on the development
>> site and verif
Hello, David. It's not clear to me why Koha (or CGI::Session, more
likely) uses REPLACE INTO for sessions. It's a performance killer.
Each time it's run it splits up into two or four queries, depending on
conditions. Simply executing an UPDATE, then an INSERT on the
condition that zero rows were up
Hi, all.
Just a brief update on the git.koha.org outage. That server is
currently unreachable, even on an administrative basis. We've been
working with the hosting provider (Spry) for the past several hours to
get it back online. It ought to be available again soon.
Cheers,
Clay
_
Git service is now fully restored. I'm doing a post-mortem and will
report back on the cause if there's anything unusual.
Clay
On Tue, Nov 24, 2009 at 12:53 PM, Clay Fouts wrote:
> Hi, all.
>
> Just a brief update on the git.koha.org outage. That server is
> currently u
it's not working again this AM :(
>
> Nicole
>
> On Tue, Nov 24, 2009 at 5:10 PM, Clay Fouts wrote:
>> Git service is now fully restored. I'm doing a post-mortem and will
>> report back on the cause if there's anything unusual.
>>
>> Clay
>>
l).
I've added the robots.txt because it certainly can't hurt, and I can
analyze the requests after a couple of days. However, I don't think
it's real solution, either.
Clay
On Wed, Nov 25, 2009 at 9:15 AM, Paul Poulain wrote:
> Clay Fouts a écrit :
>>
>> I
You can also use "truncate sessions" to do the job if you just want to clear
out the contents of the table. It's faster and simpler than using mysqldump.
This issue arises from the fact that the way Koha is written, if a user just
walks away from a session without logging out, their session data w
It depends, actually. For tables without FK constraints (like Koha's
"sessions"), truncation is instantaneous in MySQL.
On Wed, Feb 17, 2010 at 12:02 PM, Chris Cormack wrote:
> 2010/2/18 Clay Fouts :
> > You can also use "truncate sessions" to do the job if yo
h enhancement to make. I’ll make it
> a point to keep an eye on the sessions table until then, and remind my
> coworkers to logout properly.
>
>
>
> Cheers,
>
>
>
>
>
> -Ian
>
>
>
> *From:* koha-devel-boun...@lists.koha.org [mailto:
> koha-devel-bou
Definitely. Even though the session table may in many cases be much smaller
than other tables in terms of bytes or rows, the frequency at which it is
written to causes it to be heavily fragmented on the disk, which greatly
reduces the average throughput during a mysqldump, increasing the backup
tim
Hi, all.
With the shift of koha.org-related services from Metavore (LibLime's former
owner) to PTFS, we're going to be relocating a few of the services that
currently reside on Metavore assets. Most notably, wiki.koha.org and
git.koha.org are going to move to a new system. This will involve a bit
ever, it's not possible to do this with the Git
repo, AFAIK, so it would be fruitless to do so with the gitweb interface.
Cheers,
Clay
On Sat, Apr 10, 2010 at 2:08 PM, Dobrica Pavlinusic wrote:
> On Fri, Apr 09, 2010 at 12:36:10PM -0700, Clay Fouts wrote:
> > Hi, all.
> >
hostnames now
resolve to 174.129.238.79.
Thank you,
Clay
On Fri, Apr 9, 2010 at 12:36 PM, Clay Fouts wrote:
> Hi, all.
>
> With the shift of koha.org-related services from Metavore (LibLime's former
> owner) to PTFS, we're going to be relocating a few of the services that
Gitosis was missing completely, actually. I've installed and re-mapped the
configuration. Test it again now, please.
Thanks,
Clay
On Mon, Apr 12, 2010 at 6:11 PM, Galen Charlton wrote:
> Hi,
>
> 2010/4/12 Clay Fouts :
> > I have completed (ostensibly) moving both of the
Hooray for progress. How about now?
Clay
On Tue, Apr 13, 2010 at 4:25 AM, Galen Charlton wrote:
> Hi,
>
> On Tue, Apr 13, 2010 at 3:02 AM, Clay Fouts wrote:
> > Gitosis was missing completely, actually. I've installed and re-mapped
> the
> > configurati
n Tue, Apr 27, 2010 at 4:47 PM, Chris Cormack wrote:
> * Clay Fouts (cfo...@ptfs.com) wrote:
> >I agree ParserDetails.ini is also not a good place to define it since
> it
> >forces a system-wide preference. But wouldn't adding it to
> C4/Context.pm
> >be
21 matches
Mail list logo
