will leave /tmp on the / for now.
On Fri, 2006-04-07 at 08:04 -0500, Corey Wright wrote:
> On Fri, 07 Apr 2006 14:11:27 +0300
> Nikolay Kichukov <email@example.com> wrote:
> > in /etc/vservers/vn/fstab:2:1: I have:
> > none /tmp tmpfs size=16m,mode=1777 0 0
> > So, if I did not enable the tmpfs file system in the kernel, is there
> > any other option I can mount the /tmp in the guest?
> yes, you can remove that line and let /tmp be on the same filesystem as / (within the guest).
> i have a large number of vservers (one for each externally accessible application; i use vserver like an industrial chroot) and didn't like the fact that for some applications a 16 MB /tmp was insufficient and for some applications /tmp went complete unused. using tmpfs was a problem in the first situation and non-beneficial in the second, so i got rid of its use.
> for short-lived files they might be held (cached) in RAM anyways. even if not, prioritized i/o should keep one application from slowing the system down too much by using/abusing /tmp (being stored on disk, as compared to much faster RAM).
> that's what i did and my reasoning, and it's worked for me.
Vserver mailing list
Received on Fri Apr 7 15:20:10 2006