similar to: Turst-Tutorial SambaXP 2019

Since 2014 I do a tutorial on the first day of the SambaXP conference in G?ttingen, this year due to corona it was a online conference :-(. So I had to do my tutorial also as a online version. This years topic was: building a CTDB-cluster with Samba 4.12 and GlusterFS 7.x. If you are interested in the handout and the Vagrant-box and install-script you will find everything here:

Hi Am 29.04.19 um 10:33 schrieb L.P.H. van Belle via samba: > Hai Mason, > > I only dont have the time to work this out now. > But the 2 Stefan'ss have done this part. > > Script + proxymod : Stefan Kania, ask him if he is willing to share his vagrant vm setup. I read my name :-) Yes I created some vagrant-files and scripts to set up some DCs. I did this for my tutorial

On 16/01/2023 18:27, Stefan Kania via samba wrote: > > > Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >> >> >> On 16/01/2023 16:56, Stefan Kania via samba wrote: >>> Hi to all, >>> Is there a known problem when using Debian 11 together with the samba >>> packages from the backports (4.17.4) and the bind9 from the backports

Am 16.01.23 um 20:35 schrieb Ingo Asche via samba: > Hi Stefan, > > I have exact that running: Samba 4.17.4 and bind 9.18 from the > bullseye-backports. > > I my case "samba_dnsupdate --verbose --all-names" runs without any errors. > On the first DC it's running like I expacted, but on the second one I'm having the provlem. > As like 9.16 I use the

Hi to all, Is there a known problem when using Debian 11 together with the samba packages from the backports (4.17.4) and the bind9 from the backports (9.18). With me it comes on each further Domaincontroller to errors with the "samba_dnsupdate --verbose --all-names". If I install Bind9 in version 9.16 everything works. I have the whole thing running in a Vagrant environment and can

On 16/01/2023 18:56, Rowland Penny via samba wrote: > > > On 16/01/2023 18:27, Stefan Kania via samba wrote: >> >> >> Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >>> >>> >>> On 16/01/2023 16:56, Stefan Kania via samba wrote: >>>> Hi to all, >>>> Is there a known problem when using Debian 11 together with the

Hi Stefan, I have exact that running: Samba 4.17.4 and bind 9.18 from the bullseye-backports. I my case "samba_dnsupdate --verbose --all-names" runs without any errors. As like 9.16 I use the "dlz_bind9_18.so" entry in named.conf. If you need further information to compare just ask. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um

On 16/01/2023 16:56, Stefan Kania via samba wrote: > Hi to all, > Is there a known problem when using Debian 11 together with the samba > packages from the backports (4.17.4) and the bind9 from the backports > (9.18). With me it comes on each further Domaincontroller to errors with > the "samba_dnsupdate --verbose --all-names". > > If I install Bind9 in version

Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: > > > On 16/01/2023 16:56, Stefan Kania via samba wrote: >> Hi to all, >> Is there a known problem when using Debian 11 together with the samba >> packages from the backports (4.17.4) and the bind9 from the backports >> (9.18). With me it comes on each further Domaincontroller to errors >> with the

Hi Thomas Am 27.02.23 um 23:10 schrieb Thomas Keppler: > Hi Stefan, > > thanks for the idea! Indeed, I didn't have the third GPO[1] of the bunch, just the two present in the Samba Wiki. > However, applying the third to the client doesn't change the situation. > > I've also resorted to use a Domain Admin and Local Admin account to conduct these tests to rule out any

Hi, The 19th International User and Developer Conference sambaXP (https://sambaxp.org/) will take place from 26th - 28th of May 2020 in G?ttingen, Germany. If you would like to give a presentation, you can submit your paper here: https://sambaxp.org/#c11 Call for paper ends on February 29th. New for this year's event: the Microsoft SMB3 Interoperability Lab (IO Lab) from May 24th-29th,

SambaXP 2020 - Online Edition The 19th International Conference for the open source software Samba will take place from 26th - 28th May 2020 as an *free* online event. The planned IO-Lab is cancelled. SambaXP is the annual meeting of the international Samba team with developers, users, manufacturers and system integrators within the Samba ecosystem, which has been held since 2002. Due to the

Hi, I''ve been trying to pass the http_proxy_host option to puppet but it''s not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:pass@fqdn.com.au --modulepath ''/tmp/vagrant-puppet/modules-0'' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose

Hi gluster ! For those of you who need to spin up virtual gluster clusters for development and testing: Just finished creating a vagrantized, fully automated, totally rebuildable and teardownable two node fedora 19 gluster setup and shared it on the forge! It uses fedora19 but since its all vagrant powered, you dont need to grab or download a distro or iso or anything, just clone the git repo,

Hello, I'm trying to automate the creation of several small samba AD DCs, each with a different domain. Samba tool works fine for creating a brand new domain, but I haven't seen any functionality for manipulating the directory structure of a new domain. Specifically, I'd like to automate the creation of a standard set of OUs, security groups and GPOs. I'm wondering whether

Trying to get SSH agent forwarding working for a popular open source configuration management system called Ansible. I?ve had some unexpected behaviour, the only cause of which I can find is how I express the command line arguments. http://stackoverflow.com/questions/20952689/vagrant-ssh-agent-forwarding-how-is-it-working?noredirect=1#comment31511341_20952689 In summarise: In the first

I'm using libvirt on Debian/stretch (testing) with vagrant and the vagrant-libvirt plugin. When I import a vagrant box (jessie64.box), the resulting file permssions let anyone in the "kvm" group read the img. But when I build upon that box, only root can read it: -rw------- 1 root root 20198785024 Sep 19 18:19 buildserver_default.img -rwxr--r-- 1 libvirt-qemu kvm

Hi, I try install python-psycopg2 with other packages, when run apt-get -y update returns the errors: err: /Stage[main]/Etc/Package[build-essential]/ensure: change from purged to present failed: Could not set ''present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 err:

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

On Sat, Sep 03, 2016 at 02:39:11PM +0800, gunnar.wagner@netcologne.de wrote: > hi all & @Kayshap > > does [this handout on > snapshots](https://kashyapc.fedorapeople.org/virt/lc-2012/snapshots-handout.html) > by Kashyap Chamarthy (I believe from 2012) still apply to current > versions of libvirt-bin & qemu? Yes, as the URL indicates, it's from 2012. And, most of