Date: Mon, 26 May 2008 20:54:05 +0400 From: Andrew Pantyukhin <infofarmer@FreeBSD.org> To: Chuck Swiger <cswiger@mac.com> Cc: Grant Peel <gpeel@thenetnow.com>, freebsd-questions@freebsd.org Subject: Re: Required Directories Message-ID: <20080526165403.GT92161@amilo.cenkes.org> In-Reply-To: <369C3C67-9A6F-419A-AA25-FA62D8FD3425@mac.com> References: <2EEC06F1F9B24B31B15CE1DCD095A7C1@GRANT> <369C3C67-9A6F-419A-AA25-FA62D8FD3425@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 26, 2008 at 09:03:29AM -0700, Chuck Swiger wrote: > On May 26, 2008, at 7:30 AM, Grant Peel wrote: >> I have several servers that the users home directories contain directories >> that must exists in order for apache and mail to work correctly. >> [ ... ] >> Is there a way (by using either proftpd, or setting sticky bit, or setting >> the uimmutable flag), that I can prevent the users from deleting these >> directories, and still retain the ability for my (root run) scripts to >> have the ability to delete them? In the hosting environment I manage, I use UFS flags extensively. Checkout chflags(1) manpage, schg and sunlnk flags in particular. > It's generally not expected that users would not own the stuff > under their homedir, or would not be able to delete their files > if they want to, even if doing so would break something. > Normally, sysadmins code their scripts to re-create any missing > directory hierarchy if needed, so that if a user manages to > shoot themselves in the foot, the cron jobs will be able to > provide first aid. I don't know what kind of sysadmins you're talking about, but, say, if a hoster did not support files with non-ascii names, but let me upload them and then just remove them automatically, I would not be happy. Preventive policies work better for me.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080526165403.GT92161>