On Thu, Jul 21, 2005 at 04:51:56PM +0200, Michael Gasch wrote:
> we have only seen the descripted behaviour on MacOSX with WordMac - not
> on windows!
>
> >fixed in Samba recently for IBM
> does that meen it should work with 3.0.14a or only for IBM's version of
> samba?
Ah - didn't spot that. I
we have only seen the descripted behaviour on MacOSX with WordMac - not
on windows!
>fixed in Samba recently for IBM
does that meen it should work with 3.0.14a or only for IBM's version of
samba?
thx
Jeremy Allison wrote:
On Mon, Jul 18, 2005 at 12:42:43PM +0200, Michael Gasch wrote:
hi f
On Mon, Jul 18, 2005 at 12:42:43PM +0200, Michael Gasch wrote:
> hi folks,
>
> to sum up:
>
> MS confirmed this as a bug and wants to "solve it as soon as possible"
> *twinker*
I think this might be something we fixed in Samba recently for IBM.
MS-Office does some weird things with ACLs.
Jerem
hi folks,
to sum up:
MS confirmed this as a bug and wants to "solve it as soon as possible"
*twinker*
greez
Michael Gasch wrote:
[UPDATE]
i'm no able to specify our problem i little bit more:
the problem only occurs with MS Office Word for Mac OSX (version X and
2004; recent patches)
[UPDATE]
i'm no able to specify our problem i little bit more:
the problem only occurs with MS Office Word for Mac OSX (version X and
2004; recent patches)
1) create a new document (word doc) in a "share" (e.g. points to
/data/share) with MacOSX
2) access a share, which is located *above*
hi list,
we recently saw the following weird behaviour on samba v3.0.13 with
MacOSX panther and tiger as clients
--setup--
[share1]
path = /data
valid users = @admins
force user = administrator
inherit permissions = yes
force create mode = 770
force directory mode = 2770
[share2]
path = /data/fol
