Writings Photos Code Contact Resume
msameer's blog

You are here

Katoob 0.5.3 is out.

Submitted by msameer on Wed, 11/10/2006 - 12:46am

Only 2 new changed:
* Can now import and export text that has bidi and shaping applied to.
* The plain text exporting now depends on fribidi.
from the usual location!


ايه الفرق ؟

Submitted by msameer on Mon, 25/09/2006 - 5:07pm

بعد قراءة هذا الخبر

الان قارن:

* و النبى البنات تلبس كويس علشان احنا مش قادرين خالص
* و النبى خلى غير المسلمين مايجهروش بالفطار علشان هايجرحوا مشاعرنا

ايه رايكم ؟

طب تفتكروا لو واحد مسلم فطر هايطردوه بره ؟

طبعا انا مش باقرا الهباب ده لكن BooDy وراهونى.


Katoob 0.5.2

Submitted by msameer on Tue, 19/09/2006 - 10:58pm

Here's the tarball, md5sum and a gpg-signed md5sum file.
ChangeLog:
Can now open remote files using an external command.
Added an option to insert files.
Some small code improvements and cleanups.
Depend on gtkmm 2.6.0 instead of 2.6.5


How bad can it be ?

Submitted by msameer on Wed, 13/09/2006 - 7:59pm

I thought about it. Your original flight was delayed, you nissed the next flight. The carrier arranged for your atay but, you are unable to find your luggage!


The spammer or a DoS attack ? Doesn't really matter.

Submitted by msameer on Sun, 10/09/2006 - 6:55pm

So, I'm still a hardcore GNU/Linux administrator after all ?!

Apache "The webserver" is down. Looks like the master process gets killed by the kernel. That's weird.

Now what's interesting is the dmesg output:

TCP: Treason uncloaked! Peer 62.68.70.130:62537/80 shrinks window 1681427947:1681430707. Repaired.
TCP: Treason uncloaked! Peer 62.68.79.66:61105/80 shrinks window 288684489:288684490. Repaired.
TCP: Treason uncloaked! Peer 62.68.79.66:61107/80 shrinks window 285018062:285018063. Repaired.
TCP: Treason uncloaked! Peer 62.68.79.66:61137/80 shrinks window 282542156:282542157. Repaired.
TCP: Treason uncloaked! Peer 62.68.79.66:61161/80 shrinks window 305746809:305746810. Repaired.
TCP: Treason uncloaked! Peer 62.68.79.66:61185/80 shrinks window 341351133:341351134. Repaired.
TCP: Treason uncloaked! Peer 62.68.79.66:61213/80 shrinks window 356410419:356410420. Repaired.

Looks like the peer is playing bad games with my TCP/IP stack. Decreasing the window size. I guess that's why apache was holding too many connections. Something like 119 connections.

netstat output was interesting:

     88 CLOSE_WAIT
     21 SYN_RECV

I wouldn't know but I guessed that the high number of SYN requests is due gto the high number of half closed sockets.

The problem is that after I've decreased the CLOSE_WAIT time via:

echo 2 >  /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait

The number of TIME_WAIT started to increase.

echo 10 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait

Of course all the above might be incorrect or even nonsense. Let's see.



katoob 0.5.1

Submitted by msameer on Tue, 05/09/2006 - 3:28pm

To fix a compilation error when dbus is disabled. Get it from the usual place!


katoob 0.5.0 is out.

Submitted by msameer on Mon, 04/09/2006 - 12:18pm

العنب العنب...

Submitted by msameer on Fri, 01/09/2006 - 1:58pm

و النبى و النبى حد يقولى ان مش انا الوحيد اللى بيعتبر الاغنيه دى زباله!!!

طب عدويه ماشى

شعبولا زباله بس اهو فيه كلام و ممكن يعدى

سعد الصغير اغنية الكلام على مين مش وحشه بس اللى بعده زباله بس بيعدى

انما اسمه ايه بعرور ده ملعون يخرب بيت كده!!!!!!!!!

بالمناسبه فيه واحد جديد اسمه عبد الله الصغير بس انا لسه ماتجراتش و سمعته


This is how you can fix your utf8 b0rked drupal database.

Submitted by msameer on Tue, 29/08/2006 - 7:21pm

The problem:

You are on a shared hosting. Your host upgrades MySQL. Your drupal 4.7 installation is boom broken!

The reason:

Drupal 4.7 sets the database connection to utf8 if you are running MySQL 4.1+
When you upgrade drupal from 4.6 to 4.7 and you are using MySQL 4.1+, drupal will convert the tables to utf8. But it won't if you are running MySQL 4.0.
Your host upgrades MySQL from 4.0 to 4.1+ and drupal will start setting the connection to utf8 BUT MySQL "knows" that the tables are in latin1 encoding. He doesnt know that the data is really utf8 but the tables are latin1. It'll convert the data from latin1 to utf8 and send it to drupal. You'll end up with a broken website due to the double utf8 conversion.

The solution:

Use his script to convert the tables to utf8.

The instructions are near the top.


Pages