Basically, you want a `top` (or logtop ;-) ) to be displayed in your website back office ? But top outputs in your terminal and you don’t know how to capture it ? Use ashttp, like this :

$ ashttp -p 8080 top

And then just open the port 8080 with an HTTP client and enjoy (typing some F5…) :

You can find the code on my github.

Your NFS client, trying to mount the NFS share will use RPC to communicate with the serveur, il will go like :

> PORTMAP GETPORT(Program: NFS, Version: 3, Proto: TCP)
< PORTMAP Port: 2049
> PORTMAP GETPORT(Program: MOUNT, Version: 3, Proto: TCP)
< PORTMAP Port 49066
> MOUNT MNT(Program Version: 3, Path: /srv/nfsroot/ )
< MOUNT Reply error 2, "remote can't support version #", Program Version (Minimum): 1, Program Version (Maximum): 2

You can see that the response is "remote can't support version #" and we should have found this solution in the RFC 1831 (RPCv2) stating :

  Given that a call message was accepted, the following is the status
   of an attempt to call a remote procedure.

      enum accept_stat {
         SUCCESS       = 0, /* RPC executed successfully             */
         PROG_UNAVAIL  = 1, /* remote hasn't exported program        */
         PROG_MISMATCH = 2, /* remote can't support version #        */
         PROC_UNAVAIL  = 3, /* program can't support procedure       */
         GARBAGE_ARGS  = 4, /* procedure can't decode params         */
         SYSTEM_ERR    = 5  /* errors like memory allocation failure */
      };

So the problem is you client is asking for a NFS version greater that your server runs … but if your server is running NFS v3, check a `ps aux | grep [r]pc.mountd` for :

root 1411 0.0 0.0 18808 1036 ? Ss Apr15 0:00 /usr/sbin/rpc.mountd –manage-gids –no-nfs-version 3

Did you catch the –no-nfs-version 3 ? If your server is compiled with NFSv3 support, drop the –no-nfs-version 3 in your configuration and it should work !

Enjoy !

So to say HELLO I’ll present something useless : My Python IRC Bot. But this article should be usefull, so I’ll speak about the Unix Philosophy :
As Doug McIlroy said :

This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.

So my Python Bot is wrote like this, only ~200 lines of Python it has only two interfaces, and they are simple.

The first step is to start the bot :

./ircbot.py connect 'server' '#chan' 'nickname'

Ok the bot is connected to a chan, now you have to write some hooks, in yauib every action raise a hook in the ‘hooks’ directory, you can write a hook in any language you want. As a good start point I wrote a default hook for received messages in hook/pubmsg, simplified like this :

#!/bin/sh -f
s_login="$(echo "$1" | sed 's#/#__SLASH__#g')"
s_host="$2"
t_login="$3"
t_host="$4"
shift 4
arguments="$*"
command=$(echo "${1%% *}" | sed 's#/#__SLASH__#g')
if [ -x "commands/$command" ]
    then
    args=$(echo "$1" | sed 's/^ *[^ ]* *//g' )
    commands/$command $args
fi

You should read : “When a message is received, the command in commands/[1st word of the message] is executed.”

So now you can start to write simple commands in the commands folder, like the command say :

#!/bin/sh
echo "$*"

This command is 17 chars long, and now, without restarting your bot, try to make it say something on the channel :
you> say hello
bot> hello

An now you can start to write dauting ones …. like … display a readeable calendar of the current month like :

     March 2011
Su Mo Tu We Th Fr Sa
       1  2  3  4  5
 6  7  8  9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31

Ready ?

#!/bin/sh
cal

As the binary cal is installed on you machine, (windows user, you can leave, now), that’s all, your’re done … sorry, it just work :p

Et voilà !

You have to keep the UNIX philosophy in mind :
– Everything is a file
– Write programs that do one thing and do it well

And you’ll be happy developers !

PS: You can download / contribute to Yauib on https://github.com/JulienPalard/yauib

grep -rni foobar . | grep -v .svn

Upgrade to grep 2.5.3 and use (alias it ?)

grep -rni --exclude-dir .svn foobar .

(or … stop using SVN ! ! !)