On Tue, 1 Jun 2021 at 11:44, Mark Davies <m...@ecs.vuw.ac.nz> wrote: > > > > On 1/06/21 10:24 pm, Chavdar Ivanov wrote: > > On Tue, 1 Jun 2021 at 11:08, Chavdar Ivanov <ci4...@gmail.com> wrote: > >> > >> Fails under FreeBSD 13 as well: > >> > >> root@f13:~xci # touch foo.txt > >> root@f13:~xci # cc -o s s.c > >> root@f13:~xci # ./s > >> fd = 3 > >> new_fd = -1 > >> root@f13:~xci # uname -a > >> FreeBSD f13 13.0-RELEASE FreeBSD 13.0-RELEASE #0 > >> releng/13.0-n244733-ea31abc261f: Fri Apr 9 04:24:09 UTC 2021 > >> r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > >> amd64 > > > > And under OpenBSD likewise: > > > > o64q$ gcc -o s s.c > > /tmp//ccoGvFqD.o: In function `main': > > s.c:(.text+0x6a): warning: sprintf() is often misused, please use snprintf() > > o64q$ touch foo.txt > > o64q$ ./s > > fd = 3 > > new_fd = -1 > > o64q$ uname -a > > OpenBSD o64q.lorien.lan 6.4 GENERIC.MP#2 amd64 > > > > So there is a theme, I guess... > > OK so is the latest samba (4.14.x) working on FreeBSD or OpenBSD? > > As the issue that lead me to track down this difference from Linux is > that since 4.14.0 if I have a samba share exported to windows and try to > edit any existing file (with for example notepad) and go to save the > changes it fails with a "File exists" dialog box, but works for the same > samba on Linux. > > older samba (4.13.7) works fine on NetBSD, but the 4.14 seems to have > reworked how they do opens to do this reopen via /proc thing. >
Yes, I have 4.14.4 on my -current laptop; it is configured as a DC and I thought there is a problem there, but it does behave as you describe - even a second save of a newly created file fails. > cheers > mark -- ----
