Is /dev/shm needed?
Hello all :))
I don't know if /dev/shm (mounted with shmfs or the newer tmpfs)
is needed for proper SYSV IPC operation with newer (2.4.16 and newer) kernel. Anyone can help?
Moreover: I want to move my /tmp from disk to tmpfs for speed (I
make a lot of compiling, so I think it would help). Is this a good idea? If so, what size can be appropriate for a small system that is not permanently running?
Thanks a lot for the answers :))
Ra�l
Quoted 3 lines · RaúlNúñez de Arenas Coronado
I don't know if
/dev/shm(mounted with shmfs or the newer tmpfs)
is needed for proper SYSV IPC operation with newer (2.4.16 and newer) kernel. Anyone can help?
It is not needed. /dev/shm mounted with tmpfs is only needed for POSIX shared memory, which is still fairly rare. SysV IPC will work fine.
Quoted 4 lines
Moreover: I want to move my /tmp from disk to tmpfs for speed (I
make a lot of compiling, so I think it would help). Is this a good idea? If so, what size can be appropriate for a small system that is not permanently running?
Some say it helps, others don't. Solaris has a similar feature, and it seems to work for them. However, Linux is light and our page-cache works well. Not so sure it is ideal.
In other words, if you have memory to spare and the data ought to be cached, Linux probably will cache it anyhow. On the other hand, if you have lots of memory to spare, give it a try. Mount /tmp or all of /var in tmpfs.
It is dynamic, so you don't need to specify a size. If you want to give a maximum size (probably a good idea), give one. Depends on what your tmp usages are and how much free memory you have.
Robert Love
Quoted 2 lines · Robert Love
have lots of memory to spare, give it a try. Mount /tmp or all of /var in tmpfs.
What? /var contains things like /var/spool/mail. I _really_ doubt that mailboxes disappearing after reboot will make anyone happy.
Quoted 6 lines · Alexander Viro
Quoted 2 lines · Robert Love
have lots of memory to spare, give it a try. Mount /tmp or all of /var in tmpfs.
What? /var contains things like
/var/spool/mail. I _really_ doubt that mailboxes disappearing after reboot will make anyone happy.
The original impetus for separating /var from /usr was not that stuff in /var is temporary, but that anything that the system has to write to in the course of normal operation goes there... that was so that /usr could be a filesystem that was shared by many machines (i.e. NFS mount for diskless workstations, etc.) /var is for data that is "variable" from machine to machine, so that /usr can be "constant".
:j
Signature · 3 lines
Jürgen Botz | While differing widely in the various [email protected] | little bits we know, in our infinite | ignorance we are all equal. -Karl Popper
Quoted 4 lines · Robert Love
In other words, if you have memory to spare and the data ought to be cached, Linux probably will cache it anyhow. On the other hand, if you have lots of memory to spare, give it a try. Mount /tmp or all of /var in tmpfs.
Unfortunately, some(many?) distros are b0rken in re /var/. There is stuff put there that is needed across boots (for example, mandrake puts the DNS master files in /var/named.)
Quoted 6 lines
It is dynamic, so you don't need to specify a size. If you want to give a maximum size (probably a good idea), give one. Depends on what your tmp usages are and how much free memory you have.
Robert Love
Signature · 8 lines
tabris
Sweet is love when all is sane
Sweet is death to rid the pain
Cruel is death when all is well
Cruel is love when all is hell
Author unkownQuoted 9 lines · Adam Schrotenboer
Quoted 4 lines · Robert Love
In other words, if you have memory to spare and the data ought to be cached, Linux probably will cache it anyhow. On the other hand, if you have lots of memory to spare, give it a try. Mount /tmp or all of /var in tmpfs.
Unfortunately, some(many?) distros are b0rken in re
/var/. There is stuff put there that is needed across boots (for example, mandrake puts the DNS master files in/var/named.)
It's not just mandrake, it's all linux and in fact that's where the named data wants to live -
Not only dns info, but things like mail spool, system logs, cron files -
And it's not just linux, it's pretty much a unix thing in general -
Are you really sure you want to blow away everyone's mail, all your dns records, cron jobs etc if the system powers down?
cu
jjs