> As for the smb.conf file to the best of my knowledge it is correctly
> configured, is there some specific directives I should check?
> I'm not sure of any specific directives, but you could try adding in
> things like "writable = yes" and "public = yes" which
*should* bypass
> any permission checks that Samba does. You could also run smbd in
> debug mode and see if you get any strange errors when attempting a save.
Start LOG ____________
[2006/01/30 10:37:41, 0] lib/fault.c:fault_report(36)
==============================================================[2006/01/30
10:37:41, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 10 in pid 2832 (3.0.21a)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/01/30 10:37:41, 0] lib/fault.c:fault_report(39)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/01/30 10:37:41, 0] lib/fault.c:fault_report(40)
==============================================================[2006/01/30
10:37:41, 0] lib/util.c:smb_panic2(1554)
PANIC: internal error
[2006/01/30 10:37:41, 1] smbd/service.c:make_connection_snum(666)
omwl (IP ADDRESS) connect to service home initially as user jjohnson
(uid=XXXX, gid=XXX) (pid 3680)
[2006/01/30 10:37:41, 0] lib/fault.c:fault_report(36)
==============================================================[2006/01/30
10:37:41, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 10 in pid 3680 (3.0.21a)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/01/30 10:37:41, 0] lib/fault.c:fault_report(39)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/01/30 10:37:41, 0] lib/fault.c:fault_report(40)
==============================================================[2006/01/30
10:37:41, 0] lib/util.c:smb_panic2(1554)
PANIC: internal error
[2006/01/30 10:37:43, 1] smbd/service.c:make_connection_snum(666)
omwl (IP ADDRESS) connect to service home initially as user jjohnson
(uid=XXXX, gid=XXX) (pid 3681)
[2006/01/30 10:37:43, 0] lib/fault.c:fault_report(36)
==============================================================[2006/01/30
10:37:43, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 10 in pid 3681 (3.0.21a)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/01/30 10:37:43, 0] lib/fault.c:fault_report(39)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/01/30 10:37:43, 0] lib/fault.c:fault_report(40)
==============================================================[2006/01/30
10:37:43, 0] lib/util.c:smb_panic2(1554)
PANIC: internal error
[2006/01/30 10:37:43, 1] smbd/service.c:make_connection_snum(666)
omwl (IP ADDRESS) connect to service home initially as user jjohnson
(uid=XXXX, gid=XXXX) (pid 3682)
End Log________________
I read the Samba3-HOWTO.pdf and found no pertinent information.
> You're definitely sure that doing the same thing with say Notepad
> works? (save as, and saving over the top of something?) You can rename
> files okay through Windows Explorer?
The problem only occurs with MS Word, all other MS products work fine.
I have no problem copy, deleting, renaming, or any other function.
> I know that I used to have a problem saving through Word because when I
> pressed the 'Save' button Word would create a temporary file to see
if
> it had write access to the disk, but then when it tried to re-open that
> temp file to write the document into it it would fail, because the file
> wasn't owned by the same user connecting to the share (e.g. even though
> "bob" was using Word, any files that "bob" created
where owned by
> "john" in the underlying filesystem, which Samba then refused to
give
> "bob" access to.)
-rwxrw-r-- 1 jeff group 179 Jan 30 10:34 Test.rtf
-rwxrw-r-- 1 jeff group 0 Jan 27 10:52 ~WRL0607.tmp
First is a file from MS Wordpad the second is a temp file from MS Word.
> This particular problem meant that I had issues with other programs
> though, but I was able to copy files into the share with Explorer (just
> not delete them again.)
> Sorry I couldn't be more helpful!
Any help would be useful as this problem did not occur before the upgrade to
v3.0.21a but I know we talked about it last year at some point.
Jeff