[Samba] App fails writing file but zero length file on Samba server

[Jeremy Allison]

On Thu, May 28, 2009 at 08:57:26AM +0800, Colin Coe wrote:
> Hi all
> 
> I've googled but not found any thing on the problem I'm having.
> 
> I'm contracting with a utilities company that uses General Electric's
> ENMAC software.  This runs on RHEL4 and makes use of Samba but it only
> works with Samba 1.9.18p10 compiled with this patch:
> ---
> diff -Naur samba-1.9.18p10/source/includes.h
> samba-1.9.18p10_good/source/includes.h
> --- samba-1.9.18p10/source/includes.h   1998-08-20 07:41:46.000000000 +0800
> +++ samba-1.9.18p10_good/source/includes.h      2008-01-11
> 10:39:49.000000000 +0900
> @@ -1176,7 +1177,7 @@
>  #include <sys/ipc.h>
>  #include <sys/sem.h>
>  #include <sys/shm.h>
> -#ifdef NO_SEMUN
> +#ifdef _SEM_SEMUN_UNDEFINED
>  union semun {
>         int val;
>         struct semid_ds *buf;
> ---
> 
> As I'm trying to streamline the building of these servers, I thought
> I'd try upgrading Samba to a reasonably current version.  I'm trying
> with latest version of Samba shipped by RedHat (3.0.33-0.17.el4).
> 
> When an edit is made and then saved in the application, the
> application responds with 'Failed to open file for writing' and on the
> Samba server a zero length file of the correct name appears.  This
> works just fine with the patched Samba 1.9.18p10.
> 
> The smb.conf files are attached.
> 
> Does anyone have any ideas on how to make this work without patching Samba?

Wow, it's a long time since I've seen anyone using such a vintage
version of Samba. 1.9.18p10 was definately a popular build :-).

Can you try using the latest version of Samba, 3.3.4, and see if
the problem is reproducible ? If so, we'll ask you to open a bug
report and get more data.

Thanks,

Jeremy.