summaryrefslogtreecommitdiffstats
path: root/source3
Commit message (Collapse)AuthorAgeFilesLines
...
* s3: Fix Coverity ID 2727 to 2740 -- UNINITVolker Lendecke2012-04-192-9/+14
|
* s3: Fix Coverity ID 2686 -- RESOURCE_LEAKVolker Lendecke2012-04-191-0/+1
|
* s3: Fix the build on FreeBSDVolker Lendecke2012-04-191-1/+1
| | | | | Autobuild-User: Volker Lendecke <vl@samba.org> Autobuild-Date: Thu Apr 19 19:13:45 CEST 2012 on sn-devel-104
* s3: Fix Coverity ID 2682: NULL_RETURNSVolker Lendecke2012-04-191-0/+4
|
* s3: Fix Coverity ID 2743: CHECKED_RETURNVolker Lendecke2012-04-191-3/+6
|
* s3: Fix Coverity ID 2744: CHECKED_RETURNVolker Lendecke2012-04-191-1/+6
|
* s3: Fix Coverity ID 2745 and 2746: FORWARD_NULLVolker Lendecke2012-04-191-11/+15
| | | | We can assume that the rbt dbs are around
* s3: Fix Coverity ID 2747: FORWARD_NULLVolker Lendecke2012-04-191-1/+1
| | | | | | For the notify cleanup process we have a notify context without a messaging entry. We will never call notify_add/remove for this, but the code should protect against this.
* s3: Attempt to fix Coverity ID 2748: INTEGER_OVERFLOWVolker Lendecke2012-04-191-1/+1
| | | | Not sure this will actually please Coverity, but it fixes a severe bug
* s3: Fix Coverity ID 2749: REVERSE_INULLVolker Lendecke2012-04-191-1/+3
|
* s3-xattr_tdb: Remove dead code: talloc_stackframe() cannot failAndrew Bartlett2012-04-192-20/+0
| | | | | Autobuild-User: Andrew Bartlett <abartlet@samba.org> Autobuild-Date: Thu Apr 19 14:15:42 CEST 2012 on sn-devel-104
* s3-dbwrap: Remove dead code: talloc_stackframe() cannot failAndrew Bartlett2012-04-191-10/+1
|
* s3-passdb: Remove unused sampass->pass_must_change_timeAndrew Bartlett2012-04-197-45/+3
| | | | | | | | | | | | There is no need to call pdb_set_pass_must_change_time() because nothing ever consults that value. It is always calculated from the domain policy. Also, this means we no longer store the value in LDAP. The value would only ever be set when migrating from tdbsam or smbpasswd, not on password changes, so would become incorrect over time. Andrew Bartlett
* s3: Fix a "ISO C90 forbids mixed declarations and code"Volker Lendecke2012-04-191-3/+7
| | | | | Autobuild-User: Volker Lendecke <vl@samba.org> Autobuild-Date: Thu Apr 19 10:32:27 CEST 2012 on sn-devel-104
* Ensure we have 12 bytes of data for a SMB_SET_CIFS_UNIX_INFO call. Add debug.Jeremy Allison2012-04-181-1/+4
|
* s3-dbwrap: Fix an unused var warningVolker Lendecke2012-04-181-0/+2
|
* libsmb: Actually use an introduced variableVolker Lendecke2012-04-181-2/+2
| | | | | Autobuild-User: Volker Lendecke <vl@samba.org> Autobuild-Date: Wed Apr 18 13:39:53 CEST 2012 on sn-devel-104
* s3-xattr_tdb: Use talloc_stackframe() more to allow calling from common codeAndrew Bartlett2012-04-181-14/+31
|
* s3-xattr_tdb: Be nice to xattr_tdb_getxattr callers, return the full blobAndrew Bartlett2012-04-183-11/+47
| | | | | | | | | | | In this case, the blob is already in memory, so it is easier to return the full blob to the caller, and let the caller decide if some interface restriction stops the full blob from being passed all the way up the stack. This allows us to quickly write a python wrapper for this xattr storage mechanism. Andrew Bartlett
* s3-xattr_tdb: make xattr_tdb a private library, for use outside vfs_xattr_tdbAndrew Bartlett2012-04-186-428/+505
|
* s3-lib: Add file_id_string()Andrew Bartlett2012-04-182-3/+23
|
* s3-build: move file_id.c into samba3-util and create a private headerAndrew Bartlett2012-04-185-8/+34
|
* dbwrap: Add dbwrap_tdb to private dbwrap libraryAndrew Bartlett2012-04-181-3/+2
| | | | Andrew Bartlett
* s3-build: Add missing samba3-util dep to tdb-wrap3Andrew Bartlett2012-04-181-1/+1
|
* lib/util: Move map_nt_error_from_tdb to the top levelAndrew Bartlett2012-04-181-58/+0
| | | | | | This will help with making dbwrap available as a top level library. Andrew Bartlett
* s3-dbwrap: push lp_ctx up another layer in the stackAndrew Bartlett2012-04-184-6/+10
| | | | | | | | | | This will allow db_open_tdb() to be called from common code, which may already have a loadparm context loaded. It also slowly moves the lp_ctx up the stack, as required to remove the library loop between smbconf and the registry. Andrew Bartlett
* s3-dbwrap: Add talloc_stackframe() callsAndrew Bartlett2012-04-181-5/+21
| | | | | | | This is in preperation for calling dbwrap from common code, where we may not have a stackframe set up. Andrew Bartlett
* build: Remove more of the s3 special cases in waf: only pidfile.c needs ↵Andrew Bartlett2012-04-181-1/+7
| | | | -DCONFIGFILE
* s3-waf: Add possibility to build with system libsmbclient.Andreas Schneider2012-04-172-34/+41
|
* s3-waf: Fix client/smbclient dependencies.Andreas Schneider2012-04-171-7/+7
|
* s3:libsmb/cliconnect: make use of ntlmssp_is_anonymous()Stefan Metzmacher2012-04-171-1/+1
| | | | | | | metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Tue Apr 17 16:16:51 CEST 2012 on sn-devel-104
* s3:libsmb/ntlmssp: improve anonymous loginsStefan Metzmacher2012-04-171-2/+3
| | | | | | | smbtorture3 (and maybe others) use fstrings for 'user' and 'password', so we need to check for empty strings. metze
* s3:libsmb/ntlmssp: add ntlmssp_is_anonymous()Stefan Metzmacher2012-04-172-0/+16
| | | | metze
* s3:libsmb/ntlmssp: remove some indentation in ntlmssp_set_password()Stefan Metzmacher2012-04-171-18/+20
| | | | metze
* Revert "s3:libsmb/ntlmssp: an empty string should mean no password"Stefan Metzmacher2012-04-171-1/+1
| | | | This reverts commit 92483eee254ef6844fe88abe1e64f67033a1ea2d.
* s3: Add smbstatus -N to output the notify dbVolker Lendecke2012-04-173-1/+42
| | | | | Autobuild-User: Volker Lendecke <vl@samba.org> Autobuild-Date: Tue Apr 17 11:54:35 CEST 2012 on sn-devel-104
* s3: Add "notify-cleanup" to smbcontrolVolker Lendecke2012-04-171-0/+13
| | | | This triggers a notify cleanup run which would normally only run periodically
* s3: New notify implementationVolker Lendecke2012-04-177-758/+1080
| | | | | | | | | | | | 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
* s3: Add two notify benchmark testsVolker Lendecke2012-04-175-0/+727
|
* s3: Make torture_nprocs globally availableVolker Lendecke2012-04-171-19/+19
|
* s3: Make ctdbd_messaging_send_blob available in non-clustered modeVolker Lendecke2012-04-171-1/+10
| | | | This will avoid the need for some #ifdefs
* s3: Make messaging_ctdbd_connection available in non-clustered modeVolker Lendecke2012-04-171-0/+9
| | | | This might make some #ifdef CLUSTER_SUPPORT unnecessary in the future
* s3: Implement tevent_barrierVolker Lendecke2012-04-173-0/+235
| | | | | | | | This will help notify torture tests: A tevent barrier can be waited on with tevent_barrier_wait_send/recv. The barrier is initialized with a number of requests that it will accept waiting. When that number is reached, all those requests will be released and their callback will be called. The barrier will be free for re-use again.
* s3: Start a list of ctdb srvid assigmentsVolker Lendecke2012-04-171-0/+40
|
* s3: Introduce ctdb_messaging_send_blobVolker Lendecke2012-04-172-20/+23
| | | | Send a raw blob without the messaging.idl wrap
* s3: Add msg_channelVolker Lendecke2012-04-177-0/+551
| | | | This is a tevent_based variant of messaging_register
* s3: Add messaging_tdb_event()Volker Lendecke2012-04-172-0/+13
| | | | | | | | This is a void* that represents a signal handler attached to some custom tevent_context. This is necessary to make the tdb based messaging infrastructure trigger its business when we are sitting in tevent_loop_once for an event context that is not the main one in the messaging context.
* s3: Add a second ctdb connect libraryVolker Lendecke2012-04-177-0/+931
| | | | The existing one is not async at all.
* s3: Add dbwrap_try_fetch_lockedVolker Lendecke2012-04-178-16/+97
| | | | | | | | | | This is designed to spread the load on individual ctdb records to allow upper layers to do backoff mechanisms. In the ctdb case, do not get the record if a local lock is already taken. If we are not dmaster, do at most one migrate attempt. For the tdb case, this is a nonblocking fetch_locked. If someone else has the lock, give up.
* s3: Add dbwrap_cacheVolker Lendecke2012-04-174-1/+244
| | | | | | This is a caching layer for the notify database and potentially for the brlock database. It caches the parse_record operation as long as the underlying seqnum does not change.
generated by cgit (git 2.34.1) at 2025-09-29 16:22:33 +0000