On Wed, 19 Mar 2003, Nir Soffer wrote:
I can't reproduce this at all on a recent (CVS) build
of SAMBA_3_0. Can you give me more details on *exactly*
how you reproduce it please ?
What I did was simply do, on the unix side:
mkdir b1996
cd b1996
touch nirtest123456
touch nirtest12345
-Original Message-
From: Richard Sharpe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 10:43 AM
To: Nir Soffer
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: rd /s, can't find the file specified (internal
reference b1996)
On Wed, 19 Mar 2003, Nir Soffer
-Original Message-
From: Richard Sharpe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 10:43 AM
To: Nir Soffer
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: rd /s, can't find the file specified (internal
reference b1996)
On Wed, 19 Mar 2003, Nir Soffer
On Wed, 19 Mar 2003, Nir Soffer wrote:
On Wed, 19 Mar 2003, Nir Soffer wrote:
I can't reproduce this at all on a recent (CVS) build
of SAMBA_3_0. Can you give me more details on *exactly*
how you reproduce it please ?
What I did was simply do, on the unix side:
On Wed, 19 Mar 2003, Nir Soffer wrote:
On Wed, 19 Mar 2003, Nir Soffer wrote:
I can't reproduce this at all on a recent (CVS) build
of SAMBA_3_0. Can you give me more details on *exactly*
how you reproduce it please ?
What I did was simply do, on the unix side:
On Wed, Mar 19, 2003 at 10:28:59AM +0200, Nir Soffer wrote:
Okay. I was being stupid. Very very stupid, and I apologize. Turns out mangled
filenames was disabled. But is this the expected error when manged filenames are
disabled?
Obviously :-). I'll take a look at what the semantics should
On Sun, Mar 16, 2003 at 06:47:44PM +0200, Nir Soffer wrote:
Following up to myself, reproducing this is apparently even simpler than I thought -
simply do a:
touch nir test test
and try to delete it from a DOS command line. It will fail.
nirtest123456 fails as well, but nirtest12345
I've tried this also, and I can't reproduce it on HEAD, 3.0alpha-17 or
3.0alpha-19
-Marc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2003 6:44 PM
To: Nir Soffer
Cc: [EMAIL PROTECTED]
Subject: Re: rd /s, can't find
? / Yes, true weeping is yet to come
-- Nick Cave and the Bad Seeds, The Weeping Song
-Original Message-
From: Richard Sharpe [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 9:23 AM
To: Nir Soffer
Cc: [EMAIL PROTECTED]
Subject: RE: rd /s, can't find the file
On Mon, 17 Mar 2003, Nir Soffer wrote:
Enjoy.
OK, now that I have looked at both traces in more detail,
here is what is
happening:
The bad trace, perhaps the one from UNIX, is returning
exactly the same
short name for each of those files, 0123456789AB.
The client tries to
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 4:44 AM
To: Nir Soffer
Cc: [EMAIL PROTECTED]
Subject: Re: rd /s, can't find the file specified (internal
reference b1996)
On Sun, Mar 16, 2003 at 06:47:44PM +0200, Nir Soffer
Soffer
Cc: [EMAIL PROTECTED]
Subject: RE: rd /s, can't find the file specified (internal
reference b1996)
On Sun, 16 Mar 2003, Nir Soffer wrote:
Following up to myself, reproducing this is apparently even simpler
than I thought - simply do a:
touch nir test test
and try
Following up to myself, reproducing this is apparently even simpler than I thought -
simply do a:
touch nir test test
and try to delete it from a DOS command line. It will fail.
nirtest123456 fails as well, but nirtest12345 so it seems to filename size
related. 13 characters won't work and
On Sun, 16 Mar 2003, Nir Soffer wrote:
Following up to myself, reproducing this is apparently even simpler
than I thought - simply do a:
touch nir test test
and try to delete it from a DOS command line. It will fail.
nirtest123456 fails as well, but nirtest12345 so it seems to
14 matches
Mail list logo
