Re: [Samba] Printer drivers installation: files are not deleted
Le 21.03.2011 16:55, Thomas Stegbauer a écrit : hi laurent, i found the error. with all the tests there was set: use client driver = yes :( now i can upload drivers and register drivers by apw and cupsaddsmb best regards thank you very for your assistance Heh, you're welcome, but I didn't do much, I didn't think about that at all. So thanks for the feedback, that piece of info can be useful in the future! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] cant use Samba window sprinter drivers on Windows XP32
hi everybody, sorry, currently there seems to ab problem, with my alias with sending eMails. i hope i fixed this now. after some trouble i was now able to upload and set printerdrivers via cupsaddsmb and windows apw. but there are two errors. - i cant use the driver on a windows xp 32, if does not get installed as root previously. - i have a Oki Execution series 7411 and used the PS Driver. when printing to that printer i get in smb.log Unable to print file to es7411 - client-error-not-authorized in cups error.log i get [21/Mar/2011:10:43:19 +0100] Returning IPP client-error-not-authorized for Print-Job (ipp://localhost/printers/es7411) from localhost but i can print (if connected as root) to other printers on the same machine? where could be the error? best regards thomas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Debugging a groups permission problem
Hello samba list, [Apologies if you've seen this message before. I'm not sure if the original got eaten by a filter somewhere along the line.] I've run into a rather strange problem at one of our deployments, and after trying a few ideas myself are turning to you to see if you have any suggestions for my next step. The problem: We're currently running samba 3.5.6 as a file server joined to an active directory. We set up acls that say group foo has r/w access to a directory. A user userA attempts to access that folder and fails even though the active directory server shows he is in that group. I've gone through the samba system checking the output of wbinfo and the getent, groups and id command; they all show that userA is in the supplementary foo group. I also turned up the logging and verified that the results of the supplementary groups in the log show the GID of the foo group when userA connects. Can you suggest to me what else I should be looking at? We've re-run this test by stripping out all acls (nt and posix) and just using permissions. Unless this particular user is the owner or the primary group the user can not access this directory. It feels as if the supplementary group is being ignored for this case, but I don't know why and I have run out of ideas. Searching google does not seem to turn up anything relevant at this point, either. I would greatly appreciate any help investigating what is going on with this system. Thank you all for your assistance. --John M. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Problem loggin in
Hi, I just installed a samba server versión 3.5.6, in a Linux debían 2.6.26-2-amd64, the clients have Windows 7. I have probed with some users and they could log in, but I have many users that can´t log in. When they type their password the computer tell the next message: Intervalo fuera de rango (out of range interval) Do you have any idea? Thanks in advance It is the smb.conf file: [global] workgroup = ALUMNO server string = %h server (Samba %v) passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . log file = /var/log/samba/log.%m printcap name = cups logon script = startup.bat logon path = logon home = domain logons = Yes os level = 65 preferred master = Yes domain master = Yes panic action = /usr/share/samba/panic-action %d #invalid users = root admin users = root,juan, kino, jestrada printing = cups print command = lpq command = %p lprm command = client ntlmv2 auth = yes [homes] writable = yes browsable = no create mode = 0700 [netlogon] path = /var/lib/samba/netlogon read only = yes [printers] comment = All Printers printable = yes path = /var/spool/samba browseable = yes guest ok = yes public = yes read only = no writable = yes create mode = 0700 [comunprepa] path = /home/comunprepa writeable = yes [comunsec] path = /home/comunsec writeable = yes create mode = 750 [typingmaster] path = /home/typingmaster writeable = yes [wallpaper] path = /home/wallpaper writeable = no [wallpaperprim] path = /home/wallpaperprim writeable = no -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Sporadic Logon Issues from Windows 2003
I have a Samba server (3.0.37) acting as a domain controller for several computers running Linux, Windows XP, Windows 7, and just recently a Windows 2003 server that replaced a Windows NT server. A couple times a day, the Windows 2003 server generates an error like the one below for everyone that attempts to connect to it. Throughout the rest of the day, there is no issue at all, but several times it will just refuse connections. -- Event Type: Failure Audit Event Source: Security Event Category: Logon/Logoff Event ID: 537 Date: 3/22/2011 Time: 2:01:54 PM User: NT AUTHORITY\SYSTEM Computer: FLEX1 Description: Logon Failure: Reason: An error occurred during logon User Name: John.Smith Domain: FLEXSERVICES Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: CWS133 Status code:0xC05E Substatus code: 0x0 Caller User Name: - Caller Domain: - Caller Logon ID:- Caller Process ID: - Transited Services: - Source Network Address: 192.168.1.133 Source Port:2621 For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. -- I have checked my Samba logs for the same time period and I don't see any kind of error entries and googling the status code and event ID together hasn't produced anything useful so far. Can anyone give me an idea of how I would go about debugging this situation? -- View this message in context: http://samba.2283325.n4.nabble.com/Sporadic-Logon-Issues-from-Windows-2003-tp3397295p3397295.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Debugging a groups permission problem
On Tue, Mar 22, 2011 at 08:27:05AM -0400, John Mulligan wrote: Hello samba list, [Apologies if you've seen this message before. I'm not sure if the original got eaten by a filter somewhere along the line.] I've run into a rather strange problem at one of our deployments, and after trying a few ideas myself are turning to you to see if you have any suggestions for my next step. The problem: We're currently running samba 3.5.6 as a file server joined to an active directory. We set up acls that say group foo has r/w access to a directory. A user userA attempts to access that folder and fails even though the active directory server shows he is in that group. I've gone through the samba system checking the output of wbinfo and the getent, groups and id command; they all show that userA is in the supplementary foo group. I also turned up the logging and verified that the results of the supplementary groups in the log show the GID of the foo group when userA connects. Can you suggest to me what else I should be looking at? We've re-run this test by stripping out all acls (nt and posix) and just using permissions. Unless this particular user is the owner or the primary group the user can not access this directory. It feels as if the supplementary group is being ignored for this case, but I don't know why and I have run out of ideas. Searching google does not seem to turn up anything relevant at this point, either. I would greatly appreciate any help investigating what is going on with this system. Set debug level 10 using smbcontrol for the smbd connected to the specific client - then search the log for ACCESS_DENIED messages. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Logon scripts not executed when NT4 trusted domain users log in a S3-controlled domain
Quoting Christian PERRIER (bubu...@debian.org): - I get a notice that the domain paassword is expired. I can either change it or ignore the warning, but: This was bug #7066. Fixed in 3.5.8. - the DomB user logon script is not executed This seems to be bug #6356 though my client is a Windows XP machine (not Win7). This is really a showstopper for me. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Upgrading system on file server
On 03/17/2011 01:45 PM, Bayardo Rivas - Open Soluciones wrote: Hi, I have an old version of Suse runing a Samba. I will upgrade this box from Suse 9.3 - Suse 11.3. I know that there are a lot of risk but my top fear is about Samba. This is a production server and network users authenticate with this server. We do not have roaming profile, but I know that if I install from scratch I lose my domain, SID number changes and I have to reconfigure all the clients and this is not an option. So, I will try to upgrade the box with the installation disks, but if I get problems and I am forced to install from scratch, what do I have to do to keep my domain working and don't lose the conection between the domain and clients and keep it transparent for clients?/ Any suggestions are welcome. Bayardo Ok, finally on the weekend I upgraded the system without big issues. When the system was upgraded it was serving all services, including Samba and authentication. First of all... everything was backed up... twice, diferent medias. Two situations after upgrade: 1. Every user had to reset password in first login authentication to domain. 2. Once the password was reset, unexpected, the system notified users that password had expired. With the command # pdbedit -P maximum password age I saw that it had the 180 value (seconds), so I had to change this policy with the command: # pdbedit -P maximum password age -C -1 Wich means, never expire the password. I need this policy this way. Well.. good luck to any body who need to work with this. Thank you for your advices. Bayardo. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Mac OS X user having problems connecting to samba running on Ubuntu Server
Hi all, Doing a bit of research on samba and hostname lead me to find the actual cause of the problem. If you don't specify the netbios name = directive in the samba configuration(smb.conf) file, samba uses hostname as the netbios name (ref: http://www.justlinux.com/forum/archive/index.php/t-126124.html read cowanrl's comment) and the maximum length of a netbios name is 16 characters. However, Microsoft limits the netbios name to 15 characters (ref: http://support.microsoft.com/kb/163409). In my case i had not specified the netbios name = directive in smb.conf file and the hostname was more than 16 characters. Adding netbios name = to something less than 15 characters did the trick. My hostname is more than 16 characters. Hope this helps some of you out there. Thanks, Amit More On Mon, 2011-03-21 at 18:16 -0700, Amit More wrote: Hello all, After spending some time looking into the problem, I have found out that changing the hostname of the machine on which samba was running to be 16(or less) characters long did the trick. With internalfileserver(which is 18 characters long) as hostname Mac users were not able to connect to the share via connect to server(apple + k) application but could connect via the command line. Changing the hostname to fileserver(which is 10 characters long) allowed Mac users to connect to the share via connect to server application as well as via the command line. I am not able to figure this out. I will share it with samba users once i find something useful. Thanks, Amit More On Thu, 2011-03-17 at 18:51 -0700, Amit More wrote: Hello all, I have installed samba version 3.3.2 on Ubuntu 9.04 server 32-bit following the documentation https://help.ubuntu.com/9.10/serverguide/C/samba-fileserver.html Windows and Ubuntu users can see and mount the shares with no problem at all. Mac OS 10.6.x users can connect to samba from terminal using smbclient, but they are refused connection when they try to connect via finder (ie using apple + k). The error Mac users get is “wrong username or password”. However, they can connect via finder only when they prefix the username with any domain name. They can pass any arbitrary domain name before the username to connect to the samba share. To be more clear here is an example smb://server.domain.com/File_share username: arbitrary-domain-name\username Also, Mac OS X users having problem connecting to samba running on Ubuntu server are able to mount the shares from Windows Server 2003 via finder. I have set the following parameters in my /etc/samba/smb.conf file workgroup = WORKGROUP server string = %h server (Samba, Ubuntu) dns proxy = no security = user encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s* \spassword:* %n\n *password\supdated\ssuccessfully* . map to guest = bad user usershare allow guests = yes [share] comment = Ubuntu File Server Share path = /srv/samba/share browsable = yes guest ok = no read only = no create mask = 0755 Things that I have tried: 1. Adding public = yes in share 2. Setting encryption = false I am new to samba and have been doing research for a long time to get this working. Is there any workaround for the problem that I am facing. I would appreciate all your help. Thanks in advance, Amit More -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Upgrade from Samba 3.0.33 to 3.5.8 woes
Greetings, I just did a major upgrade to our Samba infrastructure. I previously had a domain controller and share running 3.0.33 (on one box, one samba instance) I set up a new domain controller running 3.5.8, made that the PDC for our domain, and changed the (now former) domain controller running 3.0.33 to just be a member. Additionally, we moved the IP from the old DC to the new DC (and subsequently gave the former DC, now just a member and file share a new IP) Now I am having some strange issues. Windows machines in our London office (which is connected via a tunnel between some Cisco ASA's from HQ to London) can no longer see the domain (which is at HQ) UNLESS we disable the Windows firewall on the workstations OR add exceptions to the firewall for the PDC. Machines at HQ see the domain fine. Now, the PDC has the SAME IP as the old domain. So it's not like the rules would need to be any different anyway. Frankly, I don't quite understand how this worked before - but it did! Did something change between 3.0.x and 3.5.x which would cause this behavior and is there a fix? I am hoping to not have to run through and change all of the firewalls on all of our workstations (especially since we can't do so via netlogon scripts etc as they won't see the domain!) Worth noting, our machines all have an lmhosts file which tells them where to go for the domain, hence why we moved the IP from the old dc to the new dc. Second problem.. users can't access our file share (which was formerly the domain controller, now just a member) when connected via our VPN (a juniper ssl vpn). The VPN drops them into the same network as if they are in the office -- and it works fine if you are in the office. Yet, if you come in via VPN you received no logon servers available errors. Mac users connecting to the file share via SMB have no problem. The following error is logged in smbd.log (redacted my specific names): domain_client_validate: unable to validate password for user $username in domain $mydomain to Domain controller $mypdc. Error was NT_STATUS_UNSUCCESSFUL. Happy to provide any additional info.. I'm baffled! All of this worked before without problems. Thanks, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] strange anomaly/bug with cupsaddsmb and 64bit drivers
This is probably a CUPS bug but maybe not, I'll mention it here just in case. When using cupsaddsmb to install 64bit drivers the drivers must be in the (maybe distro/configure dependent): /usr/share/cups/drivers/x64 to be sure that's x64 with a lower case x. The cupsaddsmb app ignores the drivers if the subdirectory is named with an uppercase X (X64). Now if Samba's printers (/var/lib/samba/printers in my case) directory already contains an X64 (uppercase X) directory cupsaddsmb will work all the way up to the setdriver stage and then fail with: result was WERR_INVALID_PARAM A workaround is to delete the X64 directory (unless it is being used otherwise, then I presume that renaming it with a lower case x will work) and cupsaddsmb will create an x64 directory, and with a lowercase x the setdriver stage completes with no issues. Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Upgrade from Samba 3.0.33 to 3.5.8 woes
The same happend to me. But I didn't have the time to analize the problem. I solve it by changing the name of the server. Same ip, but new name and everything works now. It would be great to know if there is another workaround. Did you keep the sid of the pdc after the change? Did you use ldap? Bye. Greetings, I just did a major upgrade to our Samba infrastructure. I previously had a domain controller and share running 3.0.33 (on one box, one samba instance) I set up a new domain controller running 3.5.8, made that the PDC for our domain, and changed the (now former) domain controller running 3.0.33 to just be a member. Additionally, we moved the IP from the old DC to the new DC (and subsequently gave the former DC, now just a member and file share a new IP) Now I am having some strange issues. Windows machines in our London office (which is connected via a tunnel between some Cisco ASA's from HQ to London) can no longer see the domain (which is at HQ) UNLESS we disable the Windows firewall on the workstations OR add exceptions to the firewall for the PDC. Machines at HQ see the domain fine. Now, the PDC has the SAME IP as the old domain. So it's not like the rules would need to be any different anyway. Frankly, I don't quite understand how this worked before - but it did! Did something change between 3.0.x and 3.5.x which would cause this behavior and is there a fix? I am hoping to not have to run through and change all of the firewalls on all of our workstations (especially since we can't do so via netlogon scripts etc as they won't see the domain!) Worth noting, our machines all have an lmhosts file which tells them where to go for the domain, hence why we moved the IP from the old dc to the new dc. Second problem.. users can't access our file share (which was formerly the domain controller, now just a member) when connected via our VPN (a juniper ssl vpn). The VPN drops them into the same network as if they are in the office -- and it works fine if you are in the office. Yet, if you come in via VPN you received no logon servers available errors. Mac users connecting to the file share via SMB have no problem. The following error is logged in smbd.log (redacted my specific names): domain_client_validate: unable to validate password for user $username in domain $mydomain to Domain controller $mypdc. Error was NT_STATUS_UNSUCCESSFUL. Happy to provide any additional info.. I'm baffled! All of this worked before without problems. Thanks, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Upgrade from Samba 3.0.33 to 3.5.8 woes
The new DC has a new time. We do use LDAP. Which SID are you referring to? The local SID is new on the new DC, but the domain sids are the same. On Tue, Mar 22, 2011 at 10:23 PM, gu...@lorenzutti.com.ar wrote: The same happend to me. But I didn't have the time to analize the problem. I solve it by changing the name of the server. Same ip, but new name and everything works now. It would be great to know if there is another workaround. Did you keep the sid of the pdc after the change? Did you use ldap? Bye. Greetings, I just did a major upgrade to our Samba infrastructure. I previously had a domain controller and share running 3.0.33 (on one box, one samba instance) I set up a new domain controller running 3.5.8, made that the PDC for our domain, and changed the (now former) domain controller running 3.0.33 to just be a member. Additionally, we moved the IP from the old DC to the new DC (and subsequently gave the former DC, now just a member and file share a new IP) Now I am having some strange issues. Windows machines in our London office (which is connected via a tunnel between some Cisco ASA's from HQ to London) can no longer see the domain (which is at HQ) UNLESS we disable the Windows firewall on the workstations OR add exceptions to the firewall for the PDC. Machines at HQ see the domain fine. Now, the PDC has the SAME IP as the old domain. So it's not like the rules would need to be any different anyway. Frankly, I don't quite understand how this worked before - but it did! Did something change between 3.0.x and 3.5.x which would cause this behavior and is there a fix? I am hoping to not have to run through and change all of the firewalls on all of our workstations (especially since we can't do so via netlogon scripts etc as they won't see the domain!) Worth noting, our machines all have an lmhosts file which tells them where to go for the domain, hence why we moved the IP from the old dc to the new dc. Second problem.. users can't access our file share (which was formerly the domain controller, now just a member) when connected via our VPN (a juniper ssl vpn). The VPN drops them into the same network as if they are in the office -- and it works fine if you are in the office. Yet, if you come in via VPN you received no logon servers available errors. Mac users connecting to the file share via SMB have no problem. The following error is logged in smbd.log (redacted my specific names): domain_client_validate: unable to validate password for user $username in domain $mydomain to Domain controller $mypdc. Error was NT_STATUS_UNSUCCESSFUL. Happy to provide any additional info.. I'm baffled! All of this worked before without problems. Thanks, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Upgrade from Samba 3.0.33 to 3.5.8 woes
Did you update the schema on the ldap? Maybe you should. Im right know doing it. I don't know how many changes are in the schema between 3.0.33 and 3.5.x. Im migrating from 3.0.24 to 3.2.X and if I don't upgrade the schema the password must change time dosen't work. What do you mean about the dc has a new time? I was referring to the domain sid. The new DC has a new time. We do use LDAP. Which SID are you referring to? The local SID is new on the new DC, but the domain sids are the same. On Tue, Mar 22, 2011 at 10:23 PM, gu...@lorenzutti.com.ar wrote: The same happend to me. But I didn't have the time to analize the problem. I solve it by changing the name of the server. Same ip, but new name and everything works now. It would be great to know if there is another workaround. Did you keep the sid of the pdc after the change? Did you use ldap? Bye. Greetings, I just did a major upgrade to our Samba infrastructure. I previously had a domain controller and share running 3.0.33 (on one box, one samba instance) I set up a new domain controller running 3.5.8, made that the PDC for our domain, and changed the (now former) domain controller running 3.0.33 to just be a member. Additionally, we moved the IP from the old DC to the new DC (and subsequently gave the former DC, now just a member and file share a new IP) Now I am having some strange issues. Windows machines in our London office (which is connected via a tunnel between some Cisco ASA's from HQ to London) can no longer see the domain (which is at HQ) UNLESS we disable the Windows firewall on the workstations OR add exceptions to the firewall for the PDC. Machines at HQ see the domain fine. Now, the PDC has the SAME IP as the old domain. So it's not like the rules would need to be any different anyway. Frankly, I don't quite understand how this worked before - but it did! Did something change between 3.0.x and 3.5.x which would cause this behavior and is there a fix? I am hoping to not have to run through and change all of the firewalls on all of our workstations (especially since we can't do so via netlogon scripts etc as they won't see the domain!) Worth noting, our machines all have an lmhosts file which tells them where to go for the domain, hence why we moved the IP from the old dc to the new dc. Second problem.. users can't access our file share (which was formerly the domain controller, now just a member) when connected via our VPN (a juniper ssl vpn). The VPN drops them into the same network as if they are in the office -- and it works fine if you are in the office. Yet, if you come in via VPN you received no logon servers available errors. Mac users connecting to the file share via SMB have no problem. The following error is logged in smbd.log (redacted my specific names): domain_client_validate: unable to validate password for user $username in domain $mydomain to Domain controller $mypdc. Error was NT_STATUS_UNSUCCESSFUL. Happy to provide any additional info.. I'm baffled! All of this worked before without problems. Thanks, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] ACL not working
Using Samba+winbind 3.3.8 as a fileserver on a Win2008 domain. getent and wbinfo is reporting correct informations about users. However, my groups directories are allowing people who shouldn't .. From the shell everything is working as expected, but not from samba.. What did I miss !? Exported share: /export/users drwxr-x---+ 7 root root 4096 Mar 18 14:57 group# (teams directories) \ tech \--- prod - Working from shell # su prod-user $ ls tech/ ls: tech/: Permission denied - Not working from smbclient # smbclient -U prod-user //fileserver/share Domain=[FOO] OS=[Unix] Server=[Samba 3.3.8-0.52.el5_5.2] smb: \ cd group/tech/ smb: \group\tech\ -- Group -- # getent group | grep prod-user prod:*:10004:prod-user,(...) -- Acls -- # file: group # owner: root # group: root user::rwx group::r-x group:domain\040users:r-x mask::r-x other::--- # file: group/tech # owner: root # group: root user::--- group::--- group:tech:rwx mask::rwx other::--- default:user::--- default:group::--- default:group:tech:rwx default:mask::rwx default:other::--- -- Build options -- # smbd -b | grep -i acl HAVE_SYS_ACL_H HAVE_ACL_LIBACL_H HAVE_POSIX_ACLS vfs_acl_tdb_init vfs_acl_xattr_init pdb_ldap pdb_smbpasswd pdb_tdbsam rpc_lsarpc rpc_winreg rpc_initshutdown rpc_dssetup rpc_wkssvc rpc_svcctl2 rpc_ntsvcs2 rpc_netlogon rpc_netdfs rpc_srvsvc rpc_spoolss rpc_eventlog2 rpc_samr idmap_ldap idmap_tdb idmap_passdb idmap_nss nss_info_template auth_sam auth_unix auth_winbind auth_server auth_domain auth_builtin vfs_default vfs_posixacl -- smb.conf -- [global] workgroup = FOO realm = FOO.BAR local master = no domain master = no preferred master = no server string = SOVO File Server security = ads encrypt passwords = yes password server = dc1.foo.bar, dc2.foo.bar log level = 3 log file = /var/log/samba/%m max log size = 50 load printers = no printcap name = /dev/null disable spoolss = yes show add printer wizard = no client ntlmv2 auth = yes winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes winbind nested groups = Yes winbind refresh tickets = yes winbind reconnect delay = 15 winbind separator = + winbind cache time = 120 winbind nss info = rfc2307 winbind offline logon = true passdb backend = tdbsam idmap negative cache time = 120 idmap cache time = 900 idmap config FOO : backend = ad idmap config FOO : readonly = yes idmap config FOO : schema_mode = rfc2307 idmap config FOO : range = 1-40 idmap uid = 1-2 idmap gid = 1-2 nt acl support = no acl check permissions = true acl compatibility = auto acl group control = no acl map full control = false [share] path = /export/users writable = yes browseable = yes hide unreadable = yes hide dot files=yes hide files=/lost+found/ valid users = @tech @man @prod -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Windows 7 and logon scripts
I had the same problem. I fixed it with the following in smb.conf: ... preexec = /usr/local/bin/netlogon %U logon drive = X: logon script = %U.bat ; logon path = \\%L\profiles\%U ; logon home = \\%N\%U ... [netlogon] comment = The domain logon service path = /home/netlogon ; read only = yes public = no writeable = no browsable = no Regards, Dario. -- View this message in context: http://samba.2283325.n4.nabble.com/Samba-Windows-7-and-logon-scripts-tp2532596p3396892.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
autobuild: intermittent test failure detected
The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2011-03-22-1222/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2011-03-22-1222/samba3.stderr http://git.samba.org/autobuild.flakey/2011-03-22-1222/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-03-22-1222/samba4.stderr http://git.samba.org/autobuild.flakey/2011-03-22-1222/samba4.stdout The top commit at the time of the failure was: commit c8297073dbaf19237891fd97d9e62dc00ad4e1f0 Author: Andrew Tridgell tri...@samba.org Date: Tue Mar 22 14:05:23 2011 +1100 s3-fault: removed the cont_fn from fault_setup() cont_fn() was supposed to be a way to continue after a seg fault. It could never be called however, as smb_panic() from fault_report() could never return, as dump_core() never returns at the end of smb_panic() Autobuild-User: Andrew Tridgell tri...@samba.org Autobuild-Date: Tue Mar 22 05:07:58 CET 2011 on sn-devel-104
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated via bc3fb24 s3:docs: fix xml of printnotifybackchannel parameter (missing closing tag) from c829707 s3-fault: removed the cont_fn from fault_setup() http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master - Log - commit bc3fb2405ca1454a7b8da226781f9df13e1070cf Author: Michael Adam ob...@samba.org Date: Tue Mar 22 13:08:10 2011 +0100 s3:docs: fix xml of printnotifybackchannel parameter (missing closing tag) Autobuild-User: Michael Adam ob...@samba.org Autobuild-Date: Tue Mar 22 13:57:25 CET 2011 on sn-devel-104 --- Summary of changes: .../smbdotconf/printing/printnotifybackchannel.xml |1 + 1 files changed, 1 insertions(+), 0 deletions(-) Changeset truncated at 500 lines: diff --git a/docs-xml/smbdotconf/printing/printnotifybackchannel.xml b/docs-xml/smbdotconf/printing/printnotifybackchannel.xml index f895f9c..4046322 100644 --- a/docs-xml/smbdotconf/printing/printnotifybackchannel.xml +++ b/docs-xml/smbdotconf/printing/printnotifybackchannel.xml @@ -13,6 +13,7 @@ and treat corresponding requests as if the connection back to the client failed. The default setting of constantyes/constant causes smbd to attempt this connection. +/para /description value type=defaultyes/value /samba:parameter -- Samba Shared Repository
autobuild: intermittent test failure detected
The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2011-03-22-1421/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2011-03-22-1421/samba3.stderr http://git.samba.org/autobuild.flakey/2011-03-22-1421/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-03-22-1421/samba4.stderr http://git.samba.org/autobuild.flakey/2011-03-22-1421/samba4.stdout The top commit at the time of the failure was: commit bc3fb2405ca1454a7b8da226781f9df13e1070cf Author: Michael Adam ob...@samba.org Date: Tue Mar 22 13:08:10 2011 +0100 s3:docs: fix xml of printnotifybackchannel parameter (missing closing tag) Autobuild-User: Michael Adam ob...@samba.org Autobuild-Date: Tue Mar 22 13:57:25 CET 2011 on sn-devel-104
[SCM] Samba Shared Repository - branch v3-6-test updated
The branch, v3-6-test has been updated via f09992e s3:docs: fix xml of printnotifybackchannel parameter (missing closing tag) from c7d1017 libcli/security: make sure that we don't grant SEC_STD_DELETE to the owner by default http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-6-test - Log - commit f09992e48f064e196dfade8c33903ad273178cb9 Author: Michael Adam ob...@samba.org Date: Tue Mar 22 13:08:10 2011 +0100 s3:docs: fix xml of printnotifybackchannel parameter (missing closing tag) Autobuild-User: Michael Adam ob...@samba.org Autobuild-Date: Tue Mar 22 13:57:25 CET 2011 on sn-devel-104 --- Summary of changes: .../smbdotconf/printing/printnotifybackchannel.xml |1 + 1 files changed, 1 insertions(+), 0 deletions(-) Changeset truncated at 500 lines: diff --git a/docs-xml/smbdotconf/printing/printnotifybackchannel.xml b/docs-xml/smbdotconf/printing/printnotifybackchannel.xml index f895f9c..4046322 100644 --- a/docs-xml/smbdotconf/printing/printnotifybackchannel.xml +++ b/docs-xml/smbdotconf/printing/printnotifybackchannel.xml @@ -13,6 +13,7 @@ and treat corresponding requests as if the connection back to the client failed. The default setting of constantyes/constant causes smbd to attempt this connection. +/para /description value type=defaultyes/value /samba:parameter -- Samba Shared Repository
Re: autobuild: intermittent test failure detected
Hi, commit 4928d66fc2f469b75090c34f8d233026485e4a1e Author: Stefan Metzmacher me...@samba.org Date: Mon Mar 21 11:21:57 2011 +0100 libcli/security: make sure that we don't grant SEC_STD_DELETE to the owner by default In the file server SEC_STD_DELETE is granted on the file/directory or by FILE_DELETE_CHILD on the parent directory. metze I've pushed a fix for this to autobuild... metze signature.asc Description: OpenPGP digital signature
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via b8d0994 s4:ntvfs/posix: name-dos.attrib isn't initialized in
pvfs_access_check_create()
from bc3fb24 s3:docs: fix xml of printnotifybackchannel parameter
(missing closing tag)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit b8d0994627ef237fdc92bebd9c9a26f9d62764bc
Author: Stefan Metzmacher me...@samba.org
Date: Tue Mar 22 16:34:36 2011 +0100
s4:ntvfs/posix: name-dos.attrib isn't initialized in
pvfs_access_check_create()
That's why we have the 'container' parameter to indicate
the caller wants to create a directory.
metze
Autobuild-User: Stefan Metzmacher me...@samba.org
Autobuild-Date: Tue Mar 22 17:39:11 CET 2011 on sn-devel-104
---
Summary of changes:
source4/ntvfs/posix/pvfs_acl.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source4/ntvfs/posix/pvfs_acl.c b/source4/ntvfs/posix/pvfs_acl.c
index addd680..67b544d 100644
--- a/source4/ntvfs/posix/pvfs_acl.c
+++ b/source4/ntvfs/posix/pvfs_acl.c
@@ -698,7 +698,7 @@ NTSTATUS pvfs_access_check_create(struct pvfs_state *pvfs,
status = pvfs_resolve_parent(pvfs, req, name, parent);
NT_STATUS_NOT_OK_RETURN(status);
- if (name-dos.attrib FILE_ATTRIBUTE_DIRECTORY) {
+ if (container) {
parent_mask = SEC_DIR_ADD_SUBDIR;
} else {
parent_mask = SEC_DIR_ADD_FILE;
--
Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-6-test updated
The branch, v3-6-test has been updated
via edb5c6e s4:ntvfs/posix: name-dos.attrib isn't initialized in
pvfs_access_check_create()
from f09992e s3:docs: fix xml of printnotifybackchannel parameter
(missing closing tag)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-6-test
- Log -
commit edb5c6e4cee16bfa47310f6200adde94882d6f18
Author: Stefan Metzmacher me...@samba.org
Date: Tue Mar 22 16:34:36 2011 +0100
s4:ntvfs/posix: name-dos.attrib isn't initialized in
pvfs_access_check_create()
That's why we have the 'container' parameter to indicate
the caller wants to create a directory.
metze
Autobuild-User: Stefan Metzmacher me...@samba.org
Autobuild-Date: Tue Mar 22 17:39:11 CET 2011 on sn-devel-104
(cherry picked from commit b8d0994627ef237fdc92bebd9c9a26f9d62764bc)
---
Summary of changes:
source4/ntvfs/posix/pvfs_acl.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source4/ntvfs/posix/pvfs_acl.c b/source4/ntvfs/posix/pvfs_acl.c
index addd680..67b544d 100644
--- a/source4/ntvfs/posix/pvfs_acl.c
+++ b/source4/ntvfs/posix/pvfs_acl.c
@@ -698,7 +698,7 @@ NTSTATUS pvfs_access_check_create(struct pvfs_state *pvfs,
status = pvfs_resolve_parent(pvfs, req, name, parent);
NT_STATUS_NOT_OK_RETURN(status);
- if (name-dos.attrib FILE_ATTRIBUTE_DIRECTORY) {
+ if (container) {
parent_mask = SEC_DIR_ADD_SUBDIR;
} else {
parent_mask = SEC_DIR_ADD_FILE;
--
Samba Shared Repository
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via 3940777 s4:python bindings - handle NULL returns from
loadparm_init_global
via 5d09aca s4:param/loadparm.c - check for OOM
via bd25bc1 s4:auth/system_session.c - check for OOM
from b8d0994 s4:ntvfs/posix: name-dos.attrib isn't initialized in
pvfs_access_check_create()
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit 3940777a14a93dbf88fcc9e43452fc2f84a7b6fc
Author: Matthias Dieter Wallnöfer m...@samba.org
Date: Mon Mar 21 10:32:24 2011 +0100
s4:python bindings - handle NULL returns from loadparm_init_global
Reviewed-by: Jelmer
Autobuild-User: Matthias Dieter Wallnöfer m...@samba.org
Autobuild-Date: Tue Mar 22 19:52:57 CET 2011 on sn-devel-104
commit 5d09acab7e5e671f244d69f59d1714a16bdb93fb
Author: Matthias Dieter Wallnöfer m...@samba.org
Date: Mon Mar 21 10:25:52 2011 +0100
s4:param/loadparm.c - check for OOM
Return NULL if the loadparm context hasn't been allocated
Reviewed-by: Jelmer
commit bd25bc133a2a6f2b4d755b6d3ea83c956a60e3af
Author: Matthias Dieter Wallnöfer m...@samba.org
Date: Mon Mar 21 10:25:09 2011 +0100
s4:auth/system_session.c - check for OOM
Reviewed-by: Jelmer
---
Summary of changes:
source4/auth/gensec/pygensec.c | 10 ++
source4/auth/system_session.c |2 ++
source4/param/loadparm.c |3 +++
source4/param/pyparam.c|4
source4/param/pyparam_util.c |3 +++
5 files changed, 22 insertions(+), 0 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source4/auth/gensec/pygensec.c b/source4/auth/gensec/pygensec.c
index cd05bd7..5fe3703 100644
--- a/source4/auth/gensec/pygensec.c
+++ b/source4/auth/gensec/pygensec.c
@@ -113,6 +113,11 @@ static PyObject *py_gensec_start_client(PyTypeObject
*type, PyObject *args, PyOb
}
settings-lp_ctx = loadparm_init_global(true);
+ if (settings-lp_ctx == NULL) {
+ PyErr_NoMemory();
+ PyObject_DEL(self);
+ return NULL;
+ }
}
ev = tevent_context_init(self-talloc_ctx);
@@ -181,6 +186,11 @@ static PyObject *py_gensec_start_server(PyTypeObject
*type, PyObject *args, PyOb
}
settings-lp_ctx = loadparm_init_global(true);
+ if (settings-lp_ctx == NULL) {
+ PyErr_NoMemory();
+ PyObject_DEL(self);
+ return NULL;
+ }
}
ev = tevent_context_init(self-talloc_ctx);
diff --git a/source4/auth/system_session.c b/source4/auth/system_session.c
index ad0dab6..54b8f51 100644
--- a/source4/auth/system_session.c
+++ b/source4/auth/system_session.c
@@ -268,6 +268,8 @@ static NTSTATUS auth_domain_admin_session_info(TALLOC_CTX
*parent_ctx,
struct auth_user_info_dc *user_info_dc = NULL;
TALLOC_CTX *mem_ctx = talloc_new(parent_ctx);
+ NT_STATUS_HAVE_NO_MEMORY(mem_ctx);
+
nt_status = auth_domain_admin_user_info_dc(mem_ctx,
lpcfg_netbios_name(lp_ctx),
lpcfg_workgroup(lp_ctx),
domain_sid,
user_info_dc);
diff --git a/source4/param/loadparm.c b/source4/param/loadparm.c
index 1864436..49d2e1c 100644
--- a/source4/param/loadparm.c
+++ b/source4/param/loadparm.c
@@ -2533,6 +2533,9 @@ struct loadparm_context *loadparm_init_global(bool
load_default)
if (global_loadparm_context == NULL) {
global_loadparm_context = loadparm_init(NULL);
}
+ if (global_loadparm_context == NULL) {
+ return NULL;
+ }
if (load_default !global_loadparm_context-loaded) {
lpcfg_load_default(global_loadparm_context);
}
diff --git a/source4/param/pyparam.c b/source4/param/pyparam.c
index a248215..3ba8146 100644
--- a/source4/param/pyparam.c
+++ b/source4/param/pyparam.c
@@ -335,6 +335,10 @@ static PyObject *py_lp_ctx_new(PyTypeObject *type,
PyObject *args, PyObject *kwa
return NULL;
}
ret-ptr = loadparm_init_global(false);
+ if (ret-ptr == NULL) {
+ PyErr_NoMemory();
+ return NULL;
+ }
return (PyObject *)ret;
}
diff --git a/source4/param/pyparam_util.c b/source4/param/pyparam_util.c
index 528c007..cbf2095 100644
--- a/source4/param/pyparam_util.c
+++ b/source4/param/pyparam_util.c
@@ -35,6 +35,9 @@ _PUBLIC_ struct loadparm_context
*lpcfg_from_py_object(TALLOC_CTX *mem_ctx, PyOb
if (PyString_Check(py_obj)) {
lp_ctx = loadparm_init_global(false);
+ if (lp_ctx == NULL) {
+ return NULL;
+ }
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated via cfae1e7 s3:WHATSNEW: document changes of the id mapping system via 2bfe9d1 s3:selftest: fix Samba3.pm deprecated idmap config via f50a25c s3:idmap: make sure that the id mapping system is initialized for first access via 0109604 s3:loadparm: set the default idmap config * : backend in initialize_globals(). via ac8836e s3:loadparm: deprecate idmap uid/gid/backend and have them set idmap config * : range/backend via 278cfec s3:WHATSNEW: remove mention of idmap read only as new parameter via cafb25a s3:docs: remove documentation of idmap read only which was removed. via 474f6a0 s3:loadparm: remove unused parameter idmap read only. via ae5d35b s3:idmap: remove (now) unneeded function parse_idmap_module() via efc1d38 s3:idmap: simply call idmap_init_named_domain for * in idmap_init_default_domain via ca8c493 s3:idmap: remove passdb argument from idmap_init_domain() via 82853a6 s3:idmap: remove the params argument from the init function via 9885420 s3:idmap: remove special treatment of domain * from idmap_ldap_init. via 7511f08 s3:idmap: remove use of params from idmap_ldap_init - it is not used any more via 0a3627d s3:idmap: remove the special treatment of the default domain * from idmap_init_domain from 3940777 s4:python bindings - handle NULL returns from loadparm_init_global http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master - Log - commit cfae1e795f56add279d5ea24e3410d376ae908d2 Author: Michael Adam ob...@samba.org Date: Tue Feb 1 11:58:14 2011 +0100 s3:WHATSNEW: document changes of the id mapping system Autobuild-User: Michael Adam ob...@samba.org Autobuild-Date: Tue Mar 22 23:57:29 CET 2011 on sn-devel-104 commit 2bfe9d177273d9abf6dda237ebf2d8bd9e143ec3 Author: Björn Baumbach b...@sernet.de Date: Thu Mar 10 15:58:05 2011 +0100 s3:selftest: fix Samba3.pm deprecated idmap config Replace deprecated idmap uid and gid option with new idmap config * : range commit f50a25cc8d4a154aa96d9259488909d60fc40c6c Author: Michael Adam ob...@samba.org Date: Thu Mar 10 23:41:17 2011 +0100 s3:idmap: make sure that the id mapping system is initialized for first access commit 0109604f53dee04e2c0feed0cafa5c94f39ba6a4 Author: Michael Adam ob...@samba.org Date: Thu Mar 10 23:40:19 2011 +0100 s3:loadparm: set the default idmap config * : backend in initialize_globals(). commit ac8836e77f0f7a15bf52f1dc8860729d2693888f Author: Michael Adam ob...@samba.org Date: Tue Mar 8 07:15:36 2011 +0100 s3:loadparm: deprecate idmap uid/gid/backend and have them set idmap config * : range/backend commit 278cfec53a16e49973e1d04b001bb7f38e483807 Author: Michael Adam ob...@samba.org Date: Tue Mar 22 17:09:47 2011 +0100 s3:WHATSNEW: remove mention of idmap read only as new parameter commit cafb25ab371edcb9bc47da3e95b9fac0d3d57a59 Author: Michael Adam ob...@samba.org Date: Tue Mar 22 17:08:42 2011 +0100 s3:docs: remove documentation of idmap read only which was removed. commit 474f6a0f752bc3fb96cbd6cdc766b916b244c5d5 Author: Michael Adam ob...@samba.org Date: Fri Mar 4 14:25:58 2011 +0100 s3:loadparm: remove unused parameter idmap read only. This has not been released yet and is now useless since we use the idmap config * : read only = ... syntax. commit ae5d35b09e9bcf39523a5300985720786860e65a Author: Michael Adam ob...@samba.org Date: Thu Mar 3 17:50:28 2011 +0100 s3:idmap: remove (now) unneeded function parse_idmap_module() commit efc1d38b32cc35f51e0a6bf05e1e45b45dbc9abf Author: Michael Adam ob...@samba.org Date: Thu Mar 3 17:48:43 2011 +0100 s3:idmap: simply call idmap_init_named_domain for * in idmap_init_default_domain The default domain * is now treated exactly the same as other explicitly configured domains. commit ca8c493bfdc86f222a65d9ce8fc761de89fca9b7 Author: Michael Adam ob...@samba.org Date: Thu Mar 3 17:40:36 2011 +0100 s3:idmap: remove passdb argument from idmap_init_domain() commit 82853a613ba854661aa3d36ae5f0f0f11c13ce26 Author: Michael Adam ob...@samba.org Date: Wed Mar 2 23:00:58 2011 +0100 s3:idmap: remove the params argument from the init function commit 98854207feb4af953226db6bbf8169e2d44cfa5b Author: Michael Adam ob...@samba.org Date: Wed Mar 2 17:08:01 2011 +0100 s3:idmap: remove special treatment of domain * from idmap_ldap_init. The default config via domain * is now treated just as the explicit domain configs. commit 7511f080b459a5477362eeb6a326ed73e38a1b11 Author: Michael Adam ob...@samba.org Date: Wed Mar 2 17:04:59 2011 +0100 s3:idmap: remove use of params from idmap_ldap_init - it is not used any more commit 0a3627d24987efcd99ec5f7808e0d1f15e51c774 Author: Michael Adam ob...@samba.org Date:
[SCM] Samba Shared Repository - branch v3-6-test updated
The branch, v3-6-test has been updated via 012e371 s3:WHATSNEW: document changes of the id mapping system via 4e0e6db s3:selftest: fix Samba3.pm deprecated idmap config via 8ddb61d s3:idmap: make sure that the id mapping system is initialized for first access via ee7648d s3:loadparm: set the default idmap config * : backend in initialize_globals(). via ca9ee95 s3:loadparm: deprecate idmap uid/gid/backend and have them set idmap config * : range/backend via 6ffd937 s3:WHATSNEW: remove mention of idmap read only as new parameter via 9345f32 s3:docs: remove documentation of idmap read only which was removed. via 7e2fda2 s3:loadparm: remove unused parameter idmap read only. via c457509 s3:idmap: remove (now) unneeded function parse_idmap_module() via ce6ac15 s3:idmap: simply call idmap_init_named_domain for * in idmap_init_default_domain via 7742e87 s3:idmap: remove passdb argument from idmap_init_domain() via a347781 s3:idmap: remove the params argument from the init function via 4e3f904 s3:idmap: remove use of params from idmap_ldap_init - it is not used any more via f042317 s3:idmap: remove special treatment of domain * from idmap_ldap_init. via 0b1f2f4 s3:idmap: remove the special treatment of the default domain * from idmap_init_domain from edb5c6e s4:ntvfs/posix: name-dos.attrib isn't initialized in pvfs_access_check_create() http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-6-test - Log - commit 012e3712260d76fd1e86c4f1c136dc3ad8876622 Author: Michael Adam ob...@samba.org Date: Tue Feb 1 11:58:14 2011 +0100 s3:WHATSNEW: document changes of the id mapping system Autobuild-User: Michael Adam ob...@samba.org Autobuild-Date: Tue Mar 22 23:57:29 CET 2011 on sn-devel-104 commit 4e0e6db9f750a2b5f33080a0d3b68eb59a5b6113 Author: Björn Baumbach b...@sernet.de Date: Thu Mar 10 15:58:05 2011 +0100 s3:selftest: fix Samba3.pm deprecated idmap config Replace deprecated idmap uid and gid option with new idmap config * : range commit 8ddb61d1712134dd2d9bfa7baee7497d2cdbf86b Author: Michael Adam ob...@samba.org Date: Thu Mar 10 23:41:17 2011 +0100 s3:idmap: make sure that the id mapping system is initialized for first access commit ee7648db47adf6d44c84d03d23120359c2af6eb3 Author: Michael Adam ob...@samba.org Date: Thu Mar 10 23:40:19 2011 +0100 s3:loadparm: set the default idmap config * : backend in initialize_globals(). commit ca9ee9501f48c4f5497baeefeb9de1980250f2b3 Author: Michael Adam ob...@samba.org Date: Tue Mar 8 07:15:36 2011 +0100 s3:loadparm: deprecate idmap uid/gid/backend and have them set idmap config * : range/backend commit 6ffd937cd993c3c4d74e4733b3f6ffec4c16da27 Author: Michael Adam ob...@samba.org Date: Tue Mar 22 17:09:47 2011 +0100 s3:WHATSNEW: remove mention of idmap read only as new parameter commit 9345f32aa62136cb7cb732609acfe3c3bf9e9dd1 Author: Michael Adam ob...@samba.org Date: Tue Mar 22 17:08:42 2011 +0100 s3:docs: remove documentation of idmap read only which was removed. commit 7e2fda2be6f2955b5eb291fb63fdb9518beab597 Author: Michael Adam ob...@samba.org Date: Fri Mar 4 14:25:58 2011 +0100 s3:loadparm: remove unused parameter idmap read only. This has not been released yet and is now useless since we use the idmap config * : read only = ... syntax. commit c45750993eff865c4918dbb3582b38e1bb794eb5 Author: Michael Adam ob...@samba.org Date: Thu Mar 3 17:50:28 2011 +0100 s3:idmap: remove (now) unneeded function parse_idmap_module() commit ce6ac15da1ee9fd6fcc606bed0311bbf076eb183 Author: Michael Adam ob...@samba.org Date: Thu Mar 3 17:48:43 2011 +0100 s3:idmap: simply call idmap_init_named_domain for * in idmap_init_default_domain The default domain * is now treated exactly the same as other explicitly configured domains. commit 7742e87fc8ed1e085ad5f54d3f4b560bba01fc95 Author: Michael Adam ob...@samba.org Date: Thu Mar 3 17:40:36 2011 +0100 s3:idmap: remove passdb argument from idmap_init_domain() commit a3477815a6d86ef99a9e29e8757b017deff31496 Author: Michael Adam ob...@samba.org Date: Wed Mar 2 23:00:58 2011 +0100 s3:idmap: remove the params argument from the init function commit 4e3f9040953809c4baad48d0ff6b8b5cb3ca9aa3 Author: Michael Adam ob...@samba.org Date: Wed Mar 2 17:04:59 2011 +0100 s3:idmap: remove use of params from idmap_ldap_init - it is not used any more commit f04231780aa12a5f2fe4c0435df5f6569c79f548 Author: Michael Adam ob...@samba.org Date: Wed Mar 2 17:08:01 2011 +0100 s3:idmap: remove special treatment of domain * from idmap_ldap_init. The default config via domain * is now treated just as the explicit domain configs. commit 0b1f2f4393d70b038df5cb82b521d6f9c2fd6f6d Author: Michael Adam
[SCM] CTDB repository - branch master updated - ctdb-1.10-178-gfb6987c
The branch, master has been updated via fb6987c2f747d6dbf9bb3899a480124d1c242a90 (commit) from 55c3446c9ba82d24b1d7db92bc3611fd8027b7fb (commit) http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master - Log - commit fb6987c2f747d6dbf9bb3899a480124d1c242a90 Author: Mathieu Parent math.par...@gmail.com Date: Wed Mar 23 00:16:27 2011 +0100 Correction of spelling errors * continous - continuous * activete - activate (thanks to lintian) See https://bugzilla.samba.org/show_bug.cgi?id=6935 Signed-off-by: Michael Adam ob...@samba.org --- Summary of changes: config/events.d/README |2 +- doc/ctdb.1 |4 ++-- doc/ctdb.1.html|4 ++-- doc/ctdb.1.xml |4 ++-- doc/ctdbd.1|4 ++-- doc/ctdbd.1.html |4 ++-- doc/ctdbd.1.xml|4 ++-- server/ctdb_vacuum.c |2 +- 8 files changed, 14 insertions(+), 14 deletions(-) Changeset truncated at 500 lines: diff --git a/config/events.d/README b/config/events.d/README index c05a1fd..024af24 100644 --- a/config/events.d/README +++ b/config/events.d/README @@ -71,7 +71,7 @@ monitor The interval can be configured using the MonitorInterval tunable but defaults to 15 seconds. - This event is triggered by ctdb to continously monitor that all + This event is triggered by ctdb to continuously monitor that all managed services are healthy. When invoked, the event script will check that the service is healthy and return 0 if so. If the service is not healthy the event script diff --git a/doc/ctdb.1 b/doc/ctdb.1 index 2fce654..5cce2fb 100644 --- a/doc/ctdb.1 +++ b/doc/ctdb.1 @@ -786,7 +786,7 @@ This command can be used to remove all content of a database\. .PP In addition to the normal loggign to a log file, CTDBD also keeps a in\-memory ringbuffer containing the most recent log entries for all log levels (except DEBUG)\. .PP -This is useful since it allows for keeping continous logs to a file at a reasonable non\-verbose level, but shortly after an incident has occured, a much more detailed log can be pulled from memory\. This can allow you to avoid having to reproduce an issue due to the on\-disk logs being of insufficient detail\. +This is useful since it allows for keeping continuous logs to a file at a reasonable non\-verbose level, but shortly after an incident has occured, a much more detailed log can be pulled from memory\. This can allow you to avoid having to reproduce an issue due to the on\-disk logs being of insufficient detail\. .PP This command extracts all messages of level or lower log level from memory and prints it to the screen\. .SS clearlog @@ -909,7 +909,7 @@ This command will dump a clustered TDB database to the screen\. This is a debug This command will dump the content of database backup to the screen (similar to ctdb catdb)\. This is a debugging command\. .SS getmonmode .PP -This command returns the monutoring mode of a node\. The monitoring mode is either ACTIVE or DISABLED\. Normally a node will continously monitor that all other nodes that are expected are in fact connected and that they respond to commands\. +This command returns the monutoring mode of a node\. The monitoring mode is either ACTIVE or DISABLED\. Normally a node will continuously monitor that all other nodes that are expected are in fact connected and that they respond to commands\. .PP ACTIVE \- This is the normal mode\. The node is actively monitoring all other nodes, both that the transport is connected and also that the node responds to commands\. If a node becomes unavailable, it will be marked as DISCONNECTED and a recovery is initiated to restore the cluster\. .PP diff --git a/doc/ctdb.1.html b/doc/ctdb.1.html index 5c5078b..169f2ce 100644 --- a/doc/ctdb.1.html +++ b/doc/ctdb.1.html @@ -595,7 +595,7 @@ This is mainly useful for backing up persistent databases such as secrets.tdb an CTDBD also keeps a in-memory ringbuffer containing the most recent log entries for all log levels (except DEBUG). /pp - This is useful since it allows for keeping continous logs to a file + This is useful since it allows for keeping continuous logs to a file at a reasonable non-verbose level, but shortly after an incident has occured, a much more detailed log can be pulled from memory. This can allow you to avoid having to reproduce an issue due to the @@ -678,7 +678,7 @@ HEALTH: NO-HEALTHY-NODES - ERROR - Backup of corrupted TDB in '/var/ctdb/persist This command will dump the content of database backup to the screen (similar to ctdb catdb). This is a debugging command. /p/divdiv class=refsect2 title=getmonmodea name=id541247/ah3getmonmode/h3p -This
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via 6e8b635 fault: fixed smb_panic() prototypes
via 43a0762 fault: fixed call to fault_setup() to use new syntax
via a65ba83 fault: moved fault.c into common library
via 1ac079e fault: switch s4 to use the common fault.c
via 580997e fault: get fault.c ready for use by s4
via 058c3bb fault: moved s3 fault.c to top level
via cb2cc34 fault: rename fault.c to fault_s4.c
from cfae1e7 s3:WHATSNEW: document changes of the id mapping system
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit 6e8b6358ecc7dbebe9681d8e906f82993d0465df
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 10:37:54 2011 +1100
fault: fixed smb_panic() prototypes
Autobuild-User: Andrew Tridgell tri...@samba.org
Autobuild-Date: Wed Mar 23 01:51:44 CET 2011 on sn-devel-104
commit 43a07621bb26c1b6dbe8cfd848dd4d4863ca92b9
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 10:30:36 2011 +1100
fault: fixed call to fault_setup() to use new syntax
commit a65ba83ae6324ed1cbd81c81ddda7a60973aead7
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 10:30:19 2011 +1100
fault: moved fault.c into common library
commit 1ac079e3f6aa9fbbf904e9bdeab557f66487790d
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 10:27:40 2011 +1100
fault: switch s4 to use the common fault.c
commit 580997ede06d587ecf00c6a3faff237806904cd3
Author: Andrew Tridgell tri...@samba.org
Date: Tue Mar 22 16:17:39 2011 +1100
fault: get fault.c ready for use by s4
this moves the s3 specific dumpcore code into source3/lib/dumpcore.c,
and uses a function pointer to setup which smb_panic call to use
commit 058c3bb923c51ef3f1b4b6d698bea2b1220bdd10
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 10:25:01 2011 +1100
fault: moved s3 fault.c to top level
commit cb2cc34effedca2af4e9f6d57303ccc779a9cc04
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 10:22:15 2011 +1100
fault: rename fault.c to fault_s4.c
this is in preparation for merging the s3 fault code into common
---
Summary of changes:
lib/util/fault.c| 248 ---
lib/util/util.h | 13 +-
lib/util/wscript_build |4 +-
source3/Makefile.in |4 +-
source3/include/includes.h |1 -
source3/include/proto.h |6 +-
source3/lib/{fault.c = dumpcore.c} | 85 +++--
source3/lib/util.c |2 +-
source3/nmbd/nmbd.c |2 +-
source3/param/loadparm.c|2 +
source3/smbd/server.c |2 +-
source3/winbindd/winbindd.c |2 +-
source3/wscript_build |3 +-
source4/lib/cmdline/popt_common.c |2 +-
14 files changed, 121 insertions(+), 255 deletions(-)
rename source3/lib/{fault.c = dumpcore.c} (81%)
Changeset truncated at 500 lines:
diff --git a/lib/util/fault.c b/lib/util/fault.c
index 29b45ee..086dc33 100644
--- a/lib/util/fault.c
+++ b/lib/util/fault.c
@@ -1,196 +1,101 @@
-/*
+/*
Unix SMB/CIFS implementation.
Critical Fault handling
Copyright (C) Andrew Tridgell 1992-1998
-
+ Copyright (C) Tim Prouty 2009
+
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
-
+
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
-
+
You should have received a copy of the GNU General Public License
along with this program. If not, see http://www.gnu.org/licenses/.
*/
#include includes.h
-#include version.h
-#include system/wait.h
#include system/filesys.h
+#include version.h
-/**
- * @file
- * @brief Fault handling
- */
-
-/* the registered fault handler */
-static struct {
- const char *name;
- void (*fault_handler)(int sig);
-} fault_handlers;
-
-static const char *progname;
-
-#ifdef HAVE_BACKTRACE
-#include execinfo.h
-#elif HAVE_LIBEXC_H
-#include libexc.h
-#endif
-
-/**
- * Write backtrace to debug log
- */
-_PUBLIC_ void call_backtrace(void)
-{
-#ifdef HAVE_BACKTRACE
-#ifndef BACKTRACE_STACK_SIZE
-#define BACKTRACE_STACK_SIZE 64
+#ifdef HAVE_SYS_SYSCTL_H
+#include sys/sysctl.h
#endif
- void *backtrace_stack[BACKTRACE_STACK_SIZE];
- int backtrace_size;
- char **backtrace_strings;
-
- /* get the backtrace (stack frames) */
- backtrace_size =
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via d73db40 s3-safe_string: Add checked_strlcpy()
via 1d22c39 s3-safe_str: Futher simplify the macros by removing
indirection
via 1923b78 s3-lib Remove the clobber_region() code.
via cd4306b charcnv: remove the automatic fail on allow_badcharcnv true
via 282984f waf: prevent an error in the symbol checking code
via 7aef9c3 s3-config: say which config file we failed to open
from 6e8b635 fault: fixed smb_panic() prototypes
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit d73db405f71002deaddeea68adb747ef1984945c
Author: Andrew Bartlett abart...@samba.org
Date: Tue Mar 22 21:03:59 2011 +1100
s3-safe_string: Add checked_strlcpy()
This is strlcpy, just with an extra check of the parameters with
sizeof(), use only where that works.
Andrew Bartlett
Autobuild-User: Andrew Bartlett abart...@samba.org
Autobuild-Date: Wed Mar 23 03:39:35 CET 2011 on sn-devel-104
commit 1d22c3919d08b4d18a1d021a407a98cb1402d7d7
Author: Andrew Bartlett abart...@samba.org
Date: Tue Mar 22 20:57:36 2011 +1100
s3-safe_str: Futher simplify the macros by removing indirection
Now that we don't need to pass in the function name and string,
another level of indirection can be safely removed, and the operation
of these macros made much clearer.
Andrew Bartlett
commit 1923b78209aaa2aa926dedd19e6c97fb449c48c8
Author: Andrew Bartlett abart...@samba.org
Date: Tue Mar 22 15:30:43 2011 +1100
s3-lib Remove the clobber_region() code.
This code wrote to the full buffer in fstrcpy(), pstrcpy() and other
fixed-length string manipulation functions.
The hope of this code was to find out at run time if we were mixing up
pstring and fstring etc, and to record where this came from. It has a
runtime performance impact (particularly if compiled with
--enable-developer).
It is being removed because of the complexity it adds, and the
distinct lack of bugs that this complexity has been credited in
finding.
The macro-based compile-time checking of string sizes remains.
Andrew Bartlett
commit cd4306b01e4097b76777a9a85cc226e8b0e8f613
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 12:16:44 2011 +1100
charcnv: remove the automatic fail on allow_badcharcnv true
we should just fail the call if the string really is bad
commit 282984fdffee349ac60064de73f13f6e7e288b2f
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 12:15:33 2011 +1100
waf: prevent an error in the symbol checking code
commit 7aef9c3fe01f7ebda8a76a4e849c61c21de8cac4
Author: Andrew Tridgell tri...@samba.org
Date: Wed Mar 23 11:22:15 2011 +1100
s3-config: say which config file we failed to open
saves having to strace it to work that out
---
Summary of changes:
buildtools/wafsamba/symbols.py |3 +-
lib/util/charset/charcnv.c |5 --
source3/Makefile.in|2 +-
source3/include/proto.h| 59 ++--
source3/include/safe_string.h | 115
source3/lib/charcnv.c | 90 ---
source3/lib/clobber.c | 63 --
source3/lib/util.c | 14 -
source3/lib/util_sock.c|4 --
source3/lib/util_str.c | 63 +-
source3/libsmb/clientgen.c |7 ---
source3/libsmb/clistr.c| 51 +++---
source3/nmbd/nmbd.c|2 +-
source3/smbd/negprot.c |2 +-
source3/smbd/server.c |2 +-
source3/smbd/srvstr.c |5 +-
source3/winbindd/winbindd.c|2 +-
source3/wscript_build |2 +-
18 files changed, 120 insertions(+), 371 deletions(-)
delete mode 100644 source3/lib/clobber.c
Changeset truncated at 500 lines:
diff --git a/buildtools/wafsamba/symbols.py b/buildtools/wafsamba/symbols.py
index 0d0af79..0e862cb 100644
--- a/buildtools/wafsamba/symbols.py
+++ b/buildtools/wafsamba/symbols.py
@@ -361,7 +361,8 @@ def check_syslib_dependencies(bld, t):
features = TO_LIST(t.features)
if 'pyembed' in features or 'pyext' in features:
-t.unsatisfied_symbols =
t.unsatisfied_symbols.difference(bld.env.public_symbols['python'])
+if 'python' in bld.env.public_symbols:
+t.unsatisfied_symbols =
t.unsatisfied_symbols.difference(bld.env.public_symbols['python'])
needed = {}
for sym in t.unsatisfied_symbols:
diff --git a/lib/util/charset/charcnv.c b/lib/util/charset/charcnv.c
index dd2c725..9b93312 100644
--- a/lib/util/charset/charcnv.c
+++ b/lib/util/charset/charcnv.c
@@ -134,11 +134,6 @@ _PUBLIC_ bool convert_string_convenience(struct
