On Fri, 2007-12-07 at 16:03 +0200, Oron Peled wrote:
> On Friday, 7 בDecember 2007, Oded Arbel wrote:
> > The first call that is interesting is of course the open()
> > for /etc/protocols. In the second test (after I did ls /etc/protocols)
> > it looks normal:
> > open("/etc/protocols", O_RDONLY|0x80000 /* O_??? */) = 8
> > but in the first test is looks like this:
> > open("/etc/protocols", O_RDONLY|0x80000 /* O_??? */) = -530
> >
> > Reading man 2 open, it says that open() should return -1 in case of an
> > error.
> >
> > I'm still looking as to what -530 means, but I've yet to find anything
> > on the web.
>
> You wouldn't. An strace would show you the return value (which should be -1
> for an error, and a translation to errno definition). The -530 heavily hints
> that you have somehow corrupted glibc (or kernel, or both). Another option
> is a simple memory hardware problem. However, I'm not sure if you can run
> memtest86+ in your hosting environment.
>
> If something still functions on this system, than an:
>
> rpmverify glibc kernel
>
> May shed more light.
rpmverify glibc kernel return nothing (exactly nothing, no output
whatsoever - I assume that it means there are no errors). Except for the
weird inaccessibility of files until I get a shell to list them (and
then possibly only for /etc though I doubt it), everything works
correctly.
--
Oded
================================================================To unsubscribe,
send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
