Problem with the avahi daemon during the boot

A small reminder that I'm still alive plus a problem that almost scared me today (technologically speaking).

My Fedora 11 did me a trick and after an "apparently normal" shutdown yesterday, the avahi daemon failed during the boot hanging it on the login page (background image missing and plenty of error messages about the fail installing the daemon).
There were no ways to log in since after entering the password the laptop would have got stuck in an infinite loading machine. The other terminals (Ctrl+Alt+F2...) worked well.

What I did was then load the live cd and search for help over the internet being prepared to backup and re-install Fedora.
There weren't almost any hint on the web on how to solve this problem, if not for some issues with wireless cards, but nothing similar to my problem that completely blocked me from opening my GUI. I was lost.

Looking at these problems, anyway, enlightened me on how effective is the log system in Linux and the common suggestion to solve problems was, first of all and always, looking at the log in /var/log/messages, that is a record of everything Linux does in background or not.
That's how, after few minutes of searching and reading, that I stumbled upon this line:

Nov 23 09:49:01 acer avahi-daemon[1290]: write(): No space left on device
Nov 23 09:49:01 acer avahi-daemon[1290]: Failed to create PID file: No space left on device

That's even too clear. What seemed a serious problem on some damaged part of my distro was, instead, a problem of carelessly leaving the hard-disk with few bytes not even sufficient to start Gnome.

Deleting some files to free some space through terminal or using a live cd was enough to bring Gnome fully working again!

This is just to prove that sometimes problems that seem too complicate, can be solved just looking at a description of what is going on in the machine, given in detail by the machine itself.
Such an elegant service must not be wasted googleing the problem without mercy but, in most of the cases, "problems" can be solved locally using logs, man pages and your brain.

Hope I've learned the lesson!


Edit: thread found on fedoraforum.org (that is an excellent support forum, anyway) about a similar issue.