>>> As an example I state two of them: How near
>>> to SystemV are getting?
>>> Isn't /etc/profile.d/tmpdir.* a little bit
>>> dangerous for users with homes in NFS/SAMBA
>>> or with very narrow quota? Shouldn't be made
>>> a "pre-check" before setting TMPDIR?
>>
>> this is a side i didn't check, you may are
>> right but i don't see exactly the problem ?
>
> The problem is the possbility of fast overloads
> of home directory. Temporary files are very
> "specific" to their programs. In cases when
> programs can't write to their configuration or
> temporary files, a set of problems may arise.
> Here we have a NFS homedirectory tree (10Mb
> quota). When the directories get loaded it is
> frequent to meet two conditions:
I thought I would mention something I noticed
regarding personal tmp/ directories.
I use "screen" a lot, at least more than the
average user. Each screen places a
pid.screenname file in tmp/. If a user has their
home directory stored on a central NFS server,
and is logged in on multiple machines, the screen
command is using the same tmp/ directory for all
it's screens, regardless of the system it's
running on. This opens the possibility of two
screens with the same name and process ID placing
a temporary file in the user's tmp/.
When running "screen -ls" on a system, any
screens running on another system (but in the
same tmp/ directory) show up as dead. It's then
very easy to "screen -wipe" a process that
actually is still running on another machine.
Just some food for thought..
Don Head [[EMAIL PROTECTED]]
Linux Mentor, LCP, Network+ [1 314 692-1942]
Wave Technologies, Inc. [1 800 826-4640 x1942]
[AIM - Don Wave][ICQ - 18804935][Yahoo - Don_Wave]
