similar to: Mangled Names, Directory Listing and Access Failure, Unix-to-Unix

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,

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 >

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:

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

We are currently using Samba V. 3.0.21b. My question is that we are running samba on our UNIX server (Solaris 9) where we have directories that look similar to the following: A.L. E.A. T.A. You can either view the directories as they are suppose to appear, except the users can't access the data. OR The directories appear as mangled names but the users have no idea which directory they

Hi all, We are building a new system which is going to use ext3 FS. We would like to know more about the behavior of ext3 in the case of failure. But before I procede, I would like to share more information about our future system. * Our application always does an fsync on files * When symbolic links (more specifically fast symlink) are created, the host directory is also fsync'ed. * Our

CentOS Errata and Bugfix Advisory 2012:1124 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1124.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1249e7bc487ca8897a0b107ba545cc0568364e666d9173efec0b8e83c5dbd36a gvfs-1.4.3-15.el6.i686.rpm 126056c90870f293f88509ea5836a6bfe3f8af7c5937b463e2abd71d5d5d458e

CentOS Errata and Bugfix Advisory 2014:0584 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0584.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 32fc8248d488ac2fd3ca91836af5b429f1d251b0a0b3a885bd241c5519613db7 gvfs-1.4.3-16.el6_5.i686.rpm 0bcd4bed50c6d03ad6ebd20dd182ddbcbed126f305f291e1f5f77f0f6fe7e169

CentOS Errata and Bugfix Advisory 2015:0237 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0237.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7dcaac6f48780a284f3719ff9fc56bde1cc28ad20077cbcf66f1bd8716635dc0 gvfs-1.4.3-20.el6.i686.rpm 996d087774c30b30ebf9924653298e5dd1c34281713b7b151aea6bc4f44298d2

On Fri, Jan 5, 2018 at 6:37 AM, lingpanda101 <lingpanda101 at gmail.com> wrote: > I would assume you would need to use 'rm -r' to remove a directory and > it's contents. That doesn't work and the man page doesn't list flags for any commands, plus it looks like rm is strictly for files not for directories. smb: \noperms\> rm -r test1 NT_STATUS_NO_SUCH_FILE

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On Thu, Feb 8, 2024 at 1:18?PM Chris Rapier <rapier at psc.edu> wrote: > > I know that there are some methods to use federated identities (e.g. > OAuth2) with SSH authentication but, from what I've seen, they largely > seem clunky and require users to interact with web browsers to get one > time tokens. Which is sort of acceptable for occasional logins but > doesn't

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When