AboutWelcome to Free Software Daily (FSD). FSD is a hub for news and articles by and for the free and open source community. FSD is a community driven site where members of the community submit and vote for the stories that they think are important and interesting to them. Click the "About" link to read more...
Bash error messages, like so many error messages, can be more cryptic than helpful. But the good news is bash has a built-in mechanism for creating your own customized error messages, and you don't have to be an ace programmer to do it. Ubuntu and openSUSE already use this; Akkana Peck shows us how to do it ourselves.
I'm sure we have all seen error or fail messages while ubuntu is starting (server or desktop version). Because Ubuntu really loads fast sometimes we don't have enough time to actually read what module fail to load or what is causing errors.
Logwatch Error - Logwatch is a program that will parse your logs and send you an email every day about what has taken place on your server, a very friendly program. With Ubuntu I kept getting this error, though I checked, I could not find a solution so, as it looked like it was missing a location /var/cache/logwatch, I created one and it worked perfectly.
Today, I did a fresh installation of Ubuntu 9.04 inside virtual box. My original idea was to play with sudoers and sudo command. I edited /etc/sudoers and logged out. Next time I tried to sudo , I go some parse error in /etc/sudoers. I was stuck . I needed sudo for modifying the file. But sudo was preventing me because of the error.
One writer's vision of an error reporting system meant to serve users and not the manufacturer of the system--sparked by Microsoft's unwillingness to speak with him about Windows Error Reporting