Displaying 20 results from an estimated 9000 matches similar to: "lock/shared file problem"
2000 Sep 01
0
btrieve - a neverending story
Hello out there,
recently I posted a trouble report about my Samba/btrieve
experience.
I have encountered the worst case scenario - corrupt databases...
I had a brief correspondency with Dave Collier-Brown (whose book
on Samba can't be praised enough) about this, in which he told me
that working under the same login a) network-wide and b)
application-wide could lead to such corrpution.
2020 Aug 23
2
MultiDatabase shard count limitations
Olly Betts <olly at survex.com> wrote:
> On Fri, Aug 21, 2020 at 09:06:59AM +0000, Eric Wong wrote:
> > Going back to the "prioritizing aggregated DBs" thread from
> > February 2020, I've got 390 Xapian shards for 130 public inboxes
> > I want to search against(*). There's more on the horizon (we're
> > expecting tens of thousands of public
2014 Aug 27
2
Dos Btrieve Windows 98 and Samba 4.0
?We are trying to migrate a Dos based btrieve application from Windows NT
to Samba 4?.1.6-Ubuntu. Running one client works, running more that one
client do not work.
I searched Google and there are many historic pages about issues related to
the btrieve / Samba combination.
Are there stable solutions of this issue?
Kind Regards
Hendre
2000 Aug 28
1
btrieve applications
Hello fellow samba users,
I have installed quite a couple of samba fileservers so far.
There are exactly two installations which give me real hard time,
and both have to do with Win9x clients running applications based
on ... *sigh* btrieve.
What I do server-sided is switch on opportunistic locking (level2
oplocks = yes).
Without this, the applications don't run at all, at least not on
more
2013 Jul 14
0
[LLVMdev] [PATCH] x86/asm: avoid mnemonics without type suffix
(resent without HTML)
On 07/14/2013 05:56 AM, Ramkumar Ramachandra wrote:
> 1c54d77 (x86: partial unification of asm-x86/bitops.h, 2008-01-30)
> changed a bunch of btrl/btsl instructions to btr/bts, with the following
> justification:
>
> The inline assembly for the bit operations has been changed to remove
> explicit sizing hints on the instructions, so the assembler will
2003 Sep 25
1
data lost in cv.tree?
Greetings -- I'm programming a data mining system
in R for protein structural data. As a seasoned
Perl and Python and Ada and ML, et al., programmer,
I am severely befuddled by the environment problem,
where data is not found in a 3rd level nested
function. I did peruse the parent frame not on the
search path idea, and came up with a hack which
kinda works, also below with the code which
2013 Jul 15
1
[LLVMdev] [PATCH] x86/asm: avoid mnemonics without type suffix
On 07/14/2013 12:23 PM, Jeremy Fitzhardinge wrote:
> (resent without HTML)
>
> On 07/14/2013 05:56 AM, Ramkumar Ramachandra wrote:
>> 1c54d77 (x86: partial unification of asm-x86/bitops.h, 2008-01-30)
>> changed a bunch of btrl/btsl instructions to btr/bts, with the following
>> justification:
>>
>> The inline assembly for the bit operations has been
1999 Sep 25
2
file locking with win apps
Hello there,
I have a serious file locking problem with samba on a RH6 based Linux
machine.
>From the exported share a database files are being requested. Problem
is, only one client can access these - and even only one client can
initialize the database query engine, which is btrieve 6.15 workstation
engine.
The same problem affects .doc files. If one client has an open document,
the file is
2013 Jul 14
2
[LLVMdev] [PATCH] x86/asm: avoid mnemonics without type suffix
Linus Torvalds wrote:
>> btrl $1, 0
>> btr $1, 0
>> btsl $1, 0
>> bts $1, 0
>
> What the heck is that supposed to show?
I was trying to show a reduced case where gas doesn't complain, but
llvm-mc does. Try compiling this with llvm-mc, and you'll get:
.text
btrl $1, 0
in.s:2:1: error: ambiguous instructions require an
2010 Oct 08
0
Wine release 1.2.1
The Wine maintenance release 1.2.1 is now available.
What's new in this release (see below for details):
- Translation updates.
- Various bug fixes.
The source is available from the following locations:
http://ibiblio.org/pub/linux/system/emulators/wine/wine-1.2.1.tar.bz2
http://prdownloads.sourceforge.net/wine/wine-1.2.1.tar.bz2
Binary packages for various distributions will be
2013 Jul 14
9
[LLVMdev] [PATCH] x86/asm: avoid mnemonics without type suffix
1c54d77 (x86: partial unification of asm-x86/bitops.h, 2008-01-30)
changed a bunch of btrl/btsl instructions to btr/bts, with the following
justification:
The inline assembly for the bit operations has been changed to remove
explicit sizing hints on the instructions, so the assembler will pick
the appropriate instruction forms depending on the architecture and
the context.
Unfortunately,
2013 Jul 10
0
[LLVMdev] [PATCH] x86: disambiguate unqualified btr, bts
Also, please elaborate on why this is a good change. Because gas accepts it isn’t sufficient reason in and of itself.
-Jim
On Jul 10, 2013, at 1:18 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
> On Wed, Jul 10, 2013 at 12:29 PM, Ramkumar Ramachandra
> <artagnon at gmail.com> wrote:
>> The instructions btr and bts are perfectly valid, and have existed since
2013 Jul 11
0
[LLVMdev] [PATCH] x86: disambiguate unqualified btr, bts
Jim Grosbach wrote:
> That does raise a clarifying question here. Is the code you’re interested in
> using Intel or AT&T syntax?
>
> Also note that the question isn’t whether we should support the btr/bts
> instructions. We absolutely must (and do). The question is whether we are
> properly handling the un-suffixed mnemonic form of the assembly syntax.
>
> Perhaps you
2013 Jul 11
0
[LLVMdev] [PATCH] x86: disambiguate unqualified btr, bts
http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/arch/x86/include/asm/bitops.h#L68
Here is one example that I found. Are the inline assembly arguments
ambiguous in size?
-Jevin
Sent from my mobile device. Typos are par for the course.
On Jul 10, 2013, at 5:47 PM, Jim Grosbach <grosbach at apple.com> wrote:
On Jul 10, 2013, at 2:30 PM, Eric Christopher <echristo at
2013 Jul 10
3
[LLVMdev] [PATCH] x86: disambiguate unqualified btr, bts
On Wed, Jul 10, 2013 at 12:29 PM, Ramkumar Ramachandra
<artagnon at gmail.com> wrote:
> The instructions btr and bts are perfectly valid, and have existed since
> Intel 386. GNU as supports them fine. Unfortunately, LLVM does not
> support them, and barfs with:
>
> error: ambiguous instructions require an explicit suffix
>
> Fix this problem by disambiguating it
2012 Feb 26
0
"device delete" kills contents
Hallo, linux-btrfs,
I''ve (once again) tried "add" and "delete".
First, with 3 devices (partitions):
mkfs.btrfs -d raid0 -m raid1 /dev/sdk1 /dev/sdl1 /dev/sdm1
Mounted (to /mnt/btr), filled with about 100 GByte data.
Then
btrfs device add /dev/sdj1 /mnt/btr
results in
# show
Label: none uuid: 6bd7d4df-e133-47d1-9b19-3c7565428770
Total devices 4 FS bytes
2003 Mar 27
2
Problem with xcopy /d & samba
A problem has arisen with the way samba handles file
creation dates compared to NT/win2k, which prevents
xcopy /d from working correctly.
On NT/Win2k, files copied from another NT machine using
xcopy end up with the modified dates equal to the original
modified date of the file, and the created and accessed
dates become the date of the xcopy operation.
On Samba, files copied from an NT
2010 Dec 03
0
Wine release 1.2.2
The Wine maintenance release 1.2.2 is now available.
What's new in this release (see below for details):
- Support for animated cursors.
- Translation updates.
- Various bug fixes.
The source is available from the following locations:
http://ibiblio.org/pub/linux/system/emulators/wine/wine-1.2.2.tar.bz2
http://prdownloads.sourceforge.net/wine/wine-1.2.2.tar.bz2
Binary packages
2013 Jul 14
0
[LLVMdev] [PATCH] x86: disambiguate unqualified btr, bts
Stephen Checkoway wrote:
> [...]
Thanks for the absolutely splendid analysis!
> For the memory, immediate form without the suffix, it seems like the options are
> 1. If the immediate value is in [0,15], use btsl/btrl since it saves a byte, otherwise error;
> 2. Follow both gas's behavior and the Solaris assembler manual Jim Grosbach linked to which stated that unsuffixed
2013 Jul 10
0
[LLVMdev] [PATCH] x86: disambiguate unqualified btr, bts
On Wed, Jul 10, 2013 at 2:08 PM, Ramkumar Ramachandra
<artagnon at gmail.com> wrote:
> Jim Grosbach wrote:
>> To say that another way, is the assembler correctly diagnosing a previously
>> unnoticed problem in the project source code, or is the assembler not
>> behaving correctly according the the documented Intel assembly mnemonics?
>
> Where are the authoritative