RE: Mandatory file locking on Linux: sgid bit set by default on files. Possible?

"Matt T. Duval" <[email protected]> Mon, 6 Dec 2004 08:18:23 -0700
Newsgroups gmane.network.ftp.wuftpd.user
Message-ID <F19EDEADE3AC644DA814AB5F325D71B5012959AB@ht-mail.denver.healthtrans.com>
We simply upload the file as <filename.working> and then rename it to
<filename> after the upload is complete. 


Thank you,

Matt Duval
Sr. Network Engineer
HealthTrans
www.healthtrans.com
(720) 493-8252
6061 South Willow Drive
Suite 125
Greenwood Village, CO 80111
"Transforming Healthcare, One Transaction At A Time"

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Steve Bright
(IS Dept)
Sent: Monday, December 06, 2004 4:00 AM
To: '[email protected]'
Subject: Mandatory file locking on Linux: sgid bit set by default on
files. Possible?

Hi,

I need to use mandatory file locking on Linux to prevent users
downloading a file that is still being uploaded.  To enable the
mandatory locking, the sgid bit must be set at file creation (note: this
is not related to sgid on directories).  

I realise this is not possible with umask, but was wondering if there
was a configuration option or patch available to support this
requirement?

Regards,
--
Steve Bright




_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed
Scanning Services - powered by MessageLabs. For further information
visit http://www.mci.com