similar to: Mangled Names

I am using a recent version of Samba mounted through GVFS. If I configure with the option "mangled names" unspecified, I am able to access everything fine, but files with ':' or '?' get mangled to the point of unusability. If I specify "mangled names = no", I see everything fine with the reserved characters displayed properly, but I am unable to list or access

Hi all, while working with Netbench I've discovered that mangled directory names clash rather frequently with Samba 2.2.4: If I take an NT box, open the cmd prompt and make the following directories on a Samba share, client100 and client121, both mangle to CLIEN~GH. If I create directories client100 through client130 I see 11 clashes altogether: CLIEN~GH: client100 client121 CLIEN~MF:

Is there a different behaviour to mangled names in 3.0.x over 2.2.8a? When we double-click on the following reg file: m:\xpapps\hvcc\reg\visstud\hkcuvccomb.reg We get a registry editor error: Cannot import m:\xpapps\hvcc\reg\visstud\HSCNGB~G.REG: Error opening file. There may be a disk or file system error. when I set "mangled names = no" is behaves as expected. This behaviour is

I just took on a new client who is having a curious problem with mangled names. Here's the history as I understand it: Originally they were on an NT server and there was no issue. My predecessor moved them to a samba server running on gentwo. I do not know what version of samba or how he moved the data, but when he did so, any files and folders with more than 8 characters started

On Feb 15, 2011, at 3:10 AM, Patrick Simmons wrote: > I have encountered a need for manually generating the mangled name of an > arbitrary C++ function. The only way I currently know how to do this is > to generate a dummy C++ source file, compile it, and look at the > output. This approach is so ugly that I would like for it never to see > the light of day. The c++filt tool

> > ---------- Forwarded message ---------- > Date: Thu, 23 May 2002 11:18:36 +0200 > From: Pascal Schelcher <pascal.schelcher@free.fr> > To: samba@lists.samba.org > Subject: [Samba] Mangled Names of Long File Name with 2.2.4 > > Hello, > > I have got samba-2.2.4 installed. > The Documentation of Samba says that the probability of a clash of mangled >

I have encountered a need for manually generating the mangled name of an arbitrary C++ function. The only way I currently know how to do this is to generate a dummy C++ source file, compile it, and look at the output. This approach is so ugly that I would like for it never to see the light of day. The c++filt tool generates demangled C++ names given the mangled ones, which is the opposite

Hello, after upgrade Samba from 1.9.17p4 to 2.0.7 I have problems with name mangling. Changed parameters in SMB.CONF for new version: oplocks = no client code page = 852 local master = yes all other parameters are the same. I one directory I have these files: 0011_BAR_ISSUEAGRES.CSV 0011_MIR_STKGEN.CSV 0011_OLO_ISSUEMPSPEC.CSV 0011_RET_ISSUEAGRES.CSV When I look to these files (DIR /X) from

Hi, On Wed, Dec 10, 2014 at 11:10:36AM +0100, Markus Doits wrote: > I have a unix server (arch linux) with samba 4.1.14. The share has files > inside which where created directly on the server. Linux and OSX > (10.10.1) clients should access the share and store files. > > When I mount this samba share into the osx client (10.10.1), files > created directly on the server with

Hello, I have a unix server (arch linux) with samba 4.1.14. The share has files inside which where created directly on the server. Linux and OSX (10.10.1) clients should access the share and store files. When I mount this samba share into the osx client (10.10.1), files created directly on the server with special names like `File with "quotes"` are displayed mangled (`C7XSWH~V`) on the

Hi Ralph, Thanks, it works as expected with 4.2.0rc2! I simply followed the manual and added this to the share's config: vfs objects = catia fruit streams_xattr fruit:resource = file fruit:metadata = netatalk fruit:locking = netatalk fruit:encoding = native Thanks for your help. Markus On 10.12.14 12:06, Ralph B?hme wrote: > Hi, > > On Wed, Dec 10, 2014 at 11:10:36AM +0100,

Hello, In samba 2.x, I had no problem with DOS name mangling. For example, if a file named 0613abcdefg.txt, it will be mangled as 0613ab~1.txt. It is very easy to know which file it is. But now in Samba 3, the mangled name is very strange, "0AFADF~1.txt", I have no clue to know which file it is. But I didn't see any configuration parameters to deal with this problem, anyone can

Hello, after upgrade Samba from 1.9.17p4 to 2.0.7. I have problems with name mangling. In one directory I have these files (only): 0011_BAR_ISSUEAGRES.CSV 0011_MIR_STKGEN.CSV 0011_OLO_ISSUEMPSPEC.CSV 0011_RET_ISSUEAGRES.CSV When I look at these files (DIR /X) from Windows95 or WindowsNT Workstation 4.0 clients I can see this: 0011_~%Y.CSV 0011_BAR_ISSUEAGRES.CSV 0011_~$%.CSV

Hello samba-list-readers, I have 2 files with long filenames on a samba-server (V2.04b). The filenames are xxxxx_APB.h and xxxxx_SEL.h For some reason the first part of the name has to be xxxxx_ In the file-property-sheet of windows-explorer the MS-DOS-name of BOTH files is XXXXX_~5X.H. That means to me, that the hash-algorithm, which generates the MS-DOS-name is to weak and produced a

Hi folks, I am having a problem rsyncing files with accents in the names. I've seen similar problems reported a few times before in the archives but they didn't seem to be referring to exactly the same problem as what I have, and I'm not good enough at Linux to solve my problem by generalising from the information there: sorry. Anyway, my specific details are this. I am running rsync

Hi All, I am doing some work to extend the target library information and ran across some function names in the old simplify-libcalls pass that are prefixed with \1. For example: \1__isoc99_scanf \1__isoc99_sscan \1fopen64 \1fseeko64 \1fstat64 \1fstatvfs64 Where do these \1 names come from? What target triples are they expected on? -- Meador Inge CodeSourcery / Mentor Embedded

> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: > > >> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> >> >> >> On 19.01.2018 04:35, Adam Weinberger wrote: >>> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. >>> It seems to be happening when I use

I''m having problems with filenames being mangled when uploaded - usually truncated either upto or after some problematic character. Here''s an example: Filename in filesystem: s+o~1@#%^&*()_-=[]{};:''".txt uploadedfile#original_filename: s+o~1@#%^&*()_-=[]{} Is this a rails/cgi.rb issue or a browser one? I note that gmail''s "attach file"

Op 1/21/2018 om 4:34 PM schreef Stephan Bosch: > Op 1/20/2018 om 11:01 PM schreef Adam Weinberger: >>> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: >>> >>> >>>> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>>> >>>> >>>> >>>> On 19.01.2018 04:35,

HTML attachment scrubbed and removed -------------- next part -------------- A non-text attachment was scrubbed... Name: klaus.troeger.vcf Type: text/x-vcard Size: 331 bytes Desc: Card for Klaus Troeger Url : http://lists.samba.org/archive/samba/attachments/20000630/dedb54e2/klaus.troeger.vcf