summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2011-08-13samba-tool: Remove gpo setacl commandAmitay Isaacs1-5/+0
2011-08-12s3:smb2cli: pass more fields to smb2cli_req_create()/smb2cli_req_send()Stefan Metzmacher11-16/+80
The caller should take care of the global cli_state values. metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Fri Aug 12 19:38:27 CEST 2011 on sn-devel-104
2011-08-12s3:smb2cli: allow 32bit dyn_len in smb2cli_req_create()/smb2cli_req_send()Stefan Metzmacher2-5/+5
metze
2011-08-12s3:libsmb: keep a cli_smb_state->one_wayStefan Metzmacher1-12/+19
This moves the SMB1 specific stuff to cli_smb_req_create(), instead of having it in the core dispatching code. metze
2011-08-12s3:libsmb: abstract the incoming dispatch function via a function pointerStefan Metzmacher2-5/+17
This will allow handling of SMB2 in future. metze
2011-08-12s3:libsmb: split out cli_state_dispatch_smb1() from cli_smb_received()Stefan Metzmacher1-45/+66
metze
2011-08-12s3:libsmb: add missing TALLOC_FREE(frame) to cli_smb_received()Stefan Metzmacher1-0/+1
metze
2011-08-12s3:smb2_server: make sure we prefer responses over requests on the client socketStefan Metzmacher1-12/+52
metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Fri Aug 12 16:46:43 CEST 2011 on sn-devel-104
2011-08-12selftest:Samba4: test --domain-critical-only in provision_vampire_dc()Stefan Metzmacher1-1/+1
This way only only replicate critical objects during the initial join as DC, then we'll replicate the whole domain while 'samba' is running. metze Signed-off-by: Andrew Tridgell <tridge@samba.org> Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Fri Aug 12 14:07:50 CEST 2011 on sn-devel-104
2011-08-12s3:samba-tool: add --domain-critical-only to "samba-tool domain join"Stefan Metzmacher1-3/+9
metze Signed-off-by: Andrew Tridgell <tridge@samba.org>
2011-08-12s4:py/samba/join: add domain_critical_only=False to join_DC/join_RODCStefan Metzmacher1-3/+10
metze Signed-off-by: Andrew Tridgell <tridge@samba.org>
2011-08-12s4:py/samba/drs_utils: pass down req/req_level to self.net.replicate_chunk()Stefan Metzmacher1-1/+2
metze Signed-off-by: Andrew Tridgell <tridge@samba.org>
2011-08-12s4:libnet_vampire: don't keep the replication state if ↵Stefan Metzmacher1-0/+30
DRSUAPI_DRS_CRITICAL_ONLY was used In that case we have incomplete information and need to start from 0 in the next run. metze Signed-off-by: Andrew Tridgell <tridge@samba.org>
2011-08-12s4:libnet: passdown the DsGetNCChangesReq* to the libnet_BecomeDC_StoreChunk ↵Stefan Metzmacher3-4/+72
handler metze Signed-off-by: Andrew Tridgell <tridge@samba.org>
2011-08-12selftest:target/Samba4: use the correct configuration in setup_vampire_dc()Stefan Metzmacher1-0/+2
This allows "TDB_NO_FSYNC=1 make -j test TESTS=vampire" to work. metze Signed-off-by: Andrew Tridgell <tridge@samba.org>
2011-08-12s3:libsmb: keep the request order in cli_smb_req_unset_pending()Stefan Metzmacher1-1/+3
metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Fri Aug 12 12:36:03 CEST 2011 on sn-devel-104
2011-08-12s3:libsmb: use tevent_req_defer_callback() unless there's only one request ↵Stefan Metzmacher1-4/+41
in cli_smb_received() Callers of tevent_req_done() (or similar functions) have to return directly. Otherwise the callback could invalidate the current stack state, which is likely to trigger segfaults. If there was only one pending request and we just got the response for that one, we can use tevent_req_done() directly. Otherwise there're more pending requests and we need to call cli_state_receive_next() or we got the response for chained requests. Both means that we have to use tevent_req_defer_callback(). metze
2011-08-12s3:libsmb: make use of cli_state_receive_next() in cli_smb_received()Stefan Metzmacher1-17/+2
metze
2011-08-12s3:libsmb: notify all request about failures in cli_smb_req_set_pending()Stefan Metzmacher1-0/+7
It's up to the caller to notify the current request, but we have to notify all other pending requests if we're not able to read the next response from the server. metze
2011-08-12s3:libsmb: split out cli_state_receive_next() from cli_smb_req_set_pending()Stefan Metzmacher1-2/+25
metze
2011-08-12s3:libsmb: use talloc_stackframe() in cli_smb_received()Stefan Metzmacher1-8/+12
metze
2011-08-12s3:libsmb: call cli_smb_req_unset_pending() before tevent_req_done() also ↵Stefan Metzmacher1-0/+1
for chained requests metze
2011-08-12s3:libsmb: reset the destructor in cli_smb_req_unset_pending()Stefan Metzmacher1-1/+2
metze
2011-08-12s3:libsmb: add cli_state_notify_pending() and use itStefan Metzmacher1-25/+45
If we got a problem on the connection we need to notify every pending request. But we need to make use of tevent_req_defer_callback() before tevent_req_nterror(), otherwise the callback, triggered by tevent_req_nterror(), could invalidate the state of current caller, which will likely cause segfaults. metze
2011-08-12s4-test: use standard process model for 'dc' serverAndrew Tridgell1-20/+12
this provides us with both 'standard' and 'single' process models in selftest, ensuring that we test the standard process model in the build farm Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org> Autobuild-User: Andrew Tridgell <tridge@samba.org> Autobuild-Date: Fri Aug 12 11:06:50 CEST 2011 on sn-devel-104
2011-08-12socket-wrapped: added wrappers for dup() and dup2()Andrew Tridgell2-2/+131
The Samba4 standard process model uses dup() on incoming sockets as an optimisation (it makes select() a tiny bit faster when used). Adding dup() to socket wrapper allows us to use the standard process model in selftest Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s3:selftest: run smbtorture3 CHAIN1/CHAIN2 testsStefan Metzmacher2-2/+1
metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Fri Aug 12 09:37:04 CEST 2011 on sn-devel-104
2011-08-12tevent: don't force the nesting flag to false in the destructorAndrew Tridgell1-3/+7
the tevent destructor is called in tevent_re_initialise(), to reset the event context back to its original state for creating child processes. We need the nesting flag to stay the same Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org> Autobuild-User: Andrew Tridgell <tridge@samba.org> Autobuild-Date: Fri Aug 12 05:18:25 CEST 2011 on sn-devel-104
2011-08-12s4-dbcheck: offer to fix dsServiceName to be in GUID formAndrew Tridgell1-0/+43
this fixes the dsServiceName so it can handle server renames Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s4-dsdb: don't cache the NTDS settings DNAndrew Tridgell1-9/+8
this DN can change due to a server rename, so we cannot cache it. It is set by provision, but not anywhere else. This seems to not have a large performance impact Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s4-join: make dsServiceName a GUID in @ROOTDSE on joinAndrew Tridgell1-3/+5
when joining another domain as a DC we should setup our dsServiceName in @ROOTDSE to be a GUID so we can cope with later server renames Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s4-provision: create dsServiceName in @ROOTDSE in GUID formAndrew Tridgell2-1/+4
this allows for handling of server renames as the GUID doesn't change Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s4-dsdb: expand dsServiceName from GUID form at runtimeAndrew Tridgell1-6/+54
this allows dsServiceName to be stored as an extended DN or GUID form in @ROOTDSE, and its string form will be found at runtime. Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s4-dsdb: remove the naming_fsmo and pdc_fsmo modulesAndrew Tridgell3-42/+0
these are not needed now that the rootdse modules calculates the validFSMOs attribute at runtime Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-12s4-dsdb: calculate validFSMOs at runtime instead of pre-computingAndrew Tridgell3-251/+45
this changes the rootdse to compute the validFSMOs attribute at runtime by checking the fSMORoleOwner attribute on the appropriate DN. This avoids the need for the pdc_fsmo and naming_fsmo modules. Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-11tevent: fix documentation for tevent_context_init_byname()Sumit Bose1-2/+2
Signed-off-by: Simo Sorce <idra@samba.org> Autobuild-User: Simo Sorce <idra@samba.org> Autobuild-Date: Thu Aug 11 21:56:37 CEST 2011 on sn-devel-104
2011-08-11tevent: Set FD_CLOEXEC on epoll handleSumit Bose4-2/+52
If an application using libtevent starts a new process the epoll file descriptor is leaked to the new process if the event context is not freed explicitly. By setting FD_CLOEXEC this is not needed anymore. Signed-off-by: Simo Sorce <idra@samba.org>
2011-08-11s3-messaging: Do not register to classes we are not going to use.Simo Sorce3-5/+4
Signed-off-by: Andreas Schneider <asn@samba.org> Autobuild-User: Andreas Schneider <asn@cryptomilk.org> Autobuild-Date: Thu Aug 11 17:09:30 CEST 2011 on sn-devel-104
2011-08-11s3-messaging: Change classification of MSG_SMB_CONF_UPDATED.Simo Sorce2-2/+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 Sorce5-12/+19
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 Sorce5-19/+2
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-08-11s3:build(autoconf): fix bug #8369: remove irritating "." targets when recent ↵Michael Adam3-9/+19
system libs exist Autobuild-User: Michael Adam <obnox@samba.org> Autobuild-Date: Thu Aug 11 13:26:27 CEST 2011 on sn-devel-104
2011-08-10Adapt tally_histogram to Samba coding conventionsVolker Lendecke1-10/+16
Autobuild-User: Volker Lendecke <vlendec@samba.org> Autobuild-Date: Wed Aug 10 21:12:59 CEST 2011 on sn-devel-104
2011-08-10Adapt get_max_bucket to Samba coding conventionsVolker Lendecke1-2/+4
2011-08-10Adapt tally_approx_median to Samba coding conventionsVolker Lendecke1-1/+2
2011-08-10Adapt bucket_range to Samba coding conventionsVolker Lendecke1-2/+3
2011-08-10Adapt tally_mean to Samba coding conventionsVolker Lendecke1-1/+2
2011-08-10Adapt divls64 to Samba coding conventionsVolker Lendecke1-1/+2
2011-08-10Avoid some // style comments in divls64Volker Lendecke1-9/+10
2011-08-10Adapt divlu64 to Samba coding conventionsVolker Lendecke1-2/+5
generated by cgit (git 2.34.1) at 2024-07-13 04:05:13 +0000