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) I've included the Executable, Source code and Lock file If we I can't get this to work I'm going to have to resort to using a MS os (HELP!!) Kevin Clarke -------------- next part -------------- A non-text attachment was scrubbed... Name: testlock.exe Type: application/x-msdownload Size: 802 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20000222/bd072c27/testlock.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: file01.lok Type: application/octet-stream Size: 9 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20000222/bd072c27/file01.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: testlock.asm Type: application/octet-stream Size: 1726 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20000222/bd072c27/testlock.obj
On Wed, 23 Feb 2000, samba@samba.org enscribed thusly:>Date: Tue, 22 Feb 2000 14:35:34 -0000 >From: "krcsamba" <krcsamba@eilis.net> >To: "Multiple recipients of list SAMBA" <samba@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@umdnj.edu Academic Computing Service UMDNJ
We have a similar problem with 2.0.6 on Compaq Tru64 (previously Digital) Unix 4.0F. This share is for NT roaming profiles and works fine with 2.0.5a. [2000/02/23 00:59:51, 1] smbd/service.c:(535) peevish (128.101.220.114) connect to service profiles as user allan (uid=5000, gid=5000) (pid 920) [2000/02/23 00:59:51, 0] lib/util_sec.c:(52) Failed to set uid privileges to (0,5000) now set to (5000,5000) [2000/02/23 00:59:51, 0] lib/util.c:(2456) PANIC: failed to set uid util_sec.c does appear much changed from 2.0.5a but I don't know the cause of the problem. I have too many variables which have changed since building 2.0.5a to be sure of anything (new OS version, patches, C compiler...). I can only guess it is the call to unbecome_user() in smbd/service.c which is failing. It is almost behaving as if we have a trapdoor uid system (as I understand it), despite never being a problem in previous Samba versions. Graham> Has there been any reported errors on Set Uid commands for HP-UX 11.00. I > am receiving the following messages whenever a share is added. > > [2000/02/21 15:17:05, 3] > /tmp/samba-2.0.6/source/smbd/password.c:authorise_login(784) > ACCEPTED: guest account and guest ok > [2000/02/21 15:17:05, 3] > /tmp/samba-2.0.6/source/smbd/service.c:make_connection(426) > Connect path is /tmp > [2000/02/21 15:17:05, 0] > /tmp/samba-2.0.6/source/lib/util_sec.c:assert_uid(54) > Failed to set uid privileges to (-1,-2) now set to (0,0) > [2000/02/21 15:17:05, 0] /tmp/samba-2.0.6/source/lib/util.c:smb_panic(2456) > PANIC: failed to set uid > > It seems to happen on all shares. I have 2.0.6 running on a 10.20 machine > without these issues.