Re: [Samba] Samba 3.0.20 on Solaris: problem with fileaccess in a automounted filesystem
[EMAIL PROTECTED] wrote: Hello Knut, The problem may well be related to locking problems between the samba server and the NFS server (Solaris 2.5.1). Isn't 2.5.1 unsupported now? Have you patched it up as much as you can? Yes, so I have been thinking myself, but when logging on to the Solaris samba server which mounts from the 2.5.1 nfs server, checking/accessing the files/directories seems fine. No locking problems. Also, when using a Sgi samba server mounting from the same Solaris 2.5.1 system, everything is fine. One should think that it is more likely that things would work better between two Sun boxes than between a Sun and a Sgi. I will try to patch the Solaris 2.5.1 server with the latest recommended set and see if this helps. -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.0.20 on Solaris: problem with fileaccess in a automounted filesystem
Regards, Sent this one before, here's another go: My sambaserver, let's call it sserv, is running Solaris 8 (latest Recommended set) or 9 (tried both) compiled with automount support. When PC client A tries to access a file in a automounted mapping from sserv, the client is freezing and Windows Explorer has to be restarted. The NFS server which the samba server automounts from is a Solaris 2.5.1 system. The strange thing is that the same scenario works OK when the samba server is an Sgi IRIX system. The following pops up in the log for PC client A on sserv: [2005/08/26 15:57:29, 0] smbd/oplock.c:(1081) request_oplock_break: no response received to oplock break request to pid 16838 on port 58990 for dev = 4f4001d, inode = 187327, file_id = 51 [2005/08/26 15:57:29, 0] smbd/open.c:(726) open_mode_check: exlusive oplock left by process 16838 after break ! For file test.zip, dev = 4f4001d, inode = 187327. Deleting it to continue... Someone's got a clue ? -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problem using automount enabled samba 3.0.14a on Solaris 8
Very little luck with this one, none to be exact, so here I go again: I have lately experienced a rather peculiar problem, details follows: Trying to minimise the number of samba servers, I have compiled in support for automounting in a Solaris 8 version of samba 3.0.14a. Amongst others, this server mounts a filesystem from a Solaris 6 box by request. The samba server mounts the Solaris 6 filesystem fine, but when the user tries to access the directory symlinked from his homeshare (a NetApp share which works just fine), Windows Explorer freezes and has to be killed. The same procedure completes OK when using a Sgi samba server, so this makes me believe this is a samba Solaris only issue. Anyone able to help me with this one ? -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.0.14a problem: not able to see all files in a directory
Not much luck with this one, so I'm reposting hoping for some help... Samba 3.0.14a, running on Solaris 8 or Sgi IRIX 6.5.27. Scenario: 1. User has a symlink on his homeshare to a directory, let's call it dir1, which is automounted to the samba server (tried both Solaris samba server and Sgi, same result). 2. In a subdirectory under dir1 there's another directory (dir2) which contains a file (filename.wrl). 3. When the user directs Windows Explorer to homeshare\dir1\dir2, filename.wrl is invisible. If I check on the samba server, the file on the automounted filesystem is present, and looks in perfect order. If Windows Explorer is pointed to another directory at the same level as dir2, other files having the same extension (.wrl), are accessible as would be expected. This has been verified on both Win2K and XP. The file is also owned by the user that tries to access the file, and he does not have any problems accessing/modifying the file on unix (permission 666, directory is 755). Thus, it does not seem to be a permission problem. Also, touching a file in the same directory as filename.wrl, followed by a Refresh in Windows Explorer, will immediately list the touched the file, but the problemfile is still invisible. Clues, anyone ? -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * Phone: +4755996870, Fax: +4755995620 | * * Cellular Phone: +47 93005151 | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problem using automount enabled samba 3.0.14a on Solaris 8
Regards, I have lately experienced a rather peculiar problem, details follows: Trying to minimise the number of samba servers, I have compiled in support for automounting in a Solaris 8 version of samba 3.0.14a. Amongst others, this server mounts a filesystem from a Solaris 6 box by request. The samba server mounts the Solaris 6 filesystem fine, but when the user tries to access the directory symlinked from his homeshare (a NetApp share which works just fine), Windows Explorer freezes and have to be killed. The same procedure completes OK when using a Sgi samba server, so this makes me believe this is a samba Solaris only issue. Anyone able to help me with this one ? -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * Phone: +4755996870, Fax: +4755995620 | * * Cellular Phone: +47 93005151 | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.0.14a problem: not able to see all files in a directory
Regards, Samba 3.0.14a, running on Solaris 8 or Sgi IRIX 6.5.27. Scenario: 1. User has a symlink on his homeshare to a directory, let's call it dir1, which is automounted to the samba server (tried both Solaris samba server and Sgi, same result). 2. In a subdirectory under dir1 there's another directory (dir2) which contains a file (filename.wrl). 3. When the user directs Windows Explorer to homeshare\dir1\dir2, filename.wrl is invisible. If I check on the samba server, the file on the automounted filesystem is present, and looks in perfect order. If Windows Explorer is pointed to another directory at the same level as dir2, other files having the same extension (.wrl), are accessible as would be expected. This has been verified on both Win2K and XP. The file is also owned by the user that tries to access the file, and he does not have any problems accessing/modifying the file on unix (permission 666, directory is 755). Thus, it does not seem to be a permission problem. Also, touching a file in the same directory as filename.wrl, followed by a Refresh in Windows Explorer, will immediately list the touched the file, but the problemfile is still invisible. Clues, anyone ? -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * Phone: +4755996870, Fax: +4755995620 | * * Cellular Phone: +47 93005151 | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Information: IRIX 6.5.21 and samba 3.0.0RC2
Regards, I have seen one posting regarding the Error loading module '/local/samba/lib/charset/ISO8859-1.so': 291311:/local/samba/sbin/smbd: rld: Fatal Error: Cannot Successfully map soname '/local/samba/lib/charset/ISO8859-1.so' under any of the filenames /local/samba/lib/charset/ISO8859-1.so message and a reply from Samba team member Gerald Carter Please note that when compiling 3.0.0RC2 for IRIX, it seems that IRIX versions up to and including 6.5.21 need GNU libiconv to avoid the errormessages above. That is, do a configure including the --with-libiconv=/path/to/GNU/libiconv switch. If someone did manage to install 3.0.0RC2 on IRIX without use of GNU libiconv and avoiding the above messages, please drop me a note at [EMAIL PROTECTED] Compiler used: MIPSpro 7.4 -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * Phone: +4755996870, Fax: +4755995620 | * * Cellular Phone: +47 93005151 | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] nt pipe support and nt smb support in smb.conf
Regards, This is kind of urgent (isn't everything nowadays :-). Historically, our samba servers need to run with the two 'untouchables' nt pipe support and nt smb support both set to no (non default) based on a recommendation by one of our software vendors. These settings in smb.conf now prevents WIN2K SP2 clients from creating directories on the samba shares. The problem is that if I reset these two to default yes performance is better and creating directories are OK, but the application doesn't work. Despite the documentation saying that the nt smb support set to no could make Windows NT clients give faster performance with this option set to no, and this is still being investigated, does anybody know whether there are any need for these two parameters to be changed from the default ? This is with samba-2.2.5 nt pipe support (G) This boolean parameter controls whether smbd(8) will allow Windows NT clients to connect to the NT SMB specific IPC$ pipes. This is a developer debugging option and can be left alone. Default: nt pipe support = yes nt smb support (G) This boolean parameter controls whether smbd(8) will negotiate NT specific SMB support with Windows NT/2k/XP clients. Although this is a developer debugging option and should be left alone, benchmarking has discovered that Windows NT clients give faster performance with this option set to no. This is still being investigated. If this option is set to no then Samba offers exactly the same SMB calls that versions prior to Samba 2.0 offered. This information may be of use if any users are having problems with NT SMB support. You should not need to ever disable this parameter. Default: nt smb support = yes -- ** * Knut Hellebø | DAMN GOOD COFFEE !! * * Hydro IS Partner ESI (Unix) Team | (and hot too) * * Phone: +47 55 996870, Fax: +47 55 996342 | * * Cellular Phone: +47 93005151 | * * E-mail: [EMAIL PROTECTED] | Dale Cooper, FBI* ** -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
