Re: Users using /tmp as a storage space.

["Mikhail Romanenko" <mikhail@angg.ru>]

----- Original Message -----
From: Brian Harring <bdharring@wisc.edu>
To: <linux-admin@vger.kernel.org>
Sent: Thursday, March 20, 2003 7:14 PM
Subject: Re: Users using /tmp as a storage space.


> Andrew Kelly wrote:
> >  > 05  01  *   *   *   exec 'rm -rf /tmp/*'
> >
> >That's a bit too "brute force", and could interfere with normal
> >operation. It would better to only delete files that are more than X
> >hours old.
>
> Speaking from experience, I don't think that's too good of a way of
> doing it either- I know x-windows and kde both use unix sockets that
> are stored in /tmp.  If you brute force delete them, you're going to
> cause problems for any x-windows session that is currently going.
> Also, if I recall correctly, mysql stores it's unix socket there too-
> deletion of that would/should cause problems for programs that access
> mysql locally.

From my experience common users mostly use Windows on thir client computers
and access linux server via samba. I use /bin/false as default shell while
creating
a new user. In such cases I use /var/local/tmp as \\<servername>\tmp samba
resource
and disable /tmp in smb.conf which is enabled by default. Keeping in mind
that
only samba users use /var/local/tmp no "brute force" could interfere with
normal
operation.
What about users who have /bin/sh as a shell they are experienced enough to
understand explanation how they should (and should not) use /tmp. In my case
from about 150 users only two (me, as system administrator, and one more
guy),
and system pseudousers have /bin/bash as a shell.

Mikhail.