Re: [Samba] upgrade from 3.5 -> 3.6, now I have "no backend defined for idmap"
On Tue, Feb 05, 2013 at 01:56:26PM -0600, Dale Schroeder (d...@briannassaladdressing.com) wrote: > On 02/05/2013 12:08 AM, Jobst Schmalenbach wrote: > >Hi Dale > > [snip snap snip] > > Sorry that I don't have any concrete reasons as to the "why" of any > of these things. ;-) love that line. Jobst -- A loving atmosphere in your home is the foundation for your life. | |0| | Jobst Schmalenbach, jo...@barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia -- 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 3.5 -> 3.6, now I have "no backend defined for idmap"
On 02/05/2013 12:08 AM, Jobst Schmalenbach wrote: Hi Dale that worked, thanks. Just to clarify the "*" means everything else, right? That's how I understand it. On the sites I visited while gathering this information, no one seemed to know why it is required, only that everything started working after it was added. Cause now I am getting (only once) [2013/02/04 07:50:48.519114, 1] winbindd/idmap.c:288(idmap_init_named_domain) no backend defined for idmap config BUILTIN I have that line, too and also a lot of other lines regarding BUILTIN. Everything is working, so I haven't put any effort into finding out why. If you run "cat" against your Samba logs and grep for BUILTIN, you'll see what I mean. One strange side effect ... I have never had to reboot a machine because of a change to the samba daemon(s), a restart always worked. For a couple of days after the change I still was getting the message until I rebooted ... now I do not get the messages, weird. On rare occasions, I've had to do the same thing. It's something I would try when all else failed. Sorry that I don't have any concrete reasons as to the "why" of any of these things. Dale Jobst On Tue, Jan 29, 2013 at 01:17:52PM -0600, Dale Schroeder (d...@briannassaladdressing.com) wrote: Jobst, The following works for me in 3.6.x. Modify to match your criteria. idmap config * : backend= tdb idmap config * : range = - idmap config DOMAIN : default = Yes idmap config DOMAIN : backend = idmap config DOMAIN : range = - Dale On 01/28/2013 10:51 PM, Jobst Schmalenbach wrote: Hi. I am getting loads of errors "no backend defined for idmap config MYDOMAIN" after I upgraded from 3.5 -> 3.6 a couple of days ago. I read http://wiki.samba.org/index.php/Samba_3.6_Features_added/changed and did what man smb.conf suggested: idmap config MYDOMAIN : backend = tdb idmap config MYDOMAIN : range = 500-199 yet I still receive those errors. I used to have idmap uid = 500-1000 idmap gid = 500-1000 and I had no errors while running 3.5.10. I am not sure what I am doing wrong, help please. Jobst -- 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 3.5 -> 3.6, now I have "no backend defined for idmap"
Hi Dale that worked, thanks. Just to clarify the "*" means everything else, right? Cause now I am getting (only once) [2013/02/04 07:50:48.519114, 1] winbindd/idmap.c:288(idmap_init_named_domain) no backend defined for idmap config BUILTIN One strange side effect ... I have never had to reboot a machine because of a change to the samba daemon(s), a restart always worked. For a couple of days after the change I still was getting the message until I rebooted ... now I do not get the messages, weird. Jobst On Tue, Jan 29, 2013 at 01:17:52PM -0600, Dale Schroeder (d...@briannassaladdressing.com) wrote: > Jobst, > > The following works for me in 3.6.x. Modify to match your criteria. > > idmap config * : backend= tdb > idmap config * : range = - > idmap config DOMAIN : default = Yes > idmap config DOMAIN : backend = > idmap config DOMAIN : range = - > > > Dale > > On 01/28/2013 10:51 PM, Jobst Schmalenbach wrote: > >Hi. > > > >I am getting loads of errors "no backend defined for idmap config MYDOMAIN" > >after I upgraded from 3.5 -> 3.6 a couple of days ago. > > > >I read > > > > http://wiki.samba.org/index.php/Samba_3.6_Features_added/changed > > > >and did what > > man smb.conf > > > >suggested: > > > > idmap config MYDOMAIN : backend = tdb > > idmap config MYDOMAIN : range = 500-199 > > > > > >yet I still receive those errors. I used to have > > > > idmap uid = 500-1000 > > idmap gid = 500-1000 > > > >and I had no errors while running 3.5.10. > > > >I am not sure what I am doing wrong, help please. > > > > > > > >Jobst > > > > > > > > > > > > > > > > -- The journey of a thousand steps begins with few hundred forgotten necessities. | |0| | Jobst Schmalenbach, jo...@barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia -- 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 3.5 -> 3.6, now I have "no backend defined for idmap"
Jobst, The following works for me in 3.6.x. Modify to match your criteria. idmap config * : backend= tdb idmap config * : range = - idmap config DOMAIN : default = Yes idmap config DOMAIN : backend = idmap config DOMAIN : range = - Dale On 01/28/2013 10:51 PM, Jobst Schmalenbach wrote: Hi. I am getting loads of errors "no backend defined for idmap config MYDOMAIN" after I upgraded from 3.5 -> 3.6 a couple of days ago. I read http://wiki.samba.org/index.php/Samba_3.6_Features_added/changed and did what man smb.conf suggested: idmap config MYDOMAIN : backend = tdb idmap config MYDOMAIN : range = 500-199 yet I still receive those errors. I used to have idmap uid = 500-1000 idmap gid = 500-1000 and I had no errors while running 3.5.10. I am not sure what I am doing wrong, help please. Jobst -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
