summaryrefslogtreecommitdiff
path: root/source3/librpc/idl/messaging.idl
AgeCommit message (Collapse)AuthorFilesLines
2012-04-20s3:id_cache: do not use the in-memory idmap cache (it is going to be removed)Michael Adam1-1/+1
This also removes the ID_CACHE_FLUSH message.
2012-04-19s3-dbwrap: Add dbwrap_record_watch_send/recvVolker Lendecke1-1/+2
With this API you can asynchronously wait for a record to be modified
2012-04-17s3: New notify implementationVolker Lendecke1-0/+3
From notify_internal.c: /* * The notify database is split up into two databases: One * relatively static index db and the real notify db with the * volatile entries. */ This change is necessary to make notify scale better in a cluster
2011-12-13s3:messaging.idl: obsolete unused MSG_SMB_SAM_*Stefan Metzmacher1-2/+2
metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Tue Dec 13 14:13:38 CET 2011 on sn-devel-104
2011-10-31s3: Remove some leftovers of old ctdb tdb2 codeVolker Lendecke1-16/+1
2011-08-21s3-id_cache: Use better names for id cache management opsAndreas Schneider1-3/+3
The IDMAP term is normally associated with Winbind's idmap stuff. These functions deal with id caching not id mapping. Signed-off-by: Simo Sorce <idra@samba.org>
2011-08-21s3-messaging: Add preforked child-parent message typesSimo Sorce1-0/+3
Signed-off-by: Andreas Schneider <asn@samba.org> Signed-off-by: Simo Sorce <idra@samba.org>
2011-08-19Revert "s3-messaging: IDMAP_ messages belongs to the Winbind range"Simo Sorce1-4/+4
This reverts commit 102f39ae3e7df26faf81595c8e0120b2e2a45bbd. These messages are handled by smbd not winbind, and could potentially be of general interest. Autobuild-User: Simo Sorce <idra@samba.org> Autobuild-Date: Fri Aug 19 16:16:05 CEST 2011 on sn-devel-104
2011-08-16s3-messaging: IDMAP_ messages belongs to the Winbind rangeSimo Sorce1-4/+4
Autobuild-User: Simo Sorce <idra@samba.org> Autobuild-Date: Tue Aug 16 22:27:05 CEST 2011 on sn-devel-104
2011-08-11s3-messaging: Change classification of MSG_SMB_CONF_UPDATED.Simo Sorce1-1/+4
smbd is not the only daemon interested in smb.conf changes. Move this message to the GENERAL class so that all interested partied (nmbd, winbindd, spoolssd, etc..) can receive this notification. Signed-off-by: Andreas Schneider <asn@samba.org>
2011-08-11s3-messaging: Fix messaging classes.Simo Sorce1-1/+1
This has been broken since ff0ac5b0 (May 2007). Basically all messages were belonging to the General class except for CTDB messages. This fixed the message_send_all() function to correctly compute the class, and fixes registrations to include all they need to cope with the fact not all messages are of calss general (registrations rotted a bit because as long as FLAG_MSG_GENERAL was defined the process woould receive all messages). Signed-off-by: Andreas Schneider <asn@samba.org>
2011-08-11s3-messaging: Remove obsolete class.Simo Sorce1-1/+1
The FLAG_MSG_PRINT_NOTIFY class is actually obsolete and never used, as the only message belonging to it is not used either. Signed-off-by: Andreas Schneider <asn@samba.org>
2011-05-20s3:smbd remove unused codeChristian Ambach1-1/+0
in the early CTDB days, the RELEASE_IP message was defined and some code was added to react on such a message to make smbd exit if the IP address it was using for the server socket is removed by CTDB. Later, it was discovered that we need to stop smbd immediately and logic was added to ctdb_conn to call release_ip() without going through the messaging system. So this code is not used and can be removed Autobuild-User: Christian Ambach <ambi@samba.org> Autobuild-Date: Fri May 20 16:18:24 CEST 2011 on sn-devel-104
2011-02-28s3: smbcontrol to notify smbd about idmap changesGregor Beck1-0/+4
Autobuild-User: Michael Adam <obnox@samba.org> Autobuild-Date: Mon Feb 28 14:07:23 CET 2011 on sn-devel-104
2011-02-17s3: add server_id.idl and use only autogenerated code.Günther Deschner1-1/+2
Volker, Tridge and other clustering gurus, please check. It is ok to get rid of ifdef CLUSTER_SUPPORT here, right ? Why was unique_id not marshalled at all ? Guenther
2011-02-16s3-librpc: move server_id marshalling to own helper file.Günther Deschner1-1/+1
(in preparation of merging struct server_id). Guenther Autobuild-User: Günther Deschner <gd@samba.org> Autobuild-Date: Wed Feb 16 00:02:33 CET 2011 on sn-devel-104
2011-02-10s3: give ../librpc/ndr/util.c its own header.Günther Deschner1-0/+1
Guenther
2011-01-07s3-printing: Initiate pcap reload from parent smbdDavid Disseldorp1-0/+1
Since commit 7022554, smbds share a printcap cache (printer_list.tdb), therefore ordering of events between smbd processes is important when updating printcap cache information. Consider the following two process example: 1) smbd1 receives HUP or printcap cache time expiry 2) smbd1 checks whether pcap needs refresh, it does 3) smbd1 marks pcap as refreshed 4) smbd1 forks child1 to obtain cups printer info 5) smbd2 receives HUP or printcap cache time expiry 6) smbd2 checks whether pcap needs refresh, it does not (due to step 3) 7) smbd2 reloads printer shares prior to child1 completion (stale pcap) 8) child1 completion, pcap cache (printer_list.tdb) is updated by smbd1 9) smbd1 reloads printer shares based on new pcap information In this case both smbd1 and smbd2 are reliant on the pcap update performed on child1 completion. The prior commit "reload shares after pcap cache fill" ensures that smbd1 only reloads printer shares following pcap update, however smbd2 continues to present shares based on stale pcap data. This commit addresses the above problem by driving pcap cache and printer share updates from the parent smbd process. 1) smbd0 (parent) receives a HUP or printcap cache time expiry 2) smbd0 forks child0 to obtain cups printer info 3) child0 completion, pcap cache (printer_list.tdb) is updated by smbd0 4) smbd0 reloads printer shares 5) smbd0 notifies child smbds of pcap update via message_send_all() 6) child smbds read fresh pcap data and reload printer shares This architecture has the additional advantage that only a single process (the parent smbd) requests printer information from the printcap backend. Use time_mono in housekeeping functions As suggested by Björn Jacke.
2010-09-30s3: Add "smbcontrol winbindd ip-dropped <local-ip>"Volker Lendecke1-0/+1
This is supposed to improve the winbind reconnect time after an ip address has been moved away from a box. Any kind of HA scenario will benefit from this, because winbindd does not have to wait for the TCP timeout to kick in when a local IP address has been dropped and DC replies are not received anymore.
2010-02-12s3: Implement global locks in a g_lock tdbVolker Lendecke1-1/+2
This is the basis to implement global locks in ctdb without depending on a shared file system. The initial goal is to make ctdb persistent transactions deterministic without too many timeouts.
2008-09-12messaging: move types to IDL.Günther Deschner1-1/+83
Guenther (This used to be commit 6c346d0eb20af5ba9b09f30319420f7c91480da6)
2008-04-12messaging.idl: add structure to marshall dbwrap_tdb2 changesStefan Metzmacher1-0/+15
metze (This used to be commit 46a0d8e872af1ab420705a514c1d7b1b21459f82)
2007-10-10r23055: Rewrite messages.c to use auto-generated marshalling in the tdb. I'mVolker Lendecke1-0/+26
doing this because for the clustering the marshalling is needed in more than one place, so I wanted a decent routine to marshall a message_rec struct which was not there before. Tridge, this seems about the same speed as it used to be before, the librpc/ndr overhead in my tests was under the noise. Volker (This used to be commit eaefd00563173dfabb7716c5695ac0a2f7139bb6)
generated by cgit (git 2.34.1) at 2024-11-27 05:04:28 +0000