On Wed, 25 Jul 2018, wes wrote:
tmpfs and /tmp are not the same thing.
Wes, Yes. I'm reading about this. tmpfs is a filesystem that acts like a RAM disk and uses both RAM and swap.
... it looks like in one case you have a /tmp which uses tmpfs, but this is not required for anything to work. /tmp simply needs to be writable. have you tested that?
Yes, /tmp is writable. That's where alpine saves outbound e-mail messages and where SlackBuilds.org packages are placed when built and before being installed. What I've just learned is that tmpfs is supposed to be mounted on /dev/shm (for 'shared memory'?) with perms 1777. Now, /dev/shm has 4 old files none of which I need: -rw------- 1 postgres postgres 4620 May 27 08:12 PostgreSQL.149263255 -rw-rw-rw- 1 rshepard users 16 Jun 14 14:12 sem.ADBE_REL_rshepard -rw-rw-rw- 1 rshepard users 16 Jun 14 14:12 sem.ADBE_ReadPrefs_rshepard -rw-rw-rw- 1 rshepard users 16 Jun 14 14:12 sem.ADBE_WritePrefs_rshepard I think the problem is that tmpfs was somehow incorrectly mounted because /etc/fstab shows this: /dev/sda9 /tmp ext3 defaults 1 2 tmpfs /tmp tmpfs defaults,mode=1777 0 0 So, can I do this to correct tmpfs? # mount --bind tmpfs /dev/shm and not need to reboot? Thanks, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
