Re: [Samba] Solved: problems with special characters
I've just recordnized that the two options 'character set' and 'client code page' were exchanged. Using unix charset = ISO8859-1 dos charset = 850 and all worked fine! After all this probs occures with redhat v8.0 not with the older v7.3 maybe also prior versions. So this behavior not only depends on samba... bastian Hello NG, maybe anybody can help me... I got trouble with the german special characters. After upgrading to v3.0.11 any special character will be displayed as an underscore. Also the modification of the smb.conf couldn't fix the problems: character set = ISO8859-1 client code page = 850 Since v3 these options are out of date, but I used them anyway. After switching back to v3.0.3 all the characters will be displayed correctly. But I recordnized another problem: The characters won't be correctly displayed on the machine itself (using ls). So I guess it's a main problem, but I'm not sure. I set my locale to de_DE and if i touched a file with those characters in the filename it will be shown as it should. Even via samba. So, anybody experience with setting the right character encoding? Oh yes - I'm using redhat v8. Thanks, bastian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] problems with special characters
Hello NG, maybe anybody can help me... I got trouble with the german special characters. After upgrading to v3.0.11 any special character will be displayed as an underscore. Also the modification of the smb.conf couldn't fix the problems: character set = ISO8859-1 client code page = 850 Since v3 these options are out of date, but I used them anyway. After switching back to v3.0.3 all the characters will be displayed correctly. But I recordnized another problem: The characters won't be correctly displayed on the machine itself (using ls). So I guess it's a main problem, but I'm not sure. I set my locale to de_DE and if i touched a file with those characters in the filename it will be shown as it should. Even via samba. So, anybody experience with setting the right character encoding? Oh yes - I'm using redhat v8. Thanks, bastian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] compile samba v3.0.9 vfs-errors
Hello NG, found a thread with almost my current problem. There wasn't any solution out there. Maybe anything has changed? I want install samba v3.0.9 on an old rh linux v7.1. Currently there's no chance to update the core system. But while compiling it breaks with many vfs-errors as shown below: ..SNIP.. modules/vfs_shadow_copy.po(.text+0x6e2): undefined reference to `debug_add_class' modules/vfs_shadow_copy.po(.text+0x700): undefined reference to `DEBUGLEVEL_CLASS' modules/vfs_shadow_copy.po(.text+0x70e): undefined reference to `DEBUGLEVEL_CLASS_ISSET' modules/vfs_shadow_copy.po(.text+0x73d): undefined reference to `dbghdr' modules/vfs_shadow_copy.po(.text+0x764): undefined reference to `DEBUGLEVEL_CLASS' modules/vfs_shadow_copy.po(.text+0x772): undefined reference to `DEBUGLEVEL_CLASS_ISSET' modules/vfs_shadow_copy.po(.text+0x799): undefined reference to `dbghdr' modules/vfs_shadow_copy.po(.text+0x7c0): undefined reference to `dbgtext' Compiling modules/CP850.c with -fPIC Building plugin bin/CP850.so modules/CP850.po: In function `init_module': modules/CP850.po(.text+0x1c5): undefined reference to `smb_register_charset' Compiling modules/CP437.c with -fPIC Building plugin bin/CP437.so modules/CP437.po: In function `init_module': modules/CP437.po(.text+0x1c5): undefined reference to `smb_register_charset' ..END.. Here are the first lines of the posting found in http://lists.samba.org/archive/samba/2004-October/094787.html : Hi all, sorry for the long posting. Samba 2.2.x is outdated. Trying to switch to 3.0.7 with no success. The vfs layer is one of my current problems. Googled some time for an solution for this: [2004/10/21 20:04:00, 0] smbd/server.c:main(760) smbd version 3.0.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2004/10/21 22:12:07, 0] smbd/server.c:main(760) smbd version 3.0.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2004/10/21 22:12:12, 0] smbd/vfs.c:vfs_init_custom(256) Can't find a vfs module [vscan-oav] The module is there, configuration in smb.conf is correct, but there were many compile errors with _any_ vfs module. Must be a link failure, but how can I resolve this? [public] comment = public directory on test2 path = /public public = yes create mode = 0777 directory mode = 0777 browseable = yes writeable = yes level2 oplocks = no blocking locks = no oplocks = no hide files = /desktop.ini/Thumbs.db/ vfs object = vscan-oav vscan-oav: config-file = /etc/samba/vscan-oav.conf Here are the compile errors with the normal vfs modules from samba tarball: ... Thanks for your help, bastian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] compile samba v3.0.9 vfs-errors
Hello Tom,
thanks for your patch. But I get trouble patching my configure. Is the
patch available for download -
maybe it's bogus due to copy'n'paste or what else. Any other hint?
Thanks,
bastian
[EMAIL PROTECTED] source]# patch configure conf.patch
patching file configure
Hunk #1 FAILED at 3174.
1 out of 1 hunk FAILED -- saving rejects to file configure.rej
[EMAIL PROTECTED] source]# cat configure.rej
***
*** 3174,3190
if test $ac_cv_prog_gnu_ld = yes; then
-ac_cv_gnu_ld_version=`$LD -v 2/dev/null | head -1`
-echo $as_me:$LINENO: checking GNU ld release date 5
- echo $ECHO_N checking GNU ld release date... $ECHO_C 6
-ac_cv_gnu_ld_date=`echo
$ac_cv_gnu_ld_version | sed -n
's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'`
-echo $as_me:$LINENO: result:
${ac_cv_gnu_ld_date} 5
- echo ${ECHO_T}${ac_cv_gnu_ld_date} 6
-if test $ac_cv_gnu_ld_date -lt 20030217; then
- ac_cv_gnu_ld_no_default_allow_shlib_undefined=yes
-fi
fi
-
echo $as_me:$LINENO: checking for library containing strerror 5
echo $ECHO_N checking for library containing strerror... $ECHO_C 6
--- 3174,3205
if test $ac_cv_prog_gnu_ld = yes; then
+ ac_cv_gnu_ld_version=`$LD -v 2/dev/null | head -1`
+ if `echo $ac_cv_gnu_ld_version | grep -q -E
^.*[2-9][0-9][0-9][0-9][-]*[01][0-9][-]*[0-3][0-9].*$`; then
+ echo $as_me:$LINENO: checking GNU ld release date 5
+ echo $ECHO_N checking GNU ld release date... $ECHO_C 6
+ ac_cv_gnu_ld_date=`echo $ac_cv_gnu_ld_version | sed -n
's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'`
+ echo $as_me:$LINENO: result: ${ac_cv_gnu_ld_date} 5
+ echo ${ECHO_T}${ac_cv_gnu_ld_date} 6
+ if test $ac_cv_gnu_ld_date -lt 20030217; then
+ ac_cv_gnu_ld_no_default_allow_shlib_undefined=yes
+ fi
+ else
+ echo $as_me:$LINENO: checking GNU ld release version 5
+ echo $ECHO_N checking GNU ld release version... $ECHO_C 6
+ ac_cv_gnu_ld_vernr=`echo $ac_cv_gnu_ld_version | sed -n
's,^.*\([1-9][0-9]*\.[0-9][0-9]*\).*$,\1,p'`
+ echo $as_me:$LINENO: result: ${ac_cv_gnu_ld_vernr} 5
+ echo ${ECHO_T}${ac_cv_gnu_ld_vernr} 6
+ ac_cv_gnu_ld_vernr_major=`echo $ac_cv_gnu_ld_vernr | cut -d '.' -f
1`
+ echo $as_me:$LINENO: result: ac_cv_gnu_ld_vernr_major
${ac_cv_gnu_ld_vernr_major} 5
+ ac_cv_gnu_ld_vernr_minor=`echo $ac_cv_gnu_ld_vernr | cut -d '.' -f
2`
+ echo $as_me:$LINENO: result: ac_cv_gnu_ld_vernr_minor
${ac_cv_gnu_ld_vernr_minor} 5
+ if test $ac_cv_gnu_ld_vernr_major -lt 2 || test
$ac_cv_gnu_ld_vernr_minor -lt 14; then
+ ac_cv_gnu_ld_no_default_allow_shlib_undefined=yes
+ echo $as_me:$LINENO: result:
ac_cv_gnu_ld_no_default_allow_shlib_undefined
${ac_cv_gnu_ld_no_default_allow_shlib_undefined} 5
+ fi
+ fi
fi
echo $as_me:$LINENO: checking for library containing strerror 5
echo $ECHO_N checking for library containing strerror... $ECHO_C 6
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] joining v2x member to v3x pdc
Hello NG, I want to add a samba v2.2.12 system as a member server to my domain managed by a samba v3.0.3 pdc. Is this possible? It's not as easy as joining a samba v3.0.x system. My problem is, that I can't update the system to v3 right now. The users are all stored in a ldap-directory which I'm able to access onto the system using the 'id'-cmd. The system has also got its ldap-record. If I want to receive the SID it's the same result as joining the domain with -j: [EMAIL PROTECTED] smbpasswd -S DOMAIN fetch_domain_sid: unable to connect to SMB server on machine MY-PDC. Error was : SUCCESS - 0. Failed to get domain SID for DOMAIN. Here's the global section of my smb.conf: workgroup = DOMAIN server string = Member os level = 16 create mask = 0775 force create mode = 0775 directory mask = 0775 force directory mode = 0775 security = domain password server = * # ldap settings ldap suffix = dc=DOMAIN,dc=DE ldap admin dn = cn=manager,dc=DOMAIN,dc=DE ldap port = 389 ldap server = 192.186.0.1 ldap ssl = Off encrypt passwords = true If security = domain and encrypt password = true is set, no user can connect to the system (tested with smbclient): session setup failed: NT_STATUS_LOGON_FAILURE If these values are unset, only the ldap-users will get this error. The local users are able to connect. I already added this member as a workstation onto the pdc via smbldap-useradd -w member and ran the smbclient -w secret successfully. Where can I find the solution, the online samba-howtos deal only with v3. Thanks, bastian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] compiling samba v3x with sysconfdir
Hello, I just compiled the latest samba src. with the sysconfdir option as seen below: ./configure --prefix=/usr/local/samba/3.0.9 --sysconfdir=/etc/samba After installing it and configuring the smb.conf in /etc/samba I ran testparm. It failed, cause the smb.conf wasn't found: ... Load smb config files from /usr/local/samba/3.0.9/lib/smb.conf params.c:OpenConfFile() - Unable to open configuration file /usr/local/samba/3.0.9/lib/smb.conf: No such file or directory Error loading services. ... I know, that if I specifiy the location of the smb.conf, it would run correctly (testparm /etc/samba/smb.conf). Also starting Samba will fail due to this error. After using the -s options samba will start... My Question: Is the sysconfdir deprecated? Or is there any other solution to set the smb.conf location? I don't want to work with links or hide my smb.conf somewhere deep inside... Thanks, bastian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
