Displaying 4 results from an estimated 4 matches for "ctdb_manages_".
2016 Oct 21
6
CTDB and locking issues in 4.4.6 (Classic domain)
...tup here for testing for rollout of S4 AD. The
file servers are in an AD domain and are running Sernet 4.4.5, so one
version older than production. I have tested the locking on these and it
works. The only difference I can find that in prod,
/etc/default/sernet-samba-ctdb contains these lines:
CTDB_MANAGES_SAMBA=yes
CTDB_MANAGES_WINBIND=yes
Whereas in the test environment they are:
CTDB_SERVICE_WINBIND="sernet-samba-winbindd"
CTDB_SERVICE_SMB="sernet-samba-smbd"
I'm wondering if this is what's making the difference?
Cheers,
Alex
--
This message is intended only for th...
2016 Oct 21
0
CTDB and locking issues in 4.4.6 (Classic domain)
...out of S4 AD.
> The file servers are in an AD domain and are running Sernet 4.4.5, so
> one version older than production. I have tested the locking on these
> and it works. The only difference I can find that in prod,
> /etc/default/sernet-samba-ctdb contains these lines:
>
> CTDB_MANAGES_SAMBA=yes
> CTDB_MANAGES_WINBIND=yes
>
> Whereas in the test environment they are:
> CTDB_SERVICE_WINBIND="sernet-samba-winbindd"
> CTDB_SERVICE_SMB="sernet-samba-smbd"
>
> I'm wondering if this is what's making the difference?
>
> Cheers,
>...
2016 Oct 21
1
CTDB and locking issues in 4.4.6 (Classic domain)
...AD domain and are running Sernet 4.4.5, so
> > > one version older than production. I have tested the locking on these
> > > and it works. The only difference I can find that in prod,
> > > /etc/default/sernet-samba-ctdb contains these lines:
> > >
> > > CTDB_MANAGES_SAMBA=yes
> > > CTDB_MANAGES_WINBIND=yes
> > >
> > > Whereas in the test environment they are:
> > > CTDB_SERVICE_WINBIND="sernet-samba-winbindd"
> > > CTDB_SERVICE_SMB="sernet-samba-smbd"
> > >
> > > I'm wonderin...
2019 Jul 09
1
CTDB Samba 4.10 example?
Hi there,
I use Samba 4.9 since its releaseday and also had some troubles first due to the lack of informations in the wiki.
Anyways... after some try & error i got it working and since i run the Cluster (non-production environment) had no errors except CTDBs monitoring of the Samba process did'nt work as i would expect it
(RPC-Server was dead but CTDB did'nt complain and "ctdb