VS: Default ACL dosn't work
I've had the exact same problem. there has been no way to set samba use the rights. only way around was to set inheritance on acl's and permissions. anyway, this does not prevent samba from setting itself the file permissions. it forces them to be owner, domain users, and everyone! silly I say. seems that the acl-code in samba is not really considered as a solution but more as addin, sadly. so can't have real NT connectivity on file-level yet with samba. cheers, Jooel -Alkuperäinen viesti- Lähettäjä: alex [mailto:[EMAIL PROTECTED]] Lähetetty: 30. kesäkuuta 2002 0541 Vastaanottaja: [EMAIL PROTECTED] Aihe: Fw: Default ACL dosn't work Hi, I've a problem with the default ACL, I'm using samba 2.2.3a and the lastest XFS & ACL patch. I setted a default acl at console, it worked at local site, I created a new file, and it inherited the default acl. But when I created a file from windows 2000, the file didn't use default acl. What's the problem? Thanks! Alex
Proposed patch for DNS and name resolution related problems in appliance branch
I've put together some patches to solve some issues related to DNS and name resolution issues within Samba. They will probably go in to the appliance branch, but I am keen for them to also be applied to HEAD. The problem is that Samba is reliant on a working DNS server and misconfigurations of DNS servers can affect the stability and usability of Samba services. smbd and winbindd both try and contact a DNS server to resolve names, especially if the name is not in WINS and the default name resolve order is used. Broken DNS servers can cause the client resolver to run through the full set of timeout/retries which can take up to two minutes to return failure. Samba then compounds this problem by not remembering that the last lookup failed and keeps on trying. I have coded up two solutions to this problem. They are based on the idea that a Samba server should be relatively independent of services it cannot control. If there is a DNS server problem, Samba should behave gracefully and return an error to any Samba clients within a reasonable period of time. I know Jeremy initially wasn't keen on the resolve/retry stuff going in to HEAD but maybe in the context of optimising name resolution he will change his mind. (-: Tim. 1. Shorten the timeout and retry values used by the DNS resolver library Many client resolver libraries contain a global struct in which live retry and timeout fields that can be changed by application programs. In Linux this structure can be stored in resolv.h I propose two new parameters (sorry) : dns resolve retrans The retransmission time interval dns resolve retry Number of retries The retransmission time interval is given in seconds and is doubled between each retry. The default values for these under Linux are five seconds between retries and four retries. If these default values are changed to three retries, 40 seconds is taken off the time taken to return a name lookup failure. 2. Cache negative DNS lookup responses For failed DNS queries we store this failed result in a tdb with a timestamp. All subsequent lookups for that name within a certain time period return false until the negative lookup entry times out. Windows has an local internal name cache for positive lookups which can be queried or modified using the nbtstat command. Since we now have a negative caching system in place we can also do positive caching. This has more of an effect on systems where winbindd and multiple smbds are running at once. The default cache timeout under win2k is 10 minutes but this can be changed using the registry.
Re: UTF8 and character set - anyone???
on 30-06-2002 02:38, The DJ at [EMAIL PROTECTED] wrote: > I was writing some code for a config tool and was wondering the following. > > What happens when you set "coding system = utf8"? > Do you still need to set the character set in that case? > Or is it unnecessary in that case. > And can you set "coding system=utf8" with any other client codepages then > 932? I believe Ukranian does so??? > > The documention is really not complete I think when it comes to: > Character set > Client code page > Coding system > > I have the feeling some stuff is missing there. I see nothing about the > Ukrainian stuff added in 2.2.4 and as a matter of fact I don't see UTF8 > being mentioned anywhere. > > I'll be glad when 3.0 gets out and we don't have to bother with that stuff > anymore. > > DJ I see why there is no documentation on it, no one seems to know the answer DJ --- Universiteit Twente --- Derk-Jan 'The DJ' Hartman ICQnr: 10111559 Mail: mailto:[EMAIL PROTECTED] WWW: http://home.student.utwente.nl/d.hartman/ Goto: http://xamba.sourceforge.net
