G'day Myles and all... > I've just had a very unfortunate experience where openoffice (1.1) has > crashed on me and taken down the entire gnome session with it. > > Of course it was a new document and I hadn't yet saved it (I know, I > know). Gnome dumped a pretty big core file but from what I
I've also found OpenOffice to exhibit this type of behaviour when opening a document. The system seems to freeze or slow right down for a while. I'm guessing it's a fairly resource intensive at this time. (If I wait an arbitary length of time, system performance improves and I find the document loaded.) > Also I'm not sure if this is relevant but the 'init' process has been > using all cpu resources since I started my new gnome session. init is a process that starts and stops services. If it's resource hungry, it's because it's busy managing processes. Run few or no applications other than OpenOffice. Be patient, at times the machine may appear to be frozen. Also, ensure that services that aren't required are turned off. init is a special kind of process - it's started by the operating system, always has a process id of 1 and doesn't have any parent process (unlike all other processes which all have init as their highest ancestor). The configuration file for init is /etc/inittab. Other suggestions would be to either switch to a less resource intensive window environment or to turn off any extra features of gnome. (Sorry, I'm not a gnome expert.) HTH... Mike -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
