This seems awfully heavy handed for resolving something that needs to be
fixed in the kernel in the first place.  Aside from a server side inode
depletion problem, the access times on tmp would soar as users collided
during path lookup.

What exactly are the race conditions that are problematic?

Bill

>----------
>From: 	explorer@flame.org[SMTP:explorer@flame.org]
>Sent: 	Sunday, February 23, 1997 7:09 PM
>To: 	tech-kern@NetBSD.ORG
>Subject: 	Per-user temp storage
>
>
>With the popularity of race conditions involving /tmp and such, would
>the idea of a per-user temporary storage space be helpful?
>
>I was thinking of modifying the memory filesystem to do some magic
>based on the user using /tmp.
>
>Root would have full access to tmp, via /tmp/all/
>Any user can put things in /tmp/common/ which would be "shared" just like
>/tmp is now.
>Accessing simply /tmp would make a special location just for that user,
>where files placed there are not accessable by the other users.
>
>Has anyone tried something like this, or will this break too many things?
>
>If one was clever /tmp could even automatically expire based on userid
>and last access time, perhaps.
>
>--Michael
>