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

Hi Matt,

Unfortunately we already have multiple inbound and outbound connections from
customers systems.  It would be a logistical and political nightmare to get
them to make code changes for uploads.  In fact, some of them don't have any
in-house coders to do it.

If I can get wu-ftpd to set the sgid bit on file creation, file locking then
operates at kernel level.

Regards,
-- 
Steve Bright

-----Original Message-----
From: Matt T. Duval [mailto:[email protected]] 
Sent: 06 December 2004 15:18
To: Steve Bright (IS Dept); [email protected]
Subject: RE: Mandatory file locking on Linux: sgid bit set by default on
files. Possible?

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