lp:samba

Created by Jelmer Vernooij on 2009-11-24 and last modified on 2017-07-25
Get this branch:
bzr branch lp:samba

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Samba Team
Project:
samba
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://git.samba.org/samba.git.

The next import is scheduled to run in 4 hours.

Last successful import was 56 minutes ago.

Import started 1 hour ago on russkaya and finished 56 minutes ago taking 10 minutes — see the log
Import started 7 hours ago on pear and finished 7 hours ago taking 7 minutes — see the log
Import started 13 hours ago on russkaya and finished 12 hours ago taking 10 minutes — see the log
Import started 19 hours ago on pear and finished 19 hours ago taking 7 minutes — see the log
Import started on 2017-07-24 on russkaya and finished on 2017-07-24 taking 9 minutes — see the log
Import started on 2017-07-24 on russkaya and finished on 2017-07-24 taking 9 minutes — see the log
Import started on 2017-07-24 on pear and finished on 2017-07-24 taking 7 minutes — see the log
Import started on 2017-07-24 on pear and finished on 2017-07-24 taking 15 minutes — see the log
Import started on 2017-07-23 on russkaya and finished on 2017-07-23 taking 10 minutes — see the log
Import started on 2017-07-23 on pear and finished on 2017-07-23 taking 8 minutes — see the log

Recent revisions

50014. By Volker Lendecke <email address hidden> 3 hours ago

messaging: Remove "struct messaging_backend"

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

Autobuild-User(master): Ralph Böhme <email address hidden>
Autobuild-Date(master): Tue Jul 25 21:35:49 CEST 2017 on sn-devel-144

50013. By Volker Lendecke <email address hidden> 6 hours ago

messaging: Remove messages_ctdbd.c

Replaced by messages_ctdb.[ch]

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50012. By Volker Lendecke <email address hidden> 6 hours ago

ctdb_conn: Use messaging_ctdb_connection

Replace messaging_ctdbd_connection

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50011. By Volker Lendecke <email address hidden> 6 hours ago

messaging: Use messaging_ctdb_ref()

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50010. By Volker Lendecke <email address hidden> 6 hours ago

messages_ctdb: Add messaging_ctdb_connection

This will be the replacement for messaging_ctdbd_connection(). This does not
default to initializing messaging but panics. We just don't have correct
default arguments for messaging_init. Implicit multiple messaging and event
contexts is a bug also.

It *might* be that some tools fail due to this, but this needs fixing in
different ways. See the previous commit for smbpasswd.

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50009. By Volker Lendecke <email address hidden> 6 hours ago

smbpasswd: Initialize messaging for messaging_ctdb_conn

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50008. By Volker Lendecke <email address hidden> 6 hours ago

dbwrap_ctdb: Use messaging_ctdbd_connection

With messages_ctdb, the global ctdb connection will change after fork.

Don't store the wrong parent connection across a fork. The alternative would
be to do a reinit on all dbwrap_ctdb databases, but that seems overkill
given that we only have one "standard" ctdb connection anyway.

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50007. By Volker Lendecke <email address hidden> 6 hours ago

messaging: Add messages_ctdb_ref

Modeled after messages_dgm_ref

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50006. By Volker Lendecke <email address hidden> 6 hours ago

messaging: Add messaging_ctdb_init/destroy

This models connecting to ctdb after the dgm code. The main point
is that we should never open more than more ctdb socket for messaging.

With more than one socket, we might end up with our pid registered with
ctdb on more than one socket. This could lead to memory overconsumption
in ctdb. ctdbd will eventually throw away messages, but they will take
up space unnecessarily.

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

50005. By Volker Lendecke <email address hidden> 6 hours ago

dbwrap: Avoid dbwrap_merge_dbufs in db_ctdb_storev

Signed-off-by: Volker Lendecke <email address hidden>
Reviewed-by: Ralph Boehme <email address hidden>

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers

No subscribers.