From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mikhail Romanenko" Subject: Re: Users using /tmp as a storage space. Date: Fri, 21 Mar 2003 06:42:33 +0500 Sender: linux-admin-owner@vger.kernel.org Message-ID: <002101c2ef4b$250d27c0$01011fac@angg.ru> References: <3E798E3D.C3E4E840@transparency.org><15993.45907.188491.262337@cerise.nosuchdomain.co.uk> Reply-To: "Mikhail Romanenko" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-admin@vger.kernel.org ----- Original Message ----- From: Brian Harring To: 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 \\\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.