SAMBA digest 2424

Cliff Green green at UMDNJ.EDU
Tue Feb 22 18:09:14 GMT 2000


On Wed, 23 Feb 2000, samba at samba.org enscribed thusly:
>Date:   Tue, 22 Feb 2000 14:35:34 -0000
>From:   "krcsamba" <krcsamba at eilis.net>
>To:     "Multiple recipients of list SAMBA" <samba at samba.org>
>Subject: File locking with source

[munch]

>Can you please help or point me in the correct direction to solve the
>following problem
>
>We have an old stock control program which runs on all types of MS os's from
>DOS to NT4. However, It refuses to lock correctly on a samba server (Version
>samba-2.0.6-19991110.386.rpm).
>
>When both the file and lock program are placed in the same directory and the
>lock program run from a dos prompt on one machine the other machine refuses
>to lock the file correctly (program on second machine returns an error code
>of 80)

[munch]

It sounds like your locks are being created by the first user, but the
second user's not being permitted to.

A long shot:

What happens when you do the following?

1) in smb.conf, in the section defining the share where your locks are,
you add "writeable = yes" and "force create mode = 0766", and then
2) set the sticky bit on the directory in which your lock files are
written?

c
--
Cliff Green				green at umdnj.edu
Academic Computing Service			  UMDNJ



More information about the samba mailing list