Alexander Leidinger

Just another weblog


How many WP plu­g­ins are used on average?

After a quick chat with miwi, I ask myself how many peo­ple actu­ally are inter­ested in plu­g­ins for WP and how much plu­g­ins peo­ple have on average?

Miwi has cur­rently 4 plu­g­ins installed. I have 30 plu­g­ins installed as of this writing:

  • Akismet: comes with WP, anti-SPAM
  • AskA­pache RewriteRules Viewer: gives some info about the apache rewrite rules used in WP
  • Bet­ter Search: improves the search fea­tures of WP
  • Bot Tracker: shows which bots crawl your site (no robot crawled mine yet, I assume I have not acti­vated it long enough and need to wait a lit­tle bit until I see some results)
  • Bro­ken Link Checker: checks my blog for bro­ken links
  • Con­tex­tual Related Posts: adds “Related Posts:” to new post­ings, not always up to the task (as can be seen in this post­ing), but I hope it will improve with time when I post more
  • Dash­board: Lat­est Spam: gives some info in the dash­board about the blog-SPAM
  • FD Word Sta­tis­tics: gives some infos about the “com­plex­ity” of your posts in the post­ing editor
  • GD Press Tools: a col­lec­tions of mul­ti­ple features/stats/…
  • GD Sim­ple Wid­gets: not used yet, pro­vides wid­gets for the side­bar which also come with the WP-core, but this ones are modified/enhanced; I have not tested this yet
  • GD Star Rat­ing: allows you to rate my post­ings with stars and thumbs up/down (feel free to do it here, if you found some­thing useful 😉 )
  • Import HTML Pages: if I want to import exist­ing HTML pages… I have not decided yet if I will use it or not
  • Limit Login Attempts: IMO some­thing like this belongs into the WP-core
  • Plu­gin Man­ager: I want to give it a try
  • Quick Stats: some addi­tional stats
  • Search Meter: gives you some info about the searches peo­ple do in the blog (nobody searched some­thing yet…)
  • Sim­ple Track­back Val­i­da­tion: an anti-SPAM plu­gin, or at least some san­ity checking
  • Tan­Tan­Noo­dles Sim­ple Spam Fil­ter: some sim­ple anti–SPAM rules
  • TinyMCE Advanced: I want some more but­tons in my posting-editor
  • Weasels No HTTP Author: anti-SPAM, do not allow http:// in the name of authors (comments, …)
  • Stats: do I really need to explain this?
  • WP-Stats-Dashboard: sim­pli­fies the han­dling of the “Word­ Stats”-features
  • wp-Typography: auto­matic typo­graphic improve­ments to post­ings, I do not know if it is use­ful for non-English texts, but at least my post­ings in Eng­lish look better
  • WP Math Pub­lisher: allows to place some more math­e­mat­i­cal ren­der­ing of math-equations in post­ings, e.g. the golden ratio: phi = {1 + sqrt{5}}/{2}
  • WP Secu­rity Scan: scans your blog setup for known secu­rity holes
  • WP Update Mes­sage: allows to put a “post­ing updated: XXX changed”-box into your postings
  • Delete Spam Daily: not acti­vated yet, as I did not get any SPAM yet, I can not make a con­trolled test, so I wait
  • Hello Dolly: plu­gin comes with WP-core, not activated
  • Login Lock­Down: not acti­vated, I will delete it soon, as I like the “Limit Login Attempts”-plugin more
  • One-Time Pass­word: does not work out of the box for me, it looks like it does not find php-otp (it is not installed, and I need to have a look if it comes with php-otp included and iit s not found, or if I have to install it)

Tags: , , , , , , , , ,

EMC^2/Legato Net­worker status

The update to went fine. No major prob­lems encoun­tered. So far we did not see any regres­sions. The com­plete sys­tem feels a lit­tle bit more sta­ble (no restarts nec­es­sary so far, before some where nec­es­sary from time to time). We still have to test all our prob­lem cases:

  • restart NW-server directly after delet­ing a client with index entries (man­ual copy of /nsr needed before, in case the medi­adb cor­rup­tion bug is not fixed as promised)
  • shut­down a stor­age node to test if the NW-server still crashes in this case
  • start with an empty medi­adb but pop­u­lated clients (empty /nsr/mm, but untouched /nsr/res) and scan some tapes to check if “shadow clients” (my term for clients which have the same client ID but get newly cre­ated dur­ing the scan­ning with a new client ID and a name of “~<original-name>-<number>”) still get cre­ated instead of pop­u­lat­ing the index of the cor­rect client

The first two ones are sup­posed to be fixed, the last one is maybe not fixed.

Not fixed (accord­ing to the sup­port) is the prob­lem of need­ing a restart of the NW-server when mov­ing a tape library from one stor­age node to another stor­age node. It also seems that our prob­lem with the man­ual cloning of save sets is not solved. There are still some clone processes which do not get out of the “server busy” loop, no mat­ter how idle the NW-server is. In this case it can be seen that nsr­clone is wait­ing in nanosleep (use pstack or dtrace to see it). The strange thing is, that a safe set which is “fail­ing” with such behav­ior will always cause this behav­ior. We need to have a deeper look to see if we find sim­i­lar­i­ties between such safe sets and dif­fer­ences to safe sets which can be cloned with­out problems.

Tags: , , , , , , , , ,

Daily doxy­gen gen­er­ated docs of the FreeBSD ker­nel (head)

I man­aged to get some time to setup an auto­mated gen­er­a­tion of the doxy­gen docs for ker­nel sub­sys­tems of FreeBSD on my webserver.

Every night/morning (Ger­man time­zone) the sources will be updated, and the docs get regen­er­ated (this takes some time). Cur­rently this depends upon some patches to the make­file and doxy­gen con­fig files in tools/kerneldoc/subsys. Every­thing is gen­er­ated directly in the place where the web­server will look for to deliver the pages, so if you browse this in the mid­dle of the gen­er­a­tion, the con­tent may not be con­sis­tent (yet).

Please be nice to the web­server and do not mir­ror this. You can gen­er­ate this your­self very easy. Assum­ing you have the FreeBSD source on a local hard disk, you just need to down­load the patch from (if you do not find dox.diff, update your FreeBSD sources and every­thing will be OK), apply the patch, cd into tools/kerneldoc/subsys and run “make all” (or “make vm” or what­ever you are inter­ested in). You need doxy­gen installed, off course.

If you want to setup some­thing like this your­self, just down­load the script which is doing all the work, change some vari­ables in the begin­ning, and cre­ate your own local ver­sion of the com­plete docs.

In case this is using sig­nif­i­cant traf­fic, I will ask core/admins if there is the pos­si­bil­ity to host it on resources.

Tags: , , , , , , , , ,