ok:
1) Free drive space
about 300Mb free on /
several gig free on /home
2) Memory (free and total)
at this moment:
total used free shared buffers
cached
Mem: 63056 61492 1564 17856 1308
14268
-/+ buffers/cache: 45916 17140
Swap: 104384 6212 98172
is there a way to free up more ram? i am planning to purchase more, but
it seems that 1.5 meg free is a bit bad. i am running X though.
3) Hardware -- processor, video card, motherboard/chipset, etc
Pentium II 350MHz
64 meg ram
linux lives on a 6.4 gig WD hd, windows lives on a 4.3 gig WD hd
Diamond stealth 3d video card (S3 virge gx2 video chipset)
dont remember the motherboard, but i can look it up if necessary
4) SCSI or IDE
ide
5) Anything else even remotely relevant!
this didnt happen with these particular programs in 6.0. i did a
clean upgrade to 6.1. i dont have another machine handy (except my Palm
IIIx!) to telnet in with.
regular xterm locks sometimes too. :( its getting to the point
where i cant run a terminal in X. i dont need to tell you why that
sucks.
another thing i might try is to use the old gnome-terminal from 6.0 and
see if that works. anyone know how to get a single file out of an rpm?
:P
John Aldrich wrote:
>
> On Sun, 03 Oct 1999, you wrote:
> > can someone in the know give me any hints as to what to do about some
> > software that locks the computer. everytime i run the gnome-terminal,
> > it locks the computer so that nothing works except for a hard reset. i
> > have tried reinstalling gnome-core*.rpm by overwriting or deleting and
> > then reinstalling. i am also having trouble with some of the
> > screensavers that lock up the system as soon as they start. is there
> > something i can do about it? deleting and reinstalling doesnt do it.
> > would recompiling help? why is it locking my machine but not others? i
> > have checked my system logs and nothing is mentioned about the offending
> > software. i am running 6.1.
> >
> Please give us some information about your system:
> 1) Free drive space
> 2) Memory (free and total)
> 3) Hardware -- processor, video card, motherboard/chipset, etc
> 4) SCSI or IDE
> 5) Anything else even remotely relevant!
>
> As a suggestion....if you have another machine handy, try telnetting
> to your "locked" machine (or get and install SSH if you don't want to
> leave Telnet open) and issue the reboot command remotely.
> John
