summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* use string_set() instead of string_init()Andrew Tridgell2000-01-163-41/+31
| | | | bug pointed out by Richard
* added code to allow traversal of the byte range lock databaseAndrew Tridgell2000-01-163-4/+72
| | | | this is used with "smbstatus -B" to dump the lock list
* fixed a formatting errorAndrew Tridgell2000-01-161-1/+1
|
* make string_init() staticAndrew Tridgell2000-01-162-2/+2
| | | | use string_set() instead, to avoid the bug Richard discovered
* make a br_off a SMB_BIG_UINTAndrew Tridgell2000-01-161-1/+1
|
* useable_space does not include the alignment offset calculations.Jeremy Allison2000-01-141-1/+8
| | | | | Bugfix from Marc_Jacobsen@hp.com. Jeremy.
* HP changes for registry querying.Jeremy Allison2000-01-141-1/+9
| | | | Jeremy.
* Added HP change.Jeremy Allison2000-01-141-53/+54
| | | | Jeremy.
* casts and defines to make solaris happyAndrew Tridgell2000-01-143-3/+7
|
* damn, Solaris already has a "enum lock_type"Andrew Tridgell2000-01-145-15/+15
| | | | changed it to "enum brl_type"
* we now pass all byte range locking testsAndrew Tridgell2000-01-146-25/+94
| | | | | the last piece was to use a smb timeout slightly larger than the locking timeout in bloking locks to prevent a race
* Updated docs for "inherit permissions" fix.Jeremy Allison2000-01-141-3/+48
| | | | Jeremy.
* Added "inherit permissions" patch.Jeremy Allison2000-01-1410-33/+122
| | | | | Fixed locking bug found by Andrew. Jeremy.
* some more work on the byte range lockingAndrew Tridgell2000-01-143-22/+31
| | | | | | | | note the ugly global_smbpid - I hope that won't bethere for long, I just didn't want to do two lots of major surgery at the one time. Using global_smbpid avoids the big change of getting rid of our inbuf/outbuf interface to reply routines. I'll do that once the locking stuff passes all tests.
* greatly expanded the lock4 locking test. we now pass all but one testAndrew Tridgell2000-01-131-45/+93
| | | | - that should be fixed soon.
* changes to reflect the new syntax of the locking calls.Andrew Tridgell2000-01-133-20/+19
|
* the bulk of the new byte range locking coodeAndrew Tridgell2000-01-132-45/+296
| | | | it doesn't map to posix locks yet, that will come later.
* the lock routines now take a enumerated type for read/write locks, andAndrew Tridgell2000-01-131-4/+4
| | | | | | | | we now don't pass the lock type at all for unlocks. I was surprised to discover that NT totally ignores the lock type in unlocks. It unlocks a matching write lock if there is one, otherwise it removes the first matching read lock.
* added Enosuchshare and a lock_type enumAndrew Tridgell2000-01-131-0/+4
|
* new prototypesAndrew Tridgell2000-01-131-5/+22
|
* defined br_off as a type for byte range offsets. For now I've set itAndrew Tridgell2000-01-131-0/+3
| | | | | as SMB_OFF_T, we need to do some autoconf changes to generate a 64 bit int whenever possible (eg. long long on 32 bit i386)
* added locking/brlock.c, a byte range locking systemAndrew Tridgell2000-01-131-1/+1
|
* Added missing #ifdef for WITH_UTMP.Jeremy Allison2000-01-131-0/+2
| | | | Jeremy.
* Added utmp fix from David Lee <T.D.Lee@durham.ac.uk>.Jeremy Allison2000-01-129-576/+951
| | | | Jeremy.
* Use slprintf not snprintf.Jeremy Allison2000-01-121-1/+1
| | | | Jeremy.
* Fix problems with broken libc fvct returns.Jeremy Allison2000-01-121-1/+8
| | | | Jeremy.
* Fixed pointer arithmetic found by IRIX compiler.Jeremy Allison2000-01-111-1/+1
| | | | Jeremy.
* Fixed bug in unix_mask_match() that caused veto files not to work.Jeremy Allison2000-01-111-31/+9
| | | | Jeremy.
* modified smbd/msrpc credential transfer system. user session keyLuke Leighton2000-01-113-1/+32
| | | | | | | | | is *missing* from samba cvs main, therefore it is set to all zeros. this will cause, amongst other things, administrator-changing-user-passwords, and setting up new accounts, to fail, as the user's password can only be decoded with the session key (in this case, the administrator's usr sess key). it's never a perfect world, is it?
* I'm currently designing a new locking system (using a tdb database!)Andrew Tridgell2000-01-103-27/+140
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that will make us match NT semantics exactly and do away with the horrible fd multiplexing in smbd. this is some diag stuff to get me started. - added the ability to do read or write locks in clientgen.c - added a LOCK4 test to smbtorture. This produces a report on the server and its locking capabilities. For example, NT4 gives this: the same process cannot set overlapping write locks the same process can set overlapping read locks a different connection cannot set overlapping write locks a different connection can set overlapping read locks a different pid cannot set overlapping write locks a different pid can set overlapping read locks the same process can set the same read lock twice the same process cannot set the same write lock twice the same process cannot override a read lock with a write lock the same process can override a write lock with a read lock a different pid cannot override a write lock with a read lock the same process cannot coalesce read locks this server does strict write locking this server does strict read locking whereas Samba currently gives this: the same process can set overlapping write locks the same process can set overlapping read locks a different connection cannot set overlapping write locks a different connection can set overlapping read locks a different pid can set overlapping write locks a different pid can set overlapping read locks the same process can set the same read lock twice the same process can set the same write lock twice the same process can override a read lock with a write lock the same process can override a write lock with a read lock a different pid can override a write lock with a read lock the same process can coalesce read locks this server does strict write locking this server does strict read locking win95 gives this - I don't understand why! the same process cannot set overlapping write locks the same process cannot set overlapping read locks a different connection cannot set overlapping write locks a different connection cannot set overlapping read locks a different pid cannot set overlapping write locks a different pid cannot set overlapping read locks the same process cannot set the same read lock twice the same process cannot set the same write lock twice the same process cannot override a read lock with a write lock the same process cannot override a write lock with a read lock a different pid cannot override a write lock with a read lock the same process cannot coalesce read locks this server does strict write locking this server does strict read locking
* don't treat a packet as a oplock break unless it is a request, not aAndrew Tridgell2000-01-101-1/+2
| | | | reply!
* extent smbtorture to test with both an exe file and a dat fileAndrew Tridgell2000-01-081-37/+43
|
* fix a error in access_table revealed by the new deny test in smbtorture. We ↵Andrew Tridgell2000-01-081-3/+5
| | | | now exactly match NT for normal files. We still don't match for *.exe files though
* cli_open() wasn't handling DENY_FCB or O_WRONLY correctly.Andrew Tridgell2000-01-085-10/+9
| | | | | | After fixing that I needed to use O_RDWR instead of O_WRONLY in several places to avoid the silly bug in MS servers that doesn't allow getattrE on a file opened with O_WRONLY
* added a DENY test that tests deny mode handling. It produces a matrixAndrew Tridgell2000-01-081-2/+86
| | | | | of 324 lines (6*6*3*3) of all possible deny mode behaviour. This allows us to compare with NT. We currently don't match :)
* improved the error checkingAndrew Tridgell2000-01-083-27/+86
|
* Fix minor typos in the yodl for smb.conf.5 and fix minor English problems :-)Richard Sharpe2000-01-081-2/+2
|
* smbd/mangle.cJeremy Allison2000-01-085-7/+15
| | | | | | smbd/negprot.c: Tidyup of static initializers. smbd/server.c: Fix -l option. Jeremy.
* Fixed deny mode bug :Jeremy Allison2000-01-081-9/+9
| | | | | | | : If a file is resident on NT and the first user opens it read/write with DENY_READ then a subsequent : attempt by a second user (running under Windows 95) to open it read/write DENY_NONE fails. : Under samba 2.0.5a the second open succeeds but the file is write only. Jeremy.
* fixed a commentAndrew Tridgell2000-01-071-1/+1
|
* the -i options are gone from nmbd and smbd - use the smb.confAndrew Tridgell2000-01-072-18/+2
| | | | | | | parameter "netbios scope" instead -i is still available in the command line utils, as these may be used to contact another scope
* netbios scope is a DOS_STRINGAndrew Tridgell2000-01-071-1/+1
|
* always restart nmbd and smbd when asked, even if they appear not to beAndrew Tridgell2000-01-071-4/+2
| | | | responding. They could be stuck
* remove scope parameter here tooAndrew Tridgell2000-01-071-3/+3
|
* added "netbios scope" docsAndrew Tridgell2000-01-071-0/+8
|
* this looks like a big commit, but it isn't really :)Andrew Tridgell2000-01-0732-121/+90
| | | | | | | | This fixes our netbios scope handling. We now have a 'netbios scope' option in smb.conf and the scope option is removed from make_nmb_name() this was prompted by a bug in our PDC finding code where it didn't append the scope to the query of the '*' name.
* don't use strcpyAndrew Tridgell2000-01-071-1/+2
|
* don't require readlineAndrew Tridgell2000-01-071-1/+13
|
* - patch from Rusty to neaten up the code a bitAndrew Tridgell2000-01-072-232/+109
| | | | - fixed a race condition in tdb_open()
* Removed unneeded #define.Jeremy Allison2000-01-061-2/+0
| | | | Jeremy.
generated by cgit (git 2.34.1) at 2025-09-28 05:51:25 +0000