Re: [Samba] Upgrading samba 2.2.8a to 3.6.15 on Solaris 9 -- 3.6.15 brings all inetd services down
Hello, Jordan Verschuer jvsamba...@gmail.com a écrit : Hi samba friends, I'm upgrading our Samba 2.2.8a server to 3.6.15 on a Solaris 9 box, we need to do this as all our latest Mac OS X 10.8 clients cannot map to the 2.2.8a network share, and need the newer Samba (well known issue for mountain lion). My first question would be, why not use the Solaris Samba? IIRC, on S9, it was patched up to 3.something, which could be enough for your needs. I've compiled 3.6.15 and this seemed to go ok, no obvious errors were shown during .configure make and make install, and smbd -V gives output and seems ok, I've updated /etc/inet/inetd.conf and also added the same users to smbpasswd, snip I agree with Marc here: why inetd? It doesn't sound good. Also, I'm maintaining the OpenCSW Samba package for Solaris (http://www.opencsw.org/packages/CSWsamba/). It's currently 3.6.18 for Solaris 10. I've checked that it still builds for Solaris 9 with no trouble. I've put S9 packages there: http://buildfarm.opencsw.org/experimental.html#laurent You're welcome to try them and tell me if they work for you. OpenCSW is focusing on S10 at the moment, but if there is interest in S9, that could be kept running for a while. Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Conversion error: Illegal multibyte sequence
On 10/09/13 00:40, Jeremy Allison wrote: Ok, here is a fix for 3.6.x. Can you test this and see if it fixes the problem ? If so, I'll get this fixed in master and back-ported to all releases. Applies, builds, and runs, and the error message disappeared: all good. Thanks! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Conversion error: Illegal multibyte sequence
On 2013-09-07 2:04 AM, Jeremy Allison wrote: Woo hoo ! I think you've found an oold old bug :-). I told you so from the beginning! Years! ;-) Not a critical one though, it seems. I'll take a look at that asap. Thanks ! I'll be happy to get rid of it too! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Conversion error: Illegal multibyte sequence
On 2013-09-06 10:54 PM, Jeremy Allison wrote:
Either that or add another debug inside
convert_string_internal() to print out
the values of srclen and i_len at various
points and try and determine why it's off
by one.
Well, it was /quite/ further than that.
I think I got it this time, in sources3/smbd/mangle_hash2.c:
/*
* Note that if CH_UNIX is utf8 a string may be 3
* bytes, but this is ok as mb utf8 characters don't
* contain embedded ascii bytes. We are really
checking
* for mb UNIX asian characters like Japanese
(SJIS) here.
* JRA.
*/
DEBUG(3, (DEBUG ++ name, %s\n, name));
if (convert_string(CH_UNIX, CH_UTF16LE,
name, 2, mbc, 2, False) == 2) {
/* Was a good mb string. */
name += 2;
continue;
}
DEBUG(3, (DEBUG -- name, %s\n, name));
Why is the length here hardcoded to 2?
It's past 2am around here, so I could be missing something, time for bed.
Thanks,
Laurent
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Conversion error: Illegal multibyte sequence
On 2013-09-05 11:34 PM, Jeremy Allison wrote:
No, it doesn't make sense. smb_iconv() vectors
through pull and push function pointers that
do the actual conversion - that's where the
errno is coming from. That's why you need
debug statements - you know it's going into
smb_iconv() but you don't know where it's
going from there.
Jeremy.
At least those proved that neither Solaris' nor GNU's iconv were
involved :-)
I tagged all the possibles causes for EILSEQ, so here's the code causing
that issue, in lib/util/charset/iconv.c:
if ((c[0] 0xf0) == 0xe0) {
if (in_left 3 ||
(c[1] 0xc0) != 0x80 ||
(c[2] 0xc0) != 0x80) {
errno = EILSEQ;
DEBUG(3,(DEBUG, %d, %d, %d, %d\n,
in_left, c[0], c[1], c[2]));
goto error;
}
It happens because in_left == 2 when it should be 3:
[2013/09/06 20:59:50.249004, 3] ../lib/util/charset/iconv.c:600(utf8_pull)
DEBUG, 2, 226, 153, 187
[2013/09/06 20:59:50.249056, 3] lib/charcnv.c:161(convert_string_internal)
convert_string_internal: Conversion error: Illegal multibyte
sequence(â99»_Corbeille)
The sequence values are good, as this char is 0xE2 0x99 0xBB in UTF8.
I tried to backtrack the origin of this value, but I got lost after
convert_string_internal() in source3/lib/charcnv.c , where it was
incorrect already.
Is it getting warmer?
Laurent
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Conversion error: Illegal multibyte sequence
On 2013-09-05 10:35 PM, Jeremy Allison wrote: This is the call to smb_iconv() returning an errno of EINVAL. Firstly, add some debug statements inside smb_iconv_open_ex() to find out if we're using the sys_iconv() function (that calls the system iconv) or the internal UFT8 converters. If it's the system iconv then you'll have to look inside that source code. If it's the internal converters add some debug statements inside utf8_pull() and utf8_push() to see where the EINVAL is being returned. This will help track it down for your individual case. I'm not sure I'm still good at adding printf(DEBUG\n) lines around :-) so I tried my hand with dtrace for a start. Here are some examples of what it returns when looking at smb_iconv() while I opened the directory and listed the content: 0 61539 smb_iconv:entry 0 88770 convert_string_talloc:return 0 88786 push_ucs2_talloc:return 0 69264 talloc_tos:entry 0 88535talloc_tos:return 0 69516 push_ucs2_talloc:entry 0 69500 convert_string_talloc:entry 0 69497 lazy_initialize_conv:entry 0 88767 lazy_initialize_conv:return 0 61537 get_iconv_convenience:entry 0 61585 get_iconv_convenience:return 0 69852get_conv_handle:entry 0 89122 get_conv_handle:return 0 82016_talloc_realloc:entry 0 81992 talloc_alloc_pool:entry 0 81991talloc_pool_objectcount:entry 0 101091 talloc_pool_objectcount:return 0 101092 talloc_alloc_pool:return 0 101116 _talloc_realloc:return 0 61539 smb_iconv:entry 0 88770 convert_string_talloc:return 0 88786 push_ucs2_talloc:return 0 69821 strupper_w:entry 0 69840 toupper_w:entry 0 69846 toupper_m:entry 0 89116 toupper_m:return 0 89110 toupper_w:return 0 69840 toupper_w:entry 0 69846 toupper_m:entry 0 75259toupper:entry 0 94407 toupper:return 0 89116 toupper_m:return 0 89110 toupper_w:return 0 69840 toupper_w:entry 0 69846 toupper_m:entry 0 75259toupper:entry 0 94407 toupper:return 0 89116 toupper_m:return 0 89110 toupper_w:return 0 89091strupper_w:return 0 69499 convert_string:entry 0 69497 lazy_initialize_conv:entry 0 88767 lazy_initialize_conv:return 0 61537 get_iconv_convenience:entry 0 61585 get_iconv_convenience:return 0 69852get_conv_handle:entry 0 89122 get_conv_handle:return Does it make sense? There are some longer examples, but the only function call containing iconv is get_iconv_convenience(). Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Conversion error: Illegal multibyte sequence
Hello list, I've noticed this problem for a few years now, I think. I see it popped out now and then in discussions. But they always end before a solution is given. So let's try one more time :-) I have plenty of UTF-8 named files and directories. It's UTF-8 all round, I don't use anything else, so I have no doubt the byte sequences are correct in the filesystem (I happen to have accented Latin chars, Chinese, Japanese, and some non-letters chars, so it'd show up really quick if there was an issue there :-) I see those kind of errors in the logs, here about a directory named ♻_Corbeille. Please note: those lines are a direct copy of the log. So yes, the ♻ character is indeed correct in the two first entries (including the first conversion error line), but improperly logged as an invalid byte sequence in the two latter entries, and those two have different lengths. [2013/09/05 20:43:50.280597, 3] smbd/dir.c:1046(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found ./♻_Corbeille fname=♻_Corbeille (♻_Corbeille) [2013/09/05 20:43:50.280641, 3] lib/charcnv.c:161(convert_string_internal) convert_string_internal: Conversion error: Illegal multibyte sequence(♻_Corbeille) [2013/09/05 20:43:50.280679, 3] lib/charcnv.c:140(convert_string_internal) convert_string_internal: Conversion error: Incomplete multibyte sequence(��_Corbeille) [2013/09/05 20:43:50.280715, 3] lib/charcnv.c:140(convert_string_internal) convert_string_internal: Conversion error: Incomplete multibyte sequence(�_Corbeille) It does not prevent using the directory, and it displays properly on Windows clients. So the issue is merely an annoying flood of logs. The system is Solaris 10, running Samba 3.6.18 linked against GNU libiconv 1.14. The charsets are defined like this in the configuration: dos charset = cp850 unix charset = UTF8 display charset = UTF8 So, any definitive fix for that? Thanks! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Configuring pam_smbpass with Solaris
Continuing my investigation: I used tdbdump to compare the content of passdb.tdb, and the content there seems wrong. Here it is the line created with smbclient (it's consistent if I replay it with the same password, only the %\97 changes, yay for unsalted passwords) data(206) = \00\00\00\00\7F\A9T|\7F\A9T|\00\00\00\00%\97\D6Q\00\00\00\00\7F\A9T|\09\00\00\00user\00\09\00\00\00SERVER\00\01\00\00\00\00\01\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\01\00\00\00\00\01\00\00\00\00\01\00\00\00\00\01\00\00\00\00\EA\03\00\00\01\02\00\00\10\00\00\00bJ\ACA7\95\CD\C1\FF\176_\AF\1F\FE\89\10\00\00\00;\1BG\E4.\04c'n=\EDl\EF4\9F\93\00\00\00\00\10\00\00\00\A8\00\15\00\00\00 \00\00\00\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\EC\04\00\00 The same line after modification via pam_smbpass, the content is noticeably different, whatever is stored there is not the same password: data(206) = \00\00\00\00\7F\A9T|\7F\A9T|\00\00\00\00\9D\97\D6Q\00\00\00\00\FF\FF\FF\7F\09\00\00\00user\00\09\00\00\00SERVER\00\01\00\00\00\00\01\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\01\00\00\00\00\01\00\00\00\00\01\00\00\00\00\01\00\00\00\00\EA\03\00\00\01\02\00\00\10\00\00\00bJ\ACA7\95\CD\C1\FF\176_\AF\1F\FE\89\10\00\00\00\1B\A3Z\A9\D1\9D\B8\E7\0C9\AE\C1\BC\F2BB\00\00\00\00\10\00\00\00\A8\00\15\00\00\00 \00\00\00\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\FF\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\EC\04\00\00 If nobody can shed a light on this, I'll file a bug, the code is 10 year old, it might have got some bitrot. Thanks, Laurent On 04/07/13 15:00, Laurent Blume wrote: Hello all. I'm trying to configure pam_smbpass for Samba 3.6.16 on Solaris 10. However, I'm getting a strange result: instead of sync'ing the password, it *removes* it. That is not quite what I expect... I have this line in /etc/pam.conf: other password required pam_smbpass_csw.so debug use_authtok try_first_pass nonull To start the test, I make sure passwords are already in sync: passwd user smbpasswd user Then I check it works: su - user smbclient server\\share Both succeed, so so far, all good. Now I try to change it using passwd, first as user: $ passwd Enter existing login password: New Password: Permission denied The logs show: Jul 4 14:50:17 server passwd[12830]: [ID 871885 auth.notice] (pam_smbpass) failed auth request by user for service passwd as user Jul 4 14:50:17 server passwd[12830]: [ID 507756 auth.notice] (pam_smbpass) failed auth request by user for service passwd as user(-18956203) Jul 4 14:50:17 server passwd[12830]: [ID 965784 auth.notice] (pam_smbpass) 1 authentication failure from user for service passwd as user(1000) If I try as root: # passwd user New Password: Re-enter new Password: passwd: password successfully changed for user su works with the new password: su - user Samba fails: $ smbclient server\\share Enter user's password: session setup failed: NT_STATUS_LOGON_FAILURE However, the same works with an empty password (press enter at the password request). Not good. The logs show: Jul 4 14:54:10 server passwd[12912]: [ID 632017 auth.notice] (pam_smbpass) password for (user/1000) changed by (root/0) Any idea what I did wrong? Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Configuring pam_smbpass with Solaris
Hello all. I'm trying to configure pam_smbpass for Samba 3.6.16 on Solaris 10. However, I'm getting a strange result: instead of sync'ing the password, it *removes* it. That is not quite what I expect... I have this line in /etc/pam.conf: other password required pam_smbpass_csw.so debug use_authtok try_first_pass nonull To start the test, I make sure passwords are already in sync: passwd user smbpasswd user Then I check it works: su - user smbclient server\\share Both succeed, so so far, all good. Now I try to change it using passwd, first as user: $ passwd Enter existing login password: New Password: Permission denied The logs show: Jul 4 14:50:17 server passwd[12830]: [ID 871885 auth.notice] (pam_smbpass) failed auth request by user for service passwd as user Jul 4 14:50:17 server passwd[12830]: [ID 507756 auth.notice] (pam_smbpass) failed auth request by user for service passwd as user(-18956203) Jul 4 14:50:17 server passwd[12830]: [ID 965784 auth.notice] (pam_smbpass) 1 authentication failure from user for service passwd as user(1000) If I try as root: # passwd user New Password: Re-enter new Password: passwd: password successfully changed for user su works with the new password: su - user Samba fails: $ smbclient server\\share Enter user's password: session setup failed: NT_STATUS_LOGON_FAILURE However, the same works with an empty password (press enter at the password request). Not good. The logs show: Jul 4 14:54:10 server passwd[12912]: [ID 632017 auth.notice] (pam_smbpass) password for (user/1000) changed by (root/0) Any idea what I did wrong? Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer drivers installation: files are not deleted
Le 21.03.2011 16:55, Thomas Stegbauer a écrit : hi laurent, i found the error. with all the tests there was set: use client driver = yes :( now i can upload drivers and register drivers by apw and cupsaddsmb best regards thank you very for your assistance Heh, you're welcome, but I didn't do much, I didn't think about that at all. So thanks for the feedback, that piece of info can be useful in the future! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer drivers installation: files are not deleted
Le 15.03.2011 13:09, Thomas Stegbauer a écrit : i cant imagin, where this permission is set. 1. i apply the driver via apw from windows xp32 as root 2. net rpc rights list root Enter root's password: SePrintOperatorPrivilege 3. i can was able to upload the driver for HP Color LaserJet PS but i cant upload Kyocera 5350 UPD or KX driver also not OK ES7411 PS (v1.0.0) You need to check there is nothing wrong on the print share, like subdirectories with the wrong permissions or something like that. Remember you need both the rights to manipulate printers and to write files in the right place. Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer drivers installation: files are not deleted
Le 13.03.2011 22:37, Thomas Stegbauer a écrit : i have a similar problem, here. When trying to add a new printer via apw from a winXP32, the driver files get copied over to print$ on the ubuntu 10.04 Server (Samba 3.4.7) afterwards it says Permission denied And the driver get not registered. I think thatś most probably a permission issue on the server. Does the user you connect with have printer administrator privilege? Ie, member of the printadm group or similar? Where do you geht the filenames, the drivers needs? as i cant use rpcclient to register the drivers from commandline. I followed the documentation on that: I install them on a clean test system (win7 x64), then extract the list of files and the files themselves using rpcclient. That part works. Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printer drivers installation: files are not deleted
Hello all, I'm running Samba 3.5.5 on Debian 5, and following the documentation as closely as I can to install drivers using rpcclient. I first install the driver on a Windows 7 x65 workstation, then use rpcclient/smbclient to fetch the files. I then use smbclient to put those on the print$ share of the Samba server. So far, so good. Then I use rpcclient to add those files, and that appears to work: rpcclient -U DOMAIN\\LOGIN%PASSWD -c adddriver \Windows x64\ \HP Universal Printing PS (v5.1):PSCRIPT5.dll:hpcu104s.ppd:hpmdp104.dll:PSCRIPT.HLP:NULL:RAW:hpcdmc64.dll,hpbcfgre.dll,hpcpu104.CFG,hpcui104.dll,hpcpe104.dll,hpcur104.dll,hpcpn104.dll,hpcsr104.dll,hpcst104.dll,hpcev104.dll,hpcu104s.hpx,hpcsc104.dtd,hpchl104.cab,hpzfn104.ntf,hpcu104.dem,hpmux104.dll,hpmur104.dll,hpmpm081.dll,hpmpw081.dll,hpmsn104.dll,hpmsl104.dll,hpcsat20.dll,hpcu104v.ini,hpcu104s.xml,hpcls104.dll,hpcss104.dll,FxCompChannel_x64.dll,cioum.dll,cioum64.msi,hpcpn104.dll,ps5ui.dll,pscript.ntf,ps_schm.gdl,hppdcompio.dll,hpcc6104.dll,HPDRVJCT.dll,hpfxcomw.dll,hpsysobj.dll\ HAPI64-CC Printer Driver HP Universal Printing PS (v5.1) successfully installed. But actually, things are going wrong: it does create the 3/ subdirectory, it does populate it with the files in print$/x64, but those files are kept there, not deleted as they should. If I then try to delete it, there's something similar: rpcclient $ deldriverex HP Universal Printing PS (v5.1) Driver HP Universal Printing PS (v5.1) and files removed for arch [Windows x64] (version: 3). But none of the files are really removed, they're still all there. And so far, no error message that I can see. Can anybody shed some light? TIA! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] How to define an UID range for BUILTIN accounts
Hi all, I've got a Debian Lenny Samba server on which I'm trying to define UID ranges for the handful of domains it connects to. I'm using the RID backend successfully for the domains: I can switch to it successfully from the old self defined UID's, and then getent passwd/group show the new expected ones. However, the BUILTIN accounts also seen getent passwd don't change. I've been trying to define them in the same way as the domains, and some other things I've googled, but nothing. With most of my tries, after removing the Samba cache and tdb files, the BUILTIN accounts simply disappear and don't come back. Any idea or pointer on how to define those BUILTIN UID's successfully? TIA, Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] smbstatus not working as non-root user
Hi all, I haven't found any clear information yet about that problem. I'm trying the following workaround, however. If anybody believes it's not the Right Way To Do It, please do not hesitate to tell me. What I need: regular users to be able to use smbstatus, because they need to know what files are in use What I did: I changed the group of smbstatus to smbnull, put its setid bit on, changed the group and permissions on the locks directory and all the .lck files to be writable by smbstatus. This makes smbstatus work for regular users as it did before the upgrade. Is it a security issue? Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbstatus not working as non-root user
After some more investigation, I managed to find out that it's because this Samba is using lock files in /var/opt/samba/locks, such as connections.tdb.lck, which regular users can't access. What I don't get, is how to disable their use? On another box, using a slightly older version of HP CIFS server (based on Samba 2.2.8), there are no such files. There are some difference in the lock configuration beetween the two systems, but from their descriptions, there is no obvious one. Still looking for any clue on how to fix this... Laurent Laurent Blume wrote: This is for HP CIFS Server A.01.11.03 / Samba 2.2.12, on HP-UX 11.0. I've got a problem with smbstatus: if run as root, it displays everything as expected. If run as a regular user, it displays only the following: $ smbstatus tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file /var/opt/samba/locks/connections.tdb not initialized. This is normal if an SMB client has never connected to your server. Of course, plenty of Windows clients have been connecting to that box. The permissions on the tdb file are the same as the ones on another box, where it works. And it used to work on that same system, after it was installed. So I'm not sure where to look... There is nothing in the log.smbd file since Samba was started, 10 days ago. Any idea? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbstatus not working as non-root user
Hello all, This is for HP CIFS Server A.01.11.03 / Samba 2.2.12, on HP-UX 11.0. I've got a problem with smbstatus: if run as root, it displays everything as expected. If run as a regular user, it displays only the following: $ smbstatus tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file /var/opt/samba/locks/connections.tdb not initialized. This is normal if an SMB client has never connected to your server. Of course, plenty of Windows clients have been connecting to that box. The permissions on the tdb file are the same as the ones on another box, where it works. And it used to work on that same system, after it was installed. So I'm not sure where to look... There is nothing in the log.smbd file since Samba was started, 10 days ago. Any idea? TIA, Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mapping Windows groups to Unix ones on Samba 2.2
eric roseme wrote: Is this Samba Opensource 2.2.12 or HP CIFS Server 2.2.12 (A.01.11.03)? groupname map is not a real Samba feature, I believe. See Jerry's response at: http://marc.theaimsgroup.com/?l=sambam=104302387220719w=2 HP CIFS Server at 2.2 was not enabled for winbind, thus there is no way to do what you want. If you go to HP CIFS Server A.02.01 (3.0.7 and 3.0.8) you get winbind and net groupmap - not the same syntax as below but you can map AD groups. Thanks to all that answered. I guess I'm out of luck on this one, since this is HP CIFS Server, and 2.2.12 (A.01.11.03) is the most recent version for HP-UX 11.00 (compiling is not an option, though I wish it were). So I'll do that when it's upgraded to 11.11. At least I won't waste my time trying :-) Thanks a lot, Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Cannot delete files: the mounted file system does not support extended attributes
Laurent Blume wrote: When trying to delete files on a Samba share, I get the message Cannot delete file: The mounted file system does not support extended attributes. [snip] To answer myself: From what I understood, it seems this is a Samba bug in version 2.0.x, that was triggered by a recent Windows patch. There was a slight change in Windows behaviour when deleting files. As for me, the problem was fixed by going to HP's package of Samba 2.2.12, which is the most recent for HP-UX 11.00 (HP-UX CIFS Server http://www.hp.com/products1/unix/operating/hpuxcifs9000/index.html) After that change, the system went out of available file locks. Somehow, more seem to be used after that update (I'm not sure why, and it's not a bug AFAIK). We had to increase HP-UX's NFLOCK value, and it's now running fine. HTH, Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Mapping Windows groups to Unix ones on Samba 2.2
Hi all, Now that I've got Samba 2.2.12 running correctly on that HP-UX box, I need to allow write access to a given AD domain group. What is the right way to do it on Samba 2.2? I added a group.map file in smb.conf, and a line inside that said: unixgroup = AD Domain Group Then in smb.conf, I put in [global]: groupname map = /etc/opt/samba/group.map And in the correct share, I put the following: valid users = @unixgroup read list = @unixgroup write list = @unixgroup I did not restart Samba, but from what I understand, the config file was automatically reloaded. SWAT did display the new values. The users' login were already mapped in the user.map file, and that works fine. However, after doing that, the persons in the AD group still had no access. Putting the unix users directly in the unix group does work, but of course, is a much less clean solution. Any hint or pointer to documentation? I was only able to find some for the 3.0 version, which is quite different for that :-/ TIA! Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Cannoi delete files: the mounted file system does not support extended attributes
Hi all, I'm having what seems like a strange problem, I hope I'm not missing something obvious, any help will be appreciated. When trying to delete files on a Samba share, I get the message Cannot delete file: The mounted file system does not support extended attributes. What is strange is that it depends on weird conditions: in one directory, if I create a file (right click - New text document) with a name more than 16 characters, it can't be deleted, with that message. If it is less that 16 characters (renamed or created that way), it can be deleted. I tried created a serie of nested test directories, with a single a file in them. This one can be deleted: \\machine\STAT\test\test\a This one cannot: \\machine\STAT\test\test\test\a Even stranger: if I reight-click on those files, and go in the Security tab, their permissions look identical (even the special ones). But if I click on Everyone/Modify for the file that I just couldn't delete, I now can delete it. If I immediately recreate the same file, it can be deleted. If I wait a few minutes, then it can't be deleted, unless I check the security permission again. Now, the catch: this is Samba 2.0.9, running on HP-UX 11i. The clients are Windows 2000 SP4 w/ patches. I know this is an old version of Samba, but it's been working, litterally, for years, and it's not easy to update it. The problem only appeared last week. If someone has a workaround for that version of Samba, it'll be welcome. If is a known bug or limitation of that version, it'll be welcome as well to have it pointed out. I had a look at the change log without success. Thanks in advance for any help, Laurent -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
