On Sep 25, 2009, at 19:39, Frank Middleton wrote:
/var/tmp is a strange beast. It can get quite large, and be a
serious bottleneck if mapped to a physical disk and used by any
program that synchronously creates and deletes large numbers of
files. I have had no problems mapping /var/tmp to /tmp. Hopefully
a guru will step in here and explain why this is a bad idea, but
so far no problems...
The contents of /var/tmp can be expected to survive between boots
(e.g., /var/tmp/vi.recover); /tmp is nuked on power cycles (because
it's just memory/swap):
/tmp: A directory made available for applications that need a place
to create temporary files. Applications shall be allowed to create
files in this directory, but shall not assume that such files are
preserved between invocations of the application.
http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap10.html
If a program is creating and deleting large numbers of files, and
those files aren't needed between reboots, then it really should be
using /tmp.
Similar definition for Linux FWIW:
http://www.pathname.com/fhs/pub/fhs-2.3.html
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
