Maybe this is too late: after my experience launching my first WordPress-based blog, I noticed that it attracted more crawler request than my previous blogs. I understand that in the other side, I did not activate ping feature inside Movable Type — which for other reason, I do not like to be visited by several ugly name crawlers.

Inside WordPress' configuration, there is http://rpc.pingomatic.com for ping. I visited that site and read some of Matt "WordPress" Mullenweg's introduction, and thing to be considered to use. Having fulfilled into all of my Movable Type's blog, everything changed fast: more crawlers came — it means increasing hits in statistics. But, really I can not yet come into conclusion that this is all only because of ping. In other condition, I push #direktif with progressive increasing articles, so it naturally attract more visitors coming due to more and more materials reached from search engine (i.e. Google and Yahoo!).

Other way to keep visitor longer by visiting other entries is by providing related entry box. I used simple and clean approach from Kalsey, and it works very nice for #direktif.

Ah, increasing visitors: I'd like to watch figures about that just as stockbroker gets crazy in front of moving numbers in stock exchange.

How to deal with several blogs: various topics and different tools?

For some actual reasons, I live around that condition. IT and its related, social and lifestyle, literary and culture, and some short annotations about my country, are some things I want to dump out from my brain. I ever though that with some separations — and actually I use some domain name with also different tools — it will be less effective for writing continuation and the possibility of having delay in one topics.

But let me try. One day I prefer to think and write about one aspect, so I tune into that theme, and the other day I dig into others. One day into another, and I imagine these all are like some pieces of books I am free to write. These books are all open and it is up to me which one looked interesting to be written in a time.

So keep relax. And write.

YES, the unknown periode is now stopped.

I decide to maintain my account in Blogger live again after some short-but-frequently visiting some of my friends' Blogger. Thinking that it is better not to only furnishing my Blogger profile, I look toward my old blog, and still seems interesting to go on.

Choosing new template (yeah, this is a real magnet regarding what has happened in Blogger), rebuilding all pages, and activating commenting. Thanks very much for Enetation which had been used for months, and now I use Blogger's own. Unfortunately, commenting will be active for a new posting — old messages are left without comment. So, this is also first posting with comment on.

See you after this announcement post. I would like to write some sorts of my busy backoffice. Urusan dapur, that is Indonesian calls.

For unknown period, I will stop writing at this Weblog, due to the excessive works I must do in my primary Weblog, Coret Moret Amal and its families, and #direktif.

I will still keep my Blogger account alive, but let the status of this site to be archived.

Once again, I must deal with RAM of Atijembar. After some kernel error reporting segmentation fault, I came into unstable condition yesterday and this morning. Examining log, I found that fatal errors happen when available free space was too low. In the kernel language, that is time to request new page (?) and reallocate unused space. Or I think that is time "high area" of RAM is used.

I reproduced this situation several times and, indeed, that is the problem.

One of Debian experts in #debian channel in Freenode suggested me to use memtest for testing my RAM. I tested using both memtest86 and memtest86+, but the results were somewhat strange. Even with new (again) replacement RAM, it reported some errors. So, which one can I trust?

The old 128MB one is still the best, no error was reported. I tried to install Debian with 128MB (enough, er?), but it was fail at the last stage of installation. Do not know why for a long enough time, and still suspected that it was RAM problem. On Friday, 5 March, after sholat Jumat and talking for while with Ismail Fahmi (unplanned meeting in Super de Boer), I came with idea this was maybe about partition problem which I used to ease (re)installation. The /var partition was mounted from old saved one, so I do not need to back-and-forth moving large size directory there.

I did installation with letting Debian creating its new /var partition, and... ah, successful! Soon after that, both new and old /var were synchronized, and Web server was up and run again.

For a month since now, I will test this RAM with various memory-minded operation to make it sure anything is in order.

Yesterday I had to fixed my Atijembar again. File system of main partition got corrupt and aah... I want to get stability quickly, so the best thing is saving all important files to data partitions and installing Debian.

As I was surprised — and a little dissapoinment — with my server's performance overall, I was still curious where the problem really exists. And today afternoon, an incident happened and a little explanation satisfied me. I made a backup from one CD using raw method,

dd if=/dev/cdrom of=filename.iso

After minutes of reading and writing, segmentation fault suddenly happened and I had to reboot and did fsck repairment. But I knew that I missed bs (block size) parameter. I tried one more with correct command,

dd if=/dev/cdrom of=filename.iso bs=1k

It is safe and exited normally. So, my little prediction with yesterday's failure is about dumping data in huge size. Because last weekend I helped reinstalling my friend's notebook and I used Atijembar's Samba for backing up notebook's hard disk.

Since several days ago, I noticed that #direktif is less visited compared with the time before I got trouble with my server. The "search word" recorded by my Analog's statistics is also empty. So, yesterday I checked to search common word from #direktif via Google, and... oops, no result for direktif.web.id!

Ah, this is what I have to pay for last week of January until mid-February problem with Atijembar: Google's crawls were failed to read #direktif (only #direktif) so for now on (until next reindex on their database) #direktif is unreachable from Google. The other major search engines? Unfortunately they are usually too late to update.