On Fri, Mar 26, 2010 at 06:20:06PM -0400, rgheck wrote: > On 03/26/2010 06:16 PM, Enrico Forestieri wrote: > >On Fri, Mar 26, 2010 at 06:08:58PM -0400, Richard Heck wrote: > > > >>On 3/26/10 5:50 PM, Enrico Forestieri wrote: > >>>On Fri, Mar 26, 2010 at 01:30:18PM -0400, rgheck wrote: > >>> > >>>>On 03/26/2010 01:11 PM, rgheck wrote: > >>>>>A user noted that, by putting the converter cache in the user > >>>>>directory, we risk running people over their disk quotas, since > >>>>>that cache can get fairly large. The attached moves the cache to > >>>>>LyX's temporary directory. Does anyone know a reason not to do > >>>>>this? > >>>>> > >>>>Ahh, I see the reason, namely, that the converter cache is supposed > >>>>to be persistent. So, putting it in LyX's temporary directory won't > >>>>work, since that gets deleted. The other option, then, is to put it > >>>>in the system temporary directory somehow, but (a) it can't just be > >>>>/tmp/lyx-cache/ on a multi-user system and (b) it can't be > >>>>/tmp/some-random-name/, because we need to be able to find it again. > >>>>Is there any way we could do something like this: > >>>>/tmp/lyx-username-cache/? I.e., is there some cross-platform way to > >>>>find a username? > >>>Note that the /tmp directory gets nuked on reboot. Then, I don't think > >>>that it is a good idea spreading files around in the file system. > >>> > >>Not here, but you're right that some systems do nuke it. > >> > >>Any other ideas, then? This does seem to be a real problem for some people. > >Several: > >1. Disable cache. > >2. Softlink the cache dir somewhere else. > >3. Use the -userdir flag when launching lyx. > >4. Set the LYX_USERDIR_16x to a place with plenty of room. > > > So far as I can see, only the first is likely to work in the case > the user reported. Or maybe the second, but that's fairly > sophisticated.
Uh? Using a flag or setting an env var is considered sophisticated? -- Enrico
