[Samba] Does tdb can store incorrect encoding symbols?

Volker Lendecke Volker.Lendecke at SerNet.DE
Tue Jan 12 14:14:10 MST 2010

On Tue, Jan 12, 2010 at 11:21:18PM +0300, Сергей wrote:
> Case 2.
> A many years ago I had used Samba with one-byte encoding - the KOI-8R - for presenting russian letters. At that time I created first groups, which haved the russian descriptions.
> Later I move to new version of Samba (and OS so) which supports multi-byte encoding. Today samba's logs analysis show me that the description of those first groups is still one-byte encoding!!! 
> At this part of log http://www.acc.tula.ru/~acc107_3/samba/miscoding/case%202.txt a group 'tst-users' have one-byte encoded description. 'ugs' group haves multi-byte encoding (UTF-8) description.
> Because of one-byte encoded description I get error:
> lib/charcnv.c:convert_string_internal(263)
>   convert_string_internal: Conversion error: Illegal multibyte sequence(лПОЖЕТЕОГЙС)
> librpc/ndr/ndr.c:ndr_push_error(493)
>   ndr_push_error(5): Bad char conversion
> rpc_server/srv_pipe.c:api_rpcTNP(2381)
>   api_rpcTNP: samr: SAMR_QUERYDISPLAYINFO2 failed.
> and empty domain group list.
> Fragment of smb.conf
>         dos charset = 866
>         unix charset = utf-8
>         preserve case = yes
>         short preserve case = yes
>         default case = lower
>         case sensitive = auto
> So, I have two questions:
> 1. How to select one-byte encoded descriptions?

Does "unix charset = KOI-8R" help?

> 2. How to convert it to multi-byte encoding?

Within a tdb? Probably just with pdbedit or "net groupmap"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/samba/attachments/20100112/bfd6aee2/attachment.pgp>

More information about the samba mailing list