Re: exu not working

new topic     » goto parent     » topic index » view thread      » older message » newer message

On Sat, Feb 08, 2003 at 10:55:57AM -0000, tubby.toast at ntlworld.com wrote:
> 
> > btw, Chris, what does typing "file `which exu`" give you?
> 
> bash-2.05a$ file`which exu`
> /home/chrissy/bin/exu: ELF 32-bit LSB executable, Intel 80386, version 1
> (SYSV),
>  statically linked, stripped
> 
> chris.

No doubt about it, the exu binary is the same one as mine, and exu itself
is working fine. Being staticly linked, its not a linker or missing library
error. And, when run, it doesn't do anything and just returns an exitcode of
127. Since no error message is emited, it _probably_ isn't an ncurses error.
I know what its not, but I'm out of ideas to guess what it might be.

Are any other programs of yours acting funny like this? Anything else go odd
on the server once it was upgraded? or was it just exu?

And, do you know, what the server was upgraded from?

jbrown

> 
> 
> 
> TOPICA - Start your own email discussion group. FREE!

-- 
 /"\  ASCII ribbon              | 
 \ /  campain against           | Linux User:190064
  X   HTML in e-mail and        | Linux Machine:84163
 /*\  news, and unneeded MIME   |

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu