On 27 Jan 2002, Andreas Goesele wrote:
>Cameron Kerr <[EMAIL PROTECTED]> writes:
>
>> Well, if the error is indeterminate, then I would start to suspect your
>> hardware. Errors such as this often indicate bad memory, in my
>> experience. Getting segfaults all the time is a classic example of this
* Andreas Goesele ([EMAIL PROTECTED]) spake thusly:
> Dimitri Maziuk <[EMAIL PROTECTED]> writes:
>
> > I'd ask on the kernel mailing list and/or on comp.os.linux.system.
>
> Thanks. But where would I find comp.os.linux.system? My news-server
> doesn't provide it nor did I find it on googles group
On Saturday 26 January 2002 05:48 pm, Andreas Goesele wrote:
[snip]
> The problem BTW returned again, now the third time, again only for
> some minutes. It started during a cron job and started and *ended*
> during heavy disk activity.
as i mentioned earlier, you should determine whether one of t
On Saturday 26 January 2002 04:25 pm, Andreas Goesele wrote:
[snip]
> I was thinking of that. But to my uneducated eye entries in cron.d,
> cron.daily, cron weekly and cron.monthly looked rather inoffensive. Or
> is there something in the following lists which could be the offender?
> Is there some
Cameron Kerr <[EMAIL PROTECTED]> writes:
> Well, if the error is indeterminate, then I would start to suspect your
> hardware. Errors such as this often indicate bad memory, in my
> experience. Getting segfaults all the time is a classic example of this.
>
> Get hold of memtest86 (http://www.tere
ben <[EMAIL PROTECTED]> writes:
> > Thanks. But would that explanation be compatible with the fact that my
> > system most of the time functions all-right and then suddenly for some
> > time (one day and then a few minutes) not? If libc.so.6 wasn't
> > backwards compatible I would expect that the
On Saturday 26 January 2002 03:34 pm, Andreas Goesele wrote:
[snip]
> > >> foo: relocation error: /lib/libnss_compat.so.2: symbol rectory,
> > >> version GLIBC_2.0 not defined in file libc.so.6 with link time
> > >> reference
> >
> > OK, GLIBC_2.0 refers to glibc5 (or 4?). Anyway, the likely reason
On 27 Jan 2002, Andreas Goesele wrote:
>Thanks. But would that explanation be compatible with the fact that my
>system most of the time functions all-right and then suddenly for some
>time (one day and then a few minutes) not? If libc.so.6 wasn't
>backwards compatible I would expect that the probl
Cameron Kerr <[EMAIL PROTECTED]> writes:
> >* Andreas Goesele ([EMAIL PROTECTED]) spake thusly:
>
> >> Simple description: Suddenly most programs won't start anymore but will
> >> give the error message:
> >>
> >> foo: relocation error: /lib/libnss_compat.so.2: symbol rectory,
> >> version GLIBC_
Dimitri Maziuk <[EMAIL PROTECTED]> writes:
> I'd ask on the kernel mailing list and/or on comp.os.linux.system.
Thanks. But where would I find comp.os.linux.system? My news-server
doesn't provide it nor did I find it on googles groups.
Andreas Goesele
>* Andreas Goesele ([EMAIL PROTECTED]) spake thusly:
>> Simple description: Suddenly most programs won't start anymore but will
>> give the error message:
>>
>> foo: relocation error: /lib/libnss_compat.so.2: symbol rectory,
>> version GLIBC_2.0 not defined in file libc.so.6 with link time
>> refe
* Andreas Goesele ([EMAIL PROTECTED]) spake thusly:
> Hi,
>
> my problem as described in <[EMAIL PROTECTED]> and with
> some more details in <[EMAIL PROTECTED]> returned, though
> only for some minutes.
>
> Simple description: Suddenly most programs won't start anymore but will
> give the error m
Hi,
my problem as described in <[EMAIL PROTECTED]> and with
some more details in <[EMAIL PROTECTED]> returned, though
only for some minutes.
Simple description: Suddenly most programs won't start anymore but will
give the error message:
foo: relocation error: /lib/libnss_compat.so.2: symbol rect
13 matches
Mail list logo
