similar to: language charset configuration problem！

Hi fellows. I'm new to the list and hope I'll have a nice time here. one of my servers running samba+ldap is not working properly. the setup is: Debian 5 fileserver:/etc/samba#smbd --version Version 3.0.24 fileserver:/etc/samba# slapd -V @(#) $OpenLDAP: slapd 2.3.30 (Oct 5 2008 22:08:58) $

Oi F?bio. Pelo IP tamb?m n?o acessa. A minha suspeita de que era um problema ligado a interface est? errada. Aleat?riamente usu?rios nas duas interfaces perdem o acesso. Ainda assim, somente usu?rios com Windows XP tem esse problema. Vou testar suas indica??es. F?bio Rabelo wrote: > > > 2010/3/23 Leonardo Carneiro - Veltrac <lscarneiro at veltrac.com.br > <mailto:lscarneiro

hi everyone i have to create a share that will allow a group of users just to create files, not modifying or even reading these files. plus, i need to allow just xml files to be created. is that possible? tks in advance -- *Leonardo de Souza Carneiro* *Veltrac - Tecnologia em Log?stica.* lscarneiro at veltrac.com.br <mailto:lscarneiro at veltrac.com.br> http://www.veltrac.com.br

Hello everyone. I was having a problem with my Samba PDC with LDAP backend. The command 'net getlocalsid' gaves me the message "Got too many (2) domain info entries for domain [domain]". I logged im my ldap server, and saw that i have the following entries: dn: sambaDomainName=DOMINIO,dc=dominio,dc=com,dc=br sambaDomainName: DOMINIO sambaSID:

hello guys, after a power cut in this weekend, the filesystem of the machine running samba+ldap currupted. i did a fsck and every other services in the machine are running fine now, but i cannot access the samba shares and cannot join/log in the domain. in the windows machines it just show a message "the network path is not found". i'll add my smb.conf tks in advance --

Hi John. It worked well just before the upgrade. I'm not saying that this is correct, but is the reason why users aren't accessing? Also, should'n this give some specific error in the logs? Tks in advance. John H Terpstra wrote: > On 03/23/2010 02:35 PM, Leonardo Carneiro - Veltrac wrote: > >> Hi Dale and others. I had already checked the release notes. Only users

Hi everyone, I'm having trouble in deploying by group sambaLogonScript. My scripts consist only im mapping network folders. I'm using Samba 3.4.7. Is there a way to debug this? The logs does not show anything about the logon scripts. All my users are set with "%G.bat" in the ldap backend, but the vast majority of the users are not running the scripts, or running partially.

Thanks for the update. I believe I've fixed a part of the problem you have reported, the crash while entering Chinese characters to the console (e.g. via Pinyin, the error message about invalid multibyte character in mbcs_get_next). The fix is in R-devel 74693 - Windows function ReadConsoleInputA no longer works with multibyte characters (it is not documented, probably a Windows bug,

Hi Tomas, Sorry for the delayed response. I have tested the problem on the latest R-devel build (2018-04-27 r74651), and it still exists. RGui is always fine with Chinese characters, but some IDEs rely on the CLI version of R (e.g. Visual Studio Code with R plugin). >Your example print("ABC\u4f60\u597dDEF") is printing two Chinese characters, right? Yes. U+4F60, U+597D or C4E3,

Thank you for the report and initial debugging. I am not sure what is going wrong, we may have to rely on your help to debug this (I do not have a system to reproduce on). A user-targeted advice would be to use RGui (Rgui.exe). Does the problem also exist in R-devel? https://cran.r-project.org/bin/windows/base/rdevel.html Your example? print("ABC\u4f60\u597dDEF") is printing two

Hi Yihui, list.files() returns file names converted to native encoding by Windows, so one needs to use only characters representable in current native encoding for file names. If one wants to be safe, it makes sense to be much stricter than that (only ASCII, and only a subset of it, there is a number of recommendations that can be found online). Using more than that is asking for trouble.

I use R 2.3.0 under windows. > Sys.getlocale() [1] "LC_COLLATE=Chinese_People's Republic of China.936;LC_CTYPE=Chinese_People's Republic of China.936;LC_MONETARY=Chinese_People's Republic of China.936;LC_NUMERIC=C;LC_TIME=Chinese_People's Republic of China.936" > localeToCharset() [1] "CP936" Now I want to use JGR,which uses UTF-8 encoding. So when I use

i mount a windows share like this: mount -t smbfs -o iocharset=gb2312,codepage=936,username=administrator //192.168.10.27/cvs /mnt/windows and try to copy file from /mnt/windows to my local disk. but if came to file with chinese name it always told me "cp: can't creat normal file , invalid argument." by the way i can see the file name (in chinese), and here is my locale: LANG=zh_CN

Hi folks, I am trying to access the shared folders on a Windows XP PC from a Linux (FC5) PC using smbclient. Linux config info: $ locale LANG=en_US.UTF-8 $ rpm -q samba samba-3.0.24-6.fc5 smb.conf: [global] dos charset = CP936 <--- Simplified Chinese unix charset = UTF-8 display charset = LOCALE Now, here is the problem:

Hi Tomas, Sorry for the false alarm! I did some further testing, and you were right. There was no regression. I suspected it was a regression because the user who reported the issue said his code worked in R 3.6 but not 4.0. I should have tested it more carefully by myself. After I tested it again with the German locale and Chinese locale, respectively, I found that the code worked for both

On 04/03/16 09:58, Volker Lendecke wrote: > On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: >> On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: >>> OK, here is the output: >> Can you try the attached (UNTESTED!) patch? >> >> Thanks, > Gna, should have at least compiled it.... > > New patch :-) > > Volker > Sorry

Regarding yesterday's message about repeated "signal 11" errors in 2.2.12, I was able to capture a backtrace. #0 0x401543ae in waitpid () from /lib/tls/libc.so.6 #1 0x400e9d12 in system () from /lib/tls/libc.so.6 #2 0x0815ea98 in smb_panic () #3 0x0814d885 in fault_report () #4 0x0814d8e2 in sig_fault () #5 <signal handler called> #6 ldap_free_urllist (ludlist=0x185) at

Hi I am trying to upgrde ?out openldap ver 2.3 ?to the lastest version 2.4, howevre there is no rpm avaibale for 2.4 so i decide to create my own for centOS flavour 5.2 here is the ?part look of my spec file openldap.spec Summary: openldap Installer Name: openldap Version: 2.4 Release: 1 Vendor: net Solutions License: Commercial Group: ms6 BuildRoot: /usr/src/redhat/BUILD/openldap Provides:

I tried to compile various version (2.5, 2.6pre1, 3.0alpha17, HEAD,...) of Samba with LDAP support ('configure --with-ldapsam'). During configuration and 'make' process all seams fine, but after I installed ('make install') and ran, Samba complains something similar to "Unknown option: ldap server" and some other similar error messages. It seams that LDAP

I have a samba server that was updated to samba v3.0.22 and is not working. It is a fileserver for the network, it's a member of the ADS and it was working perfectly up until saturday. It doesn't panic when I change security = ADS to security = server, unfortunately I need ADS auth. I've tried to down grade back to 3.0.14a with no luck, It looks like it might be samba's