Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
James Kosin a écrit : From: Cedric Delfosse [mailto:[EMAIL PROTECTED] Sent: Fri 6/23/2006 03:05 AM To: James Kosin Hello, The SAMBA-VSCAN module I use has been compiled against the installed SAMBA version. AFAIR SAMBA doesn't load a VFS module that has a mismatched version. Ok, what kernel version? 'uname -r' samba version? 'smbd -V' # uname -r 2.4.27-2-686-smp # smbd -V Version 3.0.21c-Debian Basically, the system is a Debian Sarge, with a backport of Samba 3.0.21c. Regards, -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
James Kosin a écrit : Jeremy Allison wrote: - there is only one application (a CAO drawing tool) for which only some files causes a violation error, even with kernel oplocks = No. Looks like there was an interaction with the SAMBA-VSCAN module (version 0.3.6b) somewhere, as disabling this module removed the violation error. Interesting. If that the latest version of vscan ? Jeremy. It is the latest, although 0.4.0 has been released as a snapshot. I think maybe his problem is he may be using an older compiled version of SAMBA-VSCAN that has not been compiled for the new version of SAMBA installed. I do know the source for vscan requires integration with the correct version of samba; otherwise, unpredictable results happen. Hello, The SAMBA-VSCAN module I use has been compiled against the installed SAMBA version. AFAIR SAMBA doesn't load a VFS module that has a mismatched version. -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
Jeremy Allison a écrit : On Thu, Jun 22, 2006 at 04:09:31PM +0200, Cedric Delfosse wrote: I'm answering to myself. My problems are fixed: - kernel oplocks = No has fixed the violation error for some applications. Why the oplocks are refused is unknown, but for now I don't need them ; Yes, that would definately fix any kernel oplock problems (turning them off). - there is only one application (a CAO drawing tool) for which only some files causes a violation error, even with kernel oplocks = No. Looks like there was an interaction with the SAMBA-VSCAN module (version 0.3.6b) somewhere, as disabling this module removed the violation error. Interesting. If that the latest version of vscan ? According to [1], yes. My customer is going to send me the CAO application and some files to test. A nice new feature for samba-vscan would be to a have a list of users/machines to exclude from being scanned :) [1] http://sourceforge.net/project/showfiles.php?group_id=10590 -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
Cedric Delfosse a écrit : Cedric Delfosse a écrit : Jeremy Allison a écrit : On Thu, Jun 15, 2006 at 11:39:21AM +0200, Cedric Delfosse wrote: (Samba 3.0.21c / kernel 2.4.27 / Debian Sarge) Hello, One of my user open a file (located on a SAMBA server) in its application, and when he tries to save it, he gets a "share violation" error. (other people have this problem too). This error happens since I upgraded the SAMBA server from 3.0.14a to 3.0.21c. smbstatus for this file: 32613DENY_WRITE 0x20089 RDONLY NONE /home/user/J84400os-V8 Thu Jun 15 10:46:05 2006 Samba log when trying to save the file: [2006/06/15 10:50:44, 2] smbd/open.c:open_file(350) user1 opened file J84400os-V8 read=Yes write=No (numopen=12) [2006/06/15 10:50:44, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(161) linux_set_kernel_oplock: Refused oplock on file J84400os-V8, fd = 33, dev = b, inode = 2621998. (Resource temporarily unavailable) You can turn off kernel oplocks with "kernel oplocks = no" in your smb.conf. You might want to try 3.0.22 (or the 3.0.23RC2) instead as we made changes in this area. I will try 3.0.22 and tell you if this fix my problem. Setting "kernel oplocks = No" didn't fix the problem too: I now get a "Access Denied" error. Here is now what I have into the samba log (the user opens the file and tries to save it): Hello I'm answering to myself. My problems are fixed: - kernel oplocks = No has fixed the violation error for some applications. Why the oplocks are refused is unknown, but for now I don't need them ; - there is only one application (a CAO drawing tool) for which only some files causes a violation error, even with kernel oplocks = No. Looks like there was an interaction with the SAMBA-VSCAN module (version 0.3.6b) somewhere, as disabling this module removed the violation error. Thanks a lot for your help. Regards, -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
Le mercredi 21 juin 2006 à 18:43 +0200, Cedric Delfosse a écrit : [...] > Btw, I have found a way to reproduce the the kernel oplocks bug with > SAMBA 3.0.21C and SAMBA 3.0.22. Looks like this is related to NFS. But I > don't get the "share violation" error box from Windows. > > Here is the howto: > - On SAMBA server, in the home of a user, create a symbolic link to a > NFS imported directory. For example, if "cedric" is my username, I have: > > # ls /home/cedric -l > total 64 > drwx--S--- 2 cedric Domain Users 34 2006-06-16 14:44 Desktop > -rwx-- 1 cedric Domain Users 6527 2006-06-21 18:14 Nouveau Texte > Open Office.odt > lrwxrwxrwx 1 root Domain Users 25 2006-06-21 17:05 tmp -> > /net/soda/home/cedric/tmp Forget this part ! As the log shows, there's no need to be on NFS to get the kernel oplock error. On open: [2006/06/21 18:14:09, 3] smbd/dosmode.c:unix_mode(121) unix_mode(Nouveau Texte Open Office.odt) returning 0700 [2006/06/21 18:14:09, 2] smbd/open.c:open_file(350) cedric opened file Nouveau Texte Open Office.odt read=Yes write=Yes (numopen=1) [2006/06/21 18:14:09, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(166) linux_set_kernel_oplock: got kernel oplock on file Nouveau Texte Open Office.odt, dev = 804, inode = 446, file_id = 27 On write: [2006/06/21 18:14:27, 3] smbd/oplock.c:initial_break_processing(311) initial_break_processing: called for dev = 0x804, inode = 446 file_id = 27 Current oplocks_open (exclusive = 1, levelII = 0) ... [2006/06/21 18:14:27, 3] smbd/dosmode.c:unix_mode(121) unix_mode(Nouveau Texte Open Office.odt) returning 0700 [2006/06/21 18:14:27, 2] smbd/open.c:open_file(350) cedric opened file Nouveau Texte Open Office.odt read=Yes write=No (numopen=2)[2006/06/21 18:14:27, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(161) linux_set_kernel_oplock: Refused oplock on file Nouveau Texte Open Office.odt, fd = 26, dev = 804, inode = 446. (Ressource temporairement non disponible) Best regards -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
Cedric Delfosse a écrit : Jeremy Allison a écrit : On Thu, Jun 15, 2006 at 11:39:21AM +0200, Cedric Delfosse wrote: (Samba 3.0.21c / kernel 2.4.27 / Debian Sarge) Hello, One of my user open a file (located on a SAMBA server) in its application, and when he tries to save it, he gets a "share violation" error. (other people have this problem too). This error happens since I upgraded the SAMBA server from 3.0.14a to 3.0.21c. smbstatus for this file: 32613DENY_WRITE 0x20089 RDONLY NONE /home/user/J84400os-V8 Thu Jun 15 10:46:05 2006 Samba log when trying to save the file: [2006/06/15 10:50:44, 2] smbd/open.c:open_file(350) user1 opened file J84400os-V8 read=Yes write=No (numopen=12) [2006/06/15 10:50:44, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(161) linux_set_kernel_oplock: Refused oplock on file J84400os-V8, fd = 33, dev = b, inode = 2621998. (Resource temporarily unavailable) You can turn off kernel oplocks with "kernel oplocks = no" in your smb.conf. You might want to try 3.0.22 (or the 3.0.23RC2) instead as we made changes in this area. I will try 3.0.22 and tell you if this fix my problem. Setting "kernel oplocks = No" didn't fix the problem too: I now get a "Access Denied" error. Here is now what I have into the samba log (the user opens the file and tries to save it): This may be important: the "Services" directory of the filename you will see in the log is coming from a imported file system via autofs (NFS). ... [2006/06/21 15:58:09, 3] smbd/process.c:process_smb(1194) Transaction 82990 of length 312 [2006/06/21 15:58:09, 3] smbd/process.c:switch_message(993) switch message SMBtrans2 (pid 16301) conn 0x84a2e50 [2006/06/21 15:58:09, 3] smbd/trans2.c:call_trans2qfilepathinfo(2861) call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 [2006/06/21 15:58:09, 3] smbd/trans2.c:call_trans2qfilepathinfo(2913) call_trans2qfilepathinfo Repertoires_Partages/EMTStvit/Services/Bureau_Etude/prive/Tell/plan/J/J16/J16146/J16146os/plans/outil-roulage/plans (fnum = -1) level=1004 call=5 total_data=0 [2006/06/21 15:58:09, 3] smbd/process.c:process_smb(1194) Transaction 82991 of length 322 [2006/06/21 15:58:09, 3] smbd/process.c:switch_message(993) switch message SMBtrans2 (pid 16301) conn 0x84a2e50 [2006/06/21 15:58:09, 3] smbd/trans2.c:call_trans2findfirst(1632) call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 2 requires_resume_key = 4 level = 0x104, max_data_bytes = 16384 [2006/06/21 15:58:09, 3] smbd/dir.c:dptr_create(511) creating new dirptr 256 for path Repertoires_Partages/EMTStvit/Services/Bureau_Etude/prive/Tell/plan/J/J16/J16146/J16146os/plans/outil-roulage/plans, expect_close = 1 [2006/06/21 15:58:09, 3] smbd/process.c:process_smb(1194) Transaction 82992 of length 312 [2006/06/21 15:58:09, 3] smbd/process.c:switch_message(993) switch message SMBtrans2 (pid 16301) conn 0x84a2e50 [2006/06/21 15:58:09, 3] smbd/trans2.c:call_trans2qfilepathinfo(2861) call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 [2006/06/21 15:58:09, 3] smbd/trans2.c:call_trans2qfilepathinfo(2913) call_trans2qfilepathinfo Repertoires_Partages/EMTStvit/Services/Bureau_Etude/prive/Tell/plan/J/J16/J16146/J16146os/plans/outil-roulage/plans (fnum = -1) level=1004 call=5 total_data=0 [2006/06/21 15:58:09, 3] smbd/process.c:process_smb(1194) Transaction 82993 of length 360 [2006/06/21 15:58:09, 3] smbd/process.c:switch_message(993) switch message SMBtrans2 (pid 16301) conn 0x84a2e50 [2006/06/21 15:58:09, 3] smbd/trans2.c:call_trans2findfirst(1632) call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=1, close_if_end = 2 requires_resume_key = 4 level = 0x104, max_data_bytes = 16384 [2006/06/21 15:58:09, 3] smbd/dir.c:dptr_create(511) creating new dirptr 256 for path Repertoires_Partages/EMTStvit/Services/Bureau_Etude/prive/Tell/plan/J/J16/J16146/J16146os/plans/outil-roulage/plans, expect_close = 1 [2006/06/21 15:58:09, 3] smbd/process.c:process_smb(1194) Transaction 82994 of length 364 [2006/06/21 15:58:09, 3] smbd/process.c:switch_message(993) switch message SMBntcreateX (pid 16301) conn 0x84a2e50 [2006/06/21 15:58:09, 3] smbd/dosmode.c:unix_mode(121) unix_mode(Repertoires_Partages/EMTStvit/Services/Bureau_Etude/prive/Tell/plan/J/J16/J16146/J16146os/plans/outil-roulage/plans/J16146os2-ind.C-MAP2) returning 0764 [2006/06/21 15:58:10, 2] smbd/open.c:open_file(350) tdebouche opened file Repertoires_Partages/EMTStvit/Services/Bureau_Etude/prive/Tell/plan/J/J16/J16146/J16146os/plans/outil-roulage/plans/J16146os2-ind.C-MAP2 read=Yes write=No (numopen=4) [2006/06/21 15:58:10, 3] smbd/process.c:process_smb(1194) Transaction 82995 of length 63 [2006/06/21 15:58:10, 3] smbd/process.c:switch_message(993) switch message SMBreadX (pid 16301) conn 0x84a2e50 [2006/06/21 15:58:10, 3] smbd/reply.c:send_file_readX(2613)
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
Jeremy Allison a écrit : On Thu, Jun 15, 2006 at 11:39:21AM +0200, Cedric Delfosse wrote: (Samba 3.0.21c / kernel 2.4.27 / Debian Sarge) Hello, One of my user open a file (located on a SAMBA server) in its application, and when he tries to save it, he gets a "share violation" error. (other people have this problem too). This error happens since I upgraded the SAMBA server from 3.0.14a to 3.0.21c. smbstatus for this file: 32613DENY_WRITE 0x20089 RDONLY NONE /home/user/J84400os-V8 Thu Jun 15 10:46:05 2006 Samba log when trying to save the file: [2006/06/15 10:50:44, 2] smbd/open.c:open_file(350) user1 opened file J84400os-V8 read=Yes write=No (numopen=12) [2006/06/15 10:50:44, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(161) linux_set_kernel_oplock: Refused oplock on file J84400os-V8, fd = 33, dev = b, inode = 2621998. (Resource temporarily unavailable) You can turn off kernel oplocks with "kernel oplocks = no" in your smb.conf. You might want to try 3.0.22 (or the 3.0.23RC2) instead as we made changes in this area. I will try 3.0.22 and tell you if this fix my problem. Regards, -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
Volker Lendecke a écrit : On Thu, Jun 15, 2006 at 11:39:21AM +0200, Cedric Delfosse wrote: One of my user open a file (located on a SAMBA server) in its application, and when he tries to save it, he gets a "share violation" error. (other people have this problem too). This error happens since I upgraded the SAMBA server from 3.0.14a to 3.0.21c. Try with 'kernel oplocks = no'. This is safe as long as you do not have any processes that concurrently access the files from Unix or via an NFS export. Thanks, at last this can solve my issue for the moment. But could you provide me a setup (linux kernel version/ glibc version ?) where kernel oplocks works ? (by the way, smb.conf manual say about the kernel oplocks parameters: " This parameter defaults to on ... You should never need to touch this parameter." Maybe this statement should be changed.) Regards, -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?
(Samba 3.0.21c / kernel 2.4.27 / Debian Sarge)
Hello,
One of my user open a file (located on a SAMBA server) in its
application, and when he tries to save it, he gets a "share violation"
error. (other people have this problem too).
This error happens since I upgraded the SAMBA server from 3.0.14a to
3.0.21c.
smbstatus for this file:
32613DENY_WRITE 0x20089 RDONLY NONE
/home/user/J84400os-V8 Thu Jun 15 10:46:05 2006
Samba log when trying to save the file:
[2006/06/15 10:50:44, 2] smbd/open.c:open_file(350)
user1 opened file J84400os-V8 read=Yes write=No (numopen=12)
[2006/06/15 10:50:44, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(161)
linux_set_kernel_oplock: Refused oplock on file J84400os-V8,
fd = 33, dev = b, inode = 2621998. (Resource temporarily unavailable)
Corresponding strace log:
open("J84400os-V8",O_RDONLY|O_LARGEFILE) = 27
time(NULL) = 1150361813
geteuid32() = 1043
write(29, "[2006/06/15 10:56:53, 2] smbd/op"..., 52) = 52
geteuid32() = 1043
write(29, " user1 opened file Repertoi"..., 162) = 162
fcntl64(27, F_SETSIG, 0x24) = 0
fcntl64(27, 0x400 /* F_??? */, 0x1) = -1 EAGAIN (Resource
temporarily unavailable)
time(NULL) = 1150361813
geteuid32() = 1043
write(29, "[2006/06/15 10:56:53, 3] smbd/op"..., 74) = 74
geteuid32() = 1043
write(29, " linux_set_kernel_oplock: Refus"..., 229) = 229
fnctl 0x400 op seems to be F_SETLEASE.
Is there a problem between the version of kernel I use and how SAMBA use
F_SETLEASE ?
Is there a way to resolve this problem ? Should I recompile SAMBA with
specific options to fix this problem ?
Best regards,
--
Cédric Delfosse Linbox / Free&ALter Soft
152, rue de Grigy - Technopole Metz 57070 METZ
tél : 03 87 50 87 98 http://linbox.com
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbd hanging because netbios-ssn TCP connexion not seen as down
Hello, (Samba 3.0.21c / Linux 2.4.27) a smbd process was hanging on a file server since one day. This smbd process was locking some files on the server, and that was causing some share violation for a Windows user (well, that what I think). I did a lsof on the smbd process, and I saw that the TCP netbios-ssn connection was still seen as established with the machine of the windows user that locked the files. The problem is that the machine was shut down at this moment since at least half an hour. A strace showed me that smbd was looping on select calls, waiting for some data to read from the socket. Maybe that's why the smbd process was not exiting, and so still locking some files. What can I do to avoid this kind of problem ? In my smb.conf file, the "keepalive" option value was 300. Shouldn't this option be sufficient ? How does keepalive work ? Does it work by sending some kind of "netbios-ssn echo packets" to the windows client ? Does it work with all versions of Windows ? If I set: socket options = SO_KEEPALIVE TCP_NODELAY, will this fix the problem when keepalive SAMBA option doesn't work ? (tcp_keepalive_time is 2 hours for Linux 2.4). Best regards, -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 METZ tél : 03 87 50 87 98 http://linbox.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Domain trust relationship between Samba 3.0.21c and AD 2003
Hello, I have two domains: - a domain FRANCE on a SAMBA PDC called "SARGE" - a domain DOMAINTEST on a Active Directory called "SRV2003-2" I followed the samba howto chapter on setting a domain trust relationship between this two domains. For now, I just want DOMAINTEST users to log on shares of the FRANCE domain. On Windows 2003 side, with the MMC I can check/revalidate the trust relationship with the samba PDC. And windows tells me that it's OK. On SAMBA side, looks like it's OK: # net rpc trustdom list Trusted domains list: DOMAINTEST S-1-5-21-769731554-1856840314-4054211777 Trusting domains list: DOMAINTEST S-1-5-21-769731554-1856840314-4054211777 I installed winbind, and I can get the user and group list from DOMAINTEST: # wbinfo -gu DOMAINTEST\admins du domaine DOMAINTEST\utilisa. du domaine DOMAINTEST\invitDOMAINTEST\ordinateurs du domaine DOMAINTEST\contrDOMAINTEST\administrateurs du schDOMAINTEST\administrateurs de l'entreprise DOMAINTEST\propriDOMAINTEST\dnsupdateproxy BUILTIN\administrators BUILTIN\print operators BUILTIN\backup operators BUILTIN\replicators DOMAINTEST\administrateur DOMAINTEST\anonymous DOMAINTEST\cedric DOMAINTEST\invitDOMAINTEST\krbtgt DOMAINTEST\sshd DOMAINTEST\sshd_server DOMAINTEST\support_388945a0 Now, from the AD, if I try to log in as an AD user on a FRANCE domain share, it doesn't work (access denied). Here is what I have in log.smbd: [2006/04/21 15:30:08, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(633) Doing spnego session setup [2006/04/21 15:30:08, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(664) NativeOS=[Windows Server 2003 3790] NativeLanMan=[] PrimaryDomain=[Windows Server 2003 5.2] [2006/04/21 15:30:08, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(662) Got user=[Administrateur] domain=[DOMAINTEST] workstation=[SRV2003-2] len1=24 len2=24 ... [2006/04/21 15:30:08, 3] auth/auth.c:check_ntlm_password(219) check_ntlm_password: Checking password for unmapped user [EMAIL PROTECTED] with the new password interface [2006/04/21 15:30:08, 3] auth/auth.c:check_ntlm_password(222) check_ntlm_password: mapped user is: [EMAIL PROTECTED] ... [2006/04/21 15:30:08, 3] auth/auth_util.c:make_server_info_info3(1282) User Administrateur does not exist, trying to add it [2006/04/21 15:30:09, 0] auth/auth_util.c:make_server_info_info3(1297) make_server_info_info3: pdb_init_sam failed! [2006/04/21 15:30:09, 2] auth/auth.c:check_ntlm_password(317) check_ntlm_password: Authentication for user [Administrateur] -> [Administrateur] FAILED with error NT_STATUS_NO_SUCH_USER In log.winbind, I don't know what is the conclusion of this log: [2006/04/21 15:30:08, 3] nsswitch/winbindd_misc.c:winbindd_interface_version(454) [0]: request interface version [2006/04/21 15:30:08, 3] nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(487) [0]: request location of privileged pipe [2006/04/21 15:30:08, 3] nsswitch/winbindd_pam.c:winbindd_pam_auth_crap(519) [0]: pam auth crap domain: [DOMAINTEST] user: Administrateur [2006/04/21 15:30:08, 3] nsswitch/winbindd_misc.c:winbindd_interface_version(454) [0]: request interface version [2006/04/21 15:30:08, 3] nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(487) [0]: request location of privileged pipe [2006/04/21 15:30:08, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(336) [0]: getpwnam domaintest\administrateur [2006/04/21 15:30:08, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(336) [0]: getpwnam DOMAINTEST\administrateur [2006/04/21 15:30:08, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(336) [0]: getpwnam DOMAINTEST\ADMINISTRATEUR With "getent passwd", the DOMAINTEST users are not listed. And I have these errors in log.winbind when using this command: [2006/04/21 15:55:30, 3] nsswitch/winbindd_misc.c:winbindd_interface_version(454) [0]: request interface version [2006/04/21 15:55:30, 3] nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(487) [0]: request location of privileged pipe [2006/04/21 15:55:30, 3] nsswitch/winbindd_user.c:winbindd_setpwent_internal(432) [0]: setpwent [2006/04/21 15:55:30, 3] nsswitch/winbindd_user.c:winbindd_getpwent(626) [0]: getpwent [2006/04/21 15:55:30, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(85) error getting user id for sid S-1-5-21-769731554-1856840314-4054211777-500 [2006/04/21 15:55:30, 1] nsswitch/winbindd_user.c:winbindd_getpwent(715) could not lookup domain user anonymous [2006/04/21 15:55:30, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(85) error getting user id for sid S-1-5-21-769731554-1856840314-4054211777-1117 [2006/04/21 15:55:30, 1] nsswitch/winbindd_user.c:winbindd_getpwent(715) could not lookup domain user cedric [2006/04/21 15:55:30, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(85) error getting user id for sid S-1-5-21-769731554-1856840314-4054211777-1121 [2006/04/21 15:55:30, 1] nsswitch/winbindd_user.c:winbindd_getpwent(
[Samba] Setting a HP 9300 driver with APW -> Windows protection fault
Hello, SAMBA 3.0.10, MS Windows 2000 pro, HP deskjet 9300 printer driver available at: ftp://ftp.hp.com/pub/softlib/software3/COL4383/dj-14540-2/dj9308en.exe When I set the driver via APW, and then close the properties dialog, I get a protection fault from C:\winnt\explorer.exe. Attached is the corresponding samba log at level 3, and my smb.conf. The driver installation works fine if I set default devmode = yes in smb.conf, but I get a protection fault if I try to change a printer option. Regards, -- Cédric Delfosse Linbox / Free&ALter Soft 152, rue de Grigy - Technopole Metz 57070 Metz - FRANCE tél: +33 (0)3 87 50 87 90 http://linbox.com # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2001/05/16 09:21:39 # Global parameters [global] # Do something sensible when Samba crashes: mail the admin a backtrace panic action = /usr/share/samba/panic-action %d workgroup = MYGROUP server string = Samba Server security = user encrypt passwords = true passdb backend = tdbsam guest log file = /var/log/samba/log.%m logon path = \\%N\%U\profile max log size = 50 log level = 3 dns proxy = No hosts allow = 192.168.1. 192.168.0. 127. domain logons = yes logon script = %U.bat printing = cups printcap name = cups load printers = yes ; default devmode = yes [netlogon] path = /tmp/netlogon writeable = no guest ok = no [homes] comment = Home Directories writeable = Yes browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes public = yes writable = no printer admin = root [print$] comment = Printer Driver Download Area path = /var/lib/samba/printers/ browseable = yes guest ok = yes read only = yes write list = root admin users = root [public] path = /home/httpd/html/NewsClipper writeable = Yes guest ok = No [tmp] path = /tmp writeable = Yes guest ok = Yes [fax] comment = Fax path = /var/spool/samba printable = Yes postscript = Yes print command = ( /usr/local/bin/printfax %I %s %U %m; rm %s ) & -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
