Comments on From the Canyon Edge - :-Dustin Kirkland: Cogito Errno Sum

Proposed fixes in that branch. I see a number of ...

2010-08-01T10:13:58.787-05:00

Proposed fixes in that branch. I see a number of people have suggested some code and code improvements to solving that. If you would, please create a branch and link it to that bug.

Thanks!
:-Dustin

Sounds good, Matt. See Bug #612267: https://bugs...

2010-08-01T09:42:42.935-05:00

Sounds good, Matt. See Bug #612267:

https://bugs.edge.launchpad.net/ubuntu/+source/linux-meta/+bug/612267

:-Dustin

I have written far too many one-liners to do this....

2010-07-31T16:13:43.475-05:00

I have written far too many one-liners to do this. It would be nice to have a script bundled with some standard package.

How about linux-tools?

Interesting. Oracle has long had a utility, oerr: ...

2010-07-29T01:18:05.506-05:00

Interesting. Oracle has long had a utility, oerr:

$ oerr ora 12544
12544, 00000, "TNS:contexts have different wait/test functions"
// *Cause: Two protocol adapters have conflicting wait/test functions.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.

Took your alert alias from the other day and did t...

2010-07-27T09:27:35.169-05:00

Took your alert alias from the other day and did the following so that I have a text representation of the error in the alert:

function errno_helper {
REALNUM=$?
NUM=$REALNUM

if [[ $NUM -eq 0 ]]; then
TXT="GOOD"
else
TXT=`errno $NUM | awk '{print \$1;}'`
fi

if [[ -z $TXT ]] ; then
TXT="unknown"
fi

echo -n "$REALNUM:$TXT"
}

alias alert_helper='history|tail -n1|sed -e "s/^\s*[0-9]\+\s*//" -e "s/;\s*alert$//"'
alias alert='notify-send -i /usr/share/icons/gnome/32x32/apps/gnome-terminal.png "[$(errno_helper)] $(alert_helper)"'

I Hate, Hate, HATE useless pipes and extra overhea...

2010-07-27T09:11:55.557-05:00

I Hate, Hate, HATE useless pipes and extra overhead. I use them too often and I'm trying to teach myself better.

#!/bin/bash
headers="/usr/include/asm-generic/errno*.h"

if grep -q '[0-9]' <<< "$1"; then
awk -v c="$1" '$1=""; $3==c {print}' $headers
else
awk -v c="$1" '$1=""; $2==c {print}' $headers
fi

I use: perl -MPOSIX -e 'print strerror('$...

2010-07-27T08:57:53.715-05:00

I use:

perl -MPOSIX -e 'print strerror('$1'),"\n";'

or

python -c 'import os;print os.strerror('$1');'

Marius, good point. Updated the post text ;-) :-...

2010-07-27T08:57:40.388-05:00

Marius, good point. Updated the post text ;-)

:-Dustin

I've always used perl -e 'print $!=36, &q...

2010-07-27T08:39:19.028-05:00

I've always used

perl -e 'print $!=36, "\n"'

(which is too much typing for my tastes, and doesn't show the short EXXX name).

However just a note: POSIX *error* codes have nothing to do with program *exit* codes, so this post doesn't really have anything to do with your previous one. *Exit* codes are either an arbitrary value that a program decides to return (0 for success, non-zero for error) _or_ 128 + signal number (so a SIGSEGV would result in the program returning 139). kill -l displays signal numbers.

Kay, et al., Thanks for the suggestions! I have a...

2010-07-27T06:47:41.332-05:00

Kay, et al., Thanks for the suggestions!

I have added -w to the grep to fix the problem where multiple results are returned.

And yes, of course, Ubuntu has a manpage for errno(3), but this tool grabs just the one line I need ;-)

:-Dustin

Of course decent operating systems contain a manua...

2010-07-27T03:40:29.303-05:00

Of course decent operating systems contain a manual page for all error codes...

You can do something similar with a perl one-liner...

2010-07-27T02:05:16.736-05:00

You can do something similar with a perl one-liner. For instance, the following prints the errors from 1 to 131:

perl -e 'foreach $a (@ARGV){$!=$a;printf("%d\t%s\n",$!+0,$!)}' {1..131}

Wow, really useful, thanks! Only one set of \W met...

2010-07-27T01:52:20.083-05:00

Wow, really useful, thanks! Only one set of \W metachars around the $code doesn't weed out unwanted lines, however:
errno 3
ESRCH 3 /* No such process */
EL3HLT 46 /* Level 3 halted */
EL3RST 47 /* Level 3 reset */

Either
grep -h "\W\W$code\W\W" $headers
or
grep -wh "\W$code\W" $headers

does the trick:
errno 3
ESRCH 3 /* No such process */

Very good! Sometimes, it's the little things t...

2010-07-26T22:30:51.456-05:00

Very good! Sometimes, it's the little things that count, especially when trying to fix an "Abort/Retry/Fail"-style error message in a program!
Something to look at if you ever have too much time on your hands; I found a little bug in it. If you search for errno 2 or 3, you get three results, because other numbers have '2' and '3' in their descriptions. Not sure if it happens for other numbers, or if you can filter it out (my bash-fu is very weak). It's not really a big deal, since I know which number I was looking for and can just ignore the other two.
Thanks again for coming up with this, it'll be really helpful!