I might have unwittingly made the impression that the problem only came with
3.0.20.
The same problem was present in 3.0.14 as well as 3.0.4. It's a very
intermittent
problem which has been haunting me for months now.
Then it's not this particular bug.
No, it ain't. There's a dangling
On Fri, Oct 14, 2005 at 07:09:57PM +0100, Dragan Krnic wrote:
I might have unwittingly made the impression that the problem only came
with 3.0.20.
The same problem was present in 3.0.14 as well as 3.0.4. It's a very
intermittent
problem which has been haunting me for months now.
Hi,
Where is this patch, I would like to update my server to 3.0.20a, but if
there are some problem with Access DB Lock Files, I prefer to patche
samba before compiling.
---
Stéphane PURNELLE [EMAIL PROTECTED]
Service Informatique
I have an intermittent problem with dangling MS Access DB lock files.
In a productive environment with N batch queus (each on a separate
Windows XP Professional) a scheduler PC dispatches the work load to
a free queue by means of modifying a simple MS Access DB file called
PRIM.mdb, which
On Tue, Oct 11, 2005 at 08:03:10PM +0100, Dragan Krnic wrote:
I might have unwittingly made the impression that the problem only came
with 3.0.20. The same problem was present in 3.0.14 as well as 3.0.4.
It's a very intermittent problem which has been haunting me for months now.
Then it's
I have an intermittent problem with dangling MS Access DB lock files.
In a productive environment with N batch queus (each on a separate
Windows XP Professional) a scheduler PC dispatches the work load to
a free queue by means of modifying a simple MS Access DB file
called PRIM.mdb, which
On Mon, Oct 10, 2005 at 04:21:15PM +0100, Dragan Krnic wrote:
I have an intermittent problem with dangling MS Access DB lock files.
In a productive environment with N batch queus (each on a separate
Windows XP Professional) a scheduler PC dispatches the work load to
a free queue by means of
