summaryrefslogtreecommitdiffstats
path: root/source3
Commit message (Collapse)AuthorAgeFilesLines
...
* s3: Use smbsock_any_connect in winbindVolker Lendecke2010-12-221-45/+13
|
* s3: Retry *SMBSERVER in nb_connectVolker Lendecke2010-12-221-2/+47
|
* s3: Test smbsock_any_connectVolker Lendecke2010-12-224-0/+49
|
* s3: Add smbsock_any_connectVolker Lendecke2010-12-222-1/+232
|
* s3: Add an async smbsock_connectVolker Lendecke2010-12-223-0/+320
| | | | | | This connects to 445 and after 5 milliseconds also to 139. It treats a netbios session setup failure as equivalent as a TCP connect failure. So if 139 is faster but fails the nb session setup, the 445 still has the chance to succeed.
* s3: Add async cli_session_requestVolker Lendecke2010-12-222-0/+134
| | | | This does not do the redirects, but I think that might be obsolete anyway
* s3: Add some const to name_mangle()Volker Lendecke2010-12-222-2/+2
|
* s3-waf: fix the build.Günther Deschner2010-12-221-1/+2
| | | | | | | Guenther Autobuild-User: Günther Deschner <gd@samba.org> Autobuild-Date: Wed Dec 22 15:55:11 CET 2010 on sn-devel-104
* s3:lib/gencache: fix memory leak in error pathStefan Metzmacher2010-12-221-0/+3
| | | | | | | metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Wed Dec 22 15:08:30 CET 2010 on sn-devel-104
* s3-printing: fix crash bug in print_spool_open().Günther Deschner2010-12-221-1/+3
| | | | | | | Guenther Autobuild-User: Günther Deschner <gd@samba.org> Autobuild-Date: Wed Dec 22 14:21:58 CET 2010 on sn-devel-104
* s3-spoolss: handle NTTIME(0) as "01/01/1601" REG_SZ in driver dates.Günther Deschner2010-12-221-4/+13
| | | | Guenther
* s3:libsmb/namequery.c: don't leak 'pserver'Stefan Metzmacher2010-12-221-2/+2
| | | | | | | metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Wed Dec 22 09:54:31 CET 2010 on sn-devel-104
* Fix a warning message.Jeremy Allison2010-12-221-1/+2
| | | | | Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Wed Dec 22 03:59:18 CET 2010 on sn-devel-104
* My algorithm for determining whan an incoming sequence number can be allowed ↵Jeremy Allison2010-12-212-6/+8
| | | | | | | | | | is incorrect. (I based it on the text in MS-SMB2, silly me :-). Fix it so incoming sequence numbers can range over the entire allowable bitmap range. This fixes a repeatable disconnect against Win7. Jeremy.
* s3:cli_np_tstream: if SMBtrans is desired, the readv needs to wait for the ↵Stefan Metzmacher2010-12-211-23/+70
| | | | | | | | | last writev chunk. metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Tue Dec 21 17:43:06 CET 2010 on sn-devel-104
* s3/s4:auth SPNEGO - adaptions for the removed "const" from OIDsMatthias Dieter Wallnöfer2010-12-211-3/+1
| | | | This is needed in order to suppress warnings.
* Keep track of the sparse status of an open file handle. Allows bypass ofJeremy Allison2010-12-215-2/+15
| | | | | | | | strict allocation on sparse files. Files opened as POSIX opens are always sparse. Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Tue Dec 21 04:12:22 CET 2010 on sn-devel-104
* Added call out to a Linux-compatible fallocate() when we need to extend a fileJeremy Allison2010-12-215-3/+86
| | | | | | | allocation extent without changing end-of-file size. Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Tue Dec 21 02:41:24 CET 2010 on sn-devel-104
* CREATE in a compound CREATE/NOTIFY sequence was being passed through ↵Ken Harris2010-12-201-17/+17
| | | | | | | | | | | | set_operation_credits() twice (ultimately perhaps because of bug 7331 involving this compound sequence and the need to be ready for any incoming CANCEL of the NOTIFY). This had the server thinking it had granted more credit than it actually had, which lead to zero-credits being granted in interim NOTIFY responses. Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Mon Dec 20 20:59:55 CET 2010 on sn-devel-104
* From metze's work on sparse attributes. FILE_ATTRIBUTE_SPARSE is valid on ↵Jeremy Allison2010-12-202-3/+3
| | | | | | | get but not on set. Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Mon Dec 20 20:11:22 CET 2010 on sn-devel-104
* s3-printing: fix printer_list_traverse()David Disseldorp2010-12-201-1/+1
| | | | | | | | | The tdb traverse function returns the number of elements traversed, or less than zero on error, printer_list_traverse() is incorrectly checking for non-zero return. Autobuild-User: Andreas Schneider <asn@samba.org> Autobuild-Date: Mon Dec 20 18:44:41 CET 2010 on sn-devel-104
* s3: Remove unused "retry" from cli_start_connectionVolker Lendecke2010-12-204-15/+5
| | | | | Autobuild-User: Volker Lendecke <vlendec@samba.org> Autobuild-Date: Mon Dec 20 17:58:33 CET 2010 on sn-devel-104
* s3: Remove unused "retry" from cli_full_connectionVolker Lendecke2010-12-2016-31/+24
|
* s3: Always retry the DC connection in auth_domainVolker Lendecke2010-12-201-8/+4
| | | | | | | | | | | | The only condition that cli_full_connection marks as non-retryable is the basic name lookup and TCP connect. To me this is pretty fishy. For example if the negprot fails, this is supposed to be more retryable than a NetBIOS name lookup failure? I'd rather think the opposite is true. Jeremy, this is code from 2002, 389a16d9d533. If you have any comments from back then, let me know :-) Volker
* s3: Remove some unused variablesVolker Lendecke2010-12-202-6/+3
|
* s3: "make etags" should not grow TAGS infinitely...Volker Lendecke2010-12-191-0/+1
|
* s3: Fix bug 7066 -- wbcAuthenticateEx gives unix timesVolker Lendecke2010-12-191-3/+5
| | | | | We might eventually want to change this, but right now we get unix times out of the winbind pipe struct
* s3: Use the right uid winbindd_raw_kerberos_login()Volker Lendecke2010-12-191-1/+1
|
* wb_reqtrans is not used in libwbclientVolker Lendecke2010-12-197-7/+514
|
* Move wbc_async.[ch] to its only user: smbtorture3Volker Lendecke2010-12-195-3/+948
|
* libwbclient: Put the wb_reqtrans definitions into wb_reqtrans.hVolker Lendecke2010-12-192-2/+2
|
* s3: wcache_invalidate_samlogon only needs the SIDVolker Lendecke2010-12-193-12/+15
|
* s3: netsamlogon_clear_cached_user only needs the SIDVolker Lendecke2010-12-193-10/+4
|
* s3: Remove two pointless slprintf callsVolker Lendecke2010-12-191-4/+4
|
* s3: FreeBSD has getpeereid(), use itVolker Lendecke2010-12-192-0/+16
|
* s3: Reply correctly to FSCTL_IS_VOLUME_DIRTYVolker Lendecke2010-12-192-0/+10
|
* s3: Fix some nonempty blank linesVolker Lendecke2010-12-191-22/+22
|
* s3: Did I say this module is from hell?Volker Lendecke2010-12-191-1/+1
|
* s3: re-add some debugs to check_reduced_nameVolker Lendecke2010-12-191-0/+2
|
* s3: Fix some typosVolker Lendecke2010-12-194-6/+6
|
* s3: Fix serverid_existsVolker Lendecke2010-12-191-0/+4
| | | | | | | In the cluster case it can happen that a node just died and we did not yet have the time to clean up serverid.tdb. If the corresponding serverid.tdb record that represented a process was migrated away from the dead record, it represents existence of a process where it is already dead.
* Rename vfs operation posix_fallocate to just fallocate and add the ↵Jeremy Allison2010-12-189-42/+65
| | | | | | | | | | | | | | | | | | | | | | vfs_fallocate_mode parameter. It turns out we need the fallocate operations to be able to both allocate and extend filesize, and to allocate and not extend filesize, and posix_fallocate can only do the former. So by defining the vfs op as posix_fallocate we lose the opportunity to use any underlying syscalls (like Linux fallocate) that can do the latter as well. We don't currently use the non-extending filesize call, but now I've changed the vfs op definition we can in the future. For the moment simply map the fallocate op onto posix_fallocate for the VFS_FALLOCATE_EXTEND_SIZE case and return ENOSYS for the VFS_FALLOCATE_KEEP_SIZE case. Jeremy. Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Sat Dec 18 08:59:27 CET 2010 on sn-devel-104
* Move checks inside file_set_sparse() to allow it to be called from anywhere.Jeremy Allison2010-12-172-19/+21
| | | | | Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Fri Dec 17 21:56:38 CET 2010 on sn-devel-104
* file_set_sparse needs to be a handle based call.Jeremy Allison2010-12-173-12/+10
|
* s3:smbd: implement FSCTL_SET_SPARSE more correctlyBjörn Jacke2010-12-171-5/+43
| | | | | | | | | | | | | | this is a port of a patch from metze for 3.3: We don't do the "strict allocation" when the sparse bit isn't set, but that shouldn't matter. We now allow windows applications to set and unset the sparse bit. Note that in order to implement this 100% like described in [MS-FSA], we'd have to change our data model and support the sparse flag per stream.
* Update our attribute flags.Jeremy Allison2010-12-171-1/+6
|
* s3:smbd: add file_set_sparse() functionBjörn Jacke2010-12-172-0/+52
| | | | this is based on a patch for 3.3 from metze
* s3/vfs_gpfs: map SPARSE attribute to/from WINATTRs, tooBjörn Jacke2010-12-171-2/+8
|
* s3: remove set_sparse_flagBjörn Jacke2010-12-171-15/+1
| | | | | | | | we need to determine sparseness from the sparse flag we store not from the allocation size on the POSIX filesystem. This is how Windows works - in the first place sparseness is a file flag, not the allocation state of the file Signed-off-by: Stefan Metzmacher <metze@samba.org>
* s3: add FILE_ATTRIBUTE_SPARSE to get_stat_dos_flagsBjörn Jacke2010-12-171-0/+2
|
generated by cgit (git 2.34.1) at 2025-01-16 16:12:25 +0000