l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
April 21: Google Glass
Next Installfest:
TBD
Latest News:
Mar. 18: Google Glass at LUGOD's April meeting
Page last updated:
2003 Jul 01 15:21

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] openoffice: annoying message and load time
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] openoffice: annoying message and load time



On Tue, Jul 01, 2003 at 02:09:01PM -0700, Tim Riley wrote:
> From: Tim Riley <timriley@timriley.net>
> To: vox-tech@lists.lugod.org
> Subject: Re: [vox-tech] openoffice: annoying message and load time
> Date: Tue, 01 Jul 2003 14:09:01 -0700
> X-Mailer: Mozilla 4.7 [en]C-CCK-MCD EBM-Compaq  (Win95; U)
> Reply-To: vox-tech@lists.lugod.org
> 
> 
> 
> Peter Jay Salzman wrote:
> 
> > using open office for stressful job hunting, and there are a few
> > annoyances that i'd like to ask about.
> >
> > question 1
> > ----------
> > 1. load an .sxw document
> > 2. save as .doc document
> > 3. file | quit
> >
> > open office now asks me if i really want to save because there might be
> > information loss in the new format.
> >
> > i don't mind being warned that i'm quiting the program with unsaved
> > changes, but this warning is just useless for me.  is there a way of
> > turning it off?
> >
> > question 2
> > ----------
> > i'm unhappy with the load time of open office.  is there any way to
> > decrease load time by keeping the code segment resident in memory, even
> > if i quit open office?  would setting the sticky bit on soffice.bin do
> > this?
> 
> This would make a good, cheap experiment to perform. My guess is that
> setting
> the sticky bit will speed the re-execution of the process if your system
> is heavily loaded, but it won't speed up the re-execution if lightly
> loaded.
> If the system is lightly loaded, the process stays in memory anyway. Only
> when the memory fills up will those pages start being reused by another
> process. Setting the sticky bit tells the memory manager to not reuse
> code segments after the last process exits.

I don't think setting the sticky bit will do anything.  From the chmod
manpage:

    On older Unix systems, the sticky bit caused executable files to be
    hoarded in swap space.  This feature is not useful on modern VM sys-
    tems, and the Linux kernel ignores the sticky bit on files.  Other
    kernels may use the sticky bit on files for system-defined purposes.
    On some systems, only the superuser can set the sticky bit on files.



Matt

-- 

*************************************************
* Matt Roper <matt@mattrope.com>                *
* http://www.mattrope.com                       *
* PGP Key: http://www.mattrope.com/mattrope.asc *
*************************************************
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!