Re: [Samba] Samba and Terminal Server Whitepaper
Ok, I have had a preview of the document. The Terminal Server issues are as far as I can see all covered except one. This issue is related to a Solaris 32 bit application limitation. I do not know if HP-UX got this limitation aswell as our HP-UX samba userload is not high enough to reach this limitaion (if any). Here is a Sun statement which describes the problem: "For a 32-bit application, a stdio library FILE structure represents the underlying file descriptor as an unsigned char, limiting the range of fds which can be opened as FILE's to 0-255 inclusive. A common, known problem is that when the 32-bit stdio is used for a large server application, the 255 limit is frequently exceeded. Although this limitation does not exist for 64-bit applications, this problem will always remain for 32-bit applications." Without the netbios or hosts 'fix' described in Erics whitepaper one would easily reach this limitation. The samba server smbd process for this TS would have a large amount of open files ( > 256). To solve this on Solaris we compiled the samba source with the gcc -m64 option making the samba binaries 64 bit and increased the default settings for max file descriptors in /etc/system. Is this something which should be added in some sort of documentation/whitepaper? > Sorry about the Terminal Server Whitepaper "attachment > fiasco". HP will > host both the Samba and the HP CIFS Server versions at >>Attached is a 500KB read-only .doc file with a Samba and Terminal >>Server >>whitepaper. I have tried to hit every known issue and all available >>workarounds. If anyone has comments or suggestions, let me know. JT Regards Per Kjetil Grotnes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3 and Windows 2000 (SP4) Terminal Server
Samba-3.0.2pre1 has the MAX_CONNECTIONS-parameter fix in smbd/conn.c. So there should be no need to tweak the code anymore for Windows Terminal Server users. Regards Per Kjetil Grotnes > -Opprinnelig melding- > Fra: Per Kjetil Grotnes > [mailto:[EMAIL PROTECTED] > Sendt: 5. januar 2004 10:34 > Til: 'Sambalist ([EMAIL PROTECTED])' > Emne: Re: [Samba] Samba 3 and Windows 2000 (SP4) Terminal Server > > > > > limitation and had to modify the MAX_CONNECTIONS-parameter in > > > smbd/conn.c. Now we're planning the migration from s. > 2.2.8a to s. > > > 3.0.1. Is the modification in smbd/conn.c still necessary, > > when using > > > s. 3.0.1 in a Windows 2000 (SP4) terminal server environment? > > > > This issue has been fixed, but I'm not sure if it made 3.0.1 > > (I can't see it in the changelog). > > Andrew Bartlett > > You can find a patch at: > https://bugzilla.samba.org/show_bug.cgi?id=716 > > Jeremy > Allison claims the patch is applied, but the source code in > smbd/conn.c for samba.latest (3.0.1) has not been changed. > > Regards > Per Kjetil Grotnes > > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3 and Windows 2000 (SP4) Terminal Server
> > limitation and had to modify the MAX_CONNECTIONS-parameter in > > smbd/conn.c. Now we're planning the migration from s. 2.2.8a to s. > > 3.0.1. Is the modification in smbd/conn.c still necessary, > when using > > s. 3.0.1 in a Windows 2000 (SP4) terminal server environment? > > This issue has been fixed, but I'm not sure if it made 3.0.1 > (I can't see it in the changelog). > Andrew Bartlett You can find a patch at: https://bugzilla.samba.org/show_bug.cgi?id=716 Jeremy Allison claims the patch is applied, but the source code in smbd/conn.c for samba.latest (3.0.1) has not been changed. Regards Per Kjetil Grotnes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Suport to HP UX 10.20
> To : Support Staff You have a support agreement with the Samba support team? ;-) > I need to test SAMBA with a HP K 9000 Class machine, with HP-UX 10.20 > operating system. Wich SAMBA software version is compatible with this OS? > How can I get this software? We are running a HP 9000 with HP-UX 10.20 and Samba 2.2.7. Works like magic. And where to get it? Some would say STFW, but I would just point you to the www.samba.org site. Oh, and stay there abit and read up on samba. Then maybe you dont have to ask these questions and get snotty replies from silly people like me. ;-) Regards Per Kjetil Grotnes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Windows 2000 Terminal Server Environment
Yes, there are a few. I'll try to explain what todo and why. What: In your samba source directory before compiling change the MAX_CONNECTION in smbd/conn.c to a larger value than the default 128. We use 768. Why: In windows 2000 TS the connections (typically mounting disks) you will fast run out of connections on the samba server. This is due to the samba server only having one smbd process for each TS. So if you have 30 users with 5 mounted disks on the TS you will use 150 connections through that one smbd process. Thus you need to raise the MAX_CONNECTIONS to more than 128. What: Use the [homes] ( Path = /homes/%S )feature in smb.conf instead of making a regular share as your home-disk ie [home-disk] Path=/homes/U%. Why: if you use h: \\aixsamba\home-disk you will get conflict with matching files across user environments. Files will be locked by the TS because it thinks a matching file is already being used by another user. Scenario: User1 opens a file called 'iloveyou.doc' on his home directory the TS will open \\aixsamba\home-disk\iloveyou.doc. User2 opens a file called 'iloveyou.doc' on his home directory the TS will open \\aixsamba\home-disk\iloveyou.doc. Even though the *ix part opens up the /homes/User2/iloveyou.doc file for User2 the TS has placed a lock on the file thinking it is the same as User1 opened. Using the [homes] special share for home-dirs the UNC path will be \\aixsamba\User1\iloveyou.doc versus \\aixsamba\User2\iloveyou.doc thus placing locks on two diffrent files. What: If possible compile your samba for a 64bit environment. Why: You might run out of filedescriptors. I have no knowledge on AIX systems and file descriptors there, but on solaris a 32 bit application have max 256 filedescriptors unless you compile it as a 64 bit application (gcc -m64 worked for me). You might want to change the /etc/system file (again i dont know how AIX does it) to something like: Set rlim_fd_cur = 512 Set rlim_fd_max = 2048 But these will not matter if you do not compile samba as a 64 bits application. Well, that is what the solaris documentation claims anyway. AIX.. You know best. There might be some more issues, but at the moment I cant think of others than you might get problems with 'oplocks'. We turned all oplocks off on all shares on the samba server after users having word files corrupted on a daily basis. Hope this helps. Regards Per Kjetil Grotnes --- Emne: [Samba] Windows 2000 Terminal Server Environment I am running Citrix Metaframe XP on Windows 2000 server and would like to have the ability to access files on my AIX Unix server. Are there any issues with Samba in a Windows Terminal Server environment? Thanks, Tim Brooks -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] serious problem with W2K TS and 2.2.7 PDC
> The Win2k clients that have problems are ONLY Terminal Server machines. > Workstations do NOT have the problem. Win2k Terminal Server shares > multiple users over the one connection. One connection = one pid. > After applying the 2.2.6-2.2.7 patch minus bits regarding the %U, we > have had no further problems with the home share issue that I > described. Yesterday, I happened to be watching the log file (tail -f) > of one of the TSs as someone else logged on. I was on the same Terminal > server. Just after they connected, I tried to access my H: drive > (mapped to the home share) and got errors accessing both on the W2k > screen and in the log file. I agree that your problem is not with the authentication which I described. I see you are using the samba machine as domain master. I have no experience with this setting so I cant comment if there is something strange there. > # I snipped some printing, locking and other similar junk out. > ÆhomesÅ >comment = Home >writable = yes >valid users = %S >nt acl support = no >oplocks = no >path = /md3/profiles/%U >share modes = no The only thing I can see is diffrent from ours here is the /path/md3/%U. We use /path/md3/%S. Other than that there might be som TS registry settings (vaguely remember something about file link tracking) I am unsure. And I agree that the MultipleUsersOnConnection is sorely missed on W2K TS. Sorry that I cant be of any more assistance. Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] serious problem with W2K TS and 2.2.7 PDC
> Windows 2000 Terminal Server with SP3, with various pre SP4 updates > too. Various Win2K Pro, Win95 OSR2 clients. > ÆhomesÅ Can we see the Global section aswell please? Do you have Security = DOMAIN which is the prefered setting for Terminal Servers? (See previous postings about problem with Security = SERVER vs. Security = DOMAIN) Some in the samba team wrote earlier that they hoped SP3 for W2K would solve this problem. SP3 has not solved this problem. Just for their information. > The log for each TS has many of these errors (for various users): > Æ2002/12/06 16:39:14, 0Å smbd/service.c:make_connection(597) ts5 > (10.2.3.15) Can't change directory to /md3/profiles/rstu (Permission > denied) This is typical for some sort of auth failure in my experience. Try running loglevel 2 and see if the authentication fails (as in the problem with security = server). > Is it likely that the %U expansion fixes broke this - some assumption > with one pid/connection == one user? The one pid/connection is an issue in relation to the authentication problem. If one of the PIDs get problem with authing it will keep this problem until you kill the PID (thus it might explain why it works after you restarted). > On another issue, we get a lot of errors regarding failed connections to > truncated service names. For example we have a service called 'apps' > It only ever drops the last character and happens fairly frequently on > different shares. This has happened for quite a while, but hasn't had > any noticeable effect on users. We also saw this on a HP-UX 10.20 machine. We didnt notice any problems either, just that the log would notify a connection to a share with one letter missing. Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Does Samba 2.2.4 support 64 bit?
> Does Samba 2.2.4 on Solaris 8 support 64 bit? We are using Clearcase > & Rational told us that only samba 2.2.5 support 64 bit? We are using solaris 8 and have compiled Samba with GCC 3.02. We used the compiler option -m64 and -L/usr/local/lib/sparcv9 to get a 64 bits version of Samba. ( I placed those in the "CC = gcc " variable in the Makefile after a ./configure thus making it CC = gcc -m64 -L/usr/local/lib/sparcv9 ) This was done to make sure Solaris could use the /etc/system parameters: set rlim_fd_max = 4096 set rlim_fd_cur = 2048 If we did not the 32 bits Samba would only be able to use 256 file descriptors even though the 'system' parameter was set to those above. I am not sure if this is the correct way todo it, but it certainly solved our file descriptor problems. Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Share using %U -> File already opened
> > "H-disk" share is " /home/%U/disk"
> > User1 H: -> /home/user1/disk (h-disk)
> > User2 H: --> /home/user2/disk (h-disk)
> > When User1 opens a file "H:Øfoo.doc" and then User2 opens a file on this share
> > with the _same_ name ("H:Øfoo.doc") we get from Word (office programs?):
> > "Foo.doc already opened by another user".
> > When user1 closes his/her "foo.doc" on the home-share user2 is able to open the
> > file.
> > This is on Windows 2000 Terminal Services SP2 with Citrix Metaframe 1.8 (dont
> > diss this because it is Terminal Services please!) using office 2000.
> Don't use %U on Win2k Terminal Services. Use ÆhomesÅ and make sure you
> reference it with the *users* name, not 'homes'.
> Andrew Bartlett
Excellent. This works. The processes in Win2k now have unique share names for each
user thus preventing Win2k from thinking its the same file.
Thank you Andrew. :-)
Regards
Per Kjetil Grotnes
---
IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune
Tlf: 22 66 26 61, Fax: 22 66 26 65
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Share using %U -> File already opened
"H-disk" share is " /home/%U/disk"
User1 H: -> /home/user1/disk (h-disk)
User2 H: --> /home/user2/disk (h-disk)
When User1 opens a file "H:Øfoo.doc" and then User2 opens a file on this share
with the _same_ name ("H:Øfoo.doc") we get from Word (office programs?):
"Foo.doc already opened by another user".
When user1 closes his/her "foo.doc" on the home-share user2 is able to open the
file.
This is on Windows 2000 Terminal Services SP2 with Citrix Metaframe 1.8 (dont
diss this because it is Terminal Services please!) using office 2000.
On NT 4.0 TS w/metaframe 1.8 everything is okay.
With "foo.txt" and notepad.exe on W2K it works nicely.
When using process explorer in windows 2000 i see the PID which have the file
opned has a 'handle' like this:
ØDeviceØLanmanRedirectorØ:H:Ø5Øserver_nameØh-diskØfoo.doc
Anyone got a clue to how to let Windows 2000 (office?) know that those
home-shares are two diffrent shares with diffrent files?
As a last resort we can fix it with:
making a share "h-disk ---> /home"
Put in logonscript: net use H: ØØserver_nameØh-diskØ%username%Ødisk
We really do not like this as it will put the "root home disk" open for browsing (yes
I
know about browsable=no).
So - anyone out there please please help us with a solution for this. Any shot at it
at all would be appriciated.
Regards
Per Kjetil Grotnes
---
IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune
Tlf: 22 66 26 61, Fax: 22 66 26 65
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] lib/debug.c:reopen_logs(349)
> >Note that this error happens only with shares connected with the W2K TS > >machine and then only after a certain amount of users have logged on. > >Typically some sort of limit has been reached.. but which? > Have you tried to check the hard and soft limits for the maaximum number > of file descriptors associated with the account which have all the > shares doing the map? You mean this? /etc/system rlim_fd_max = 4096 rlim_fd_cur = 2048 I am not sure what you mean by "the account which have all the shares doing the map?". Other than the limits i wrote in the previous mail I am not sure what to adjust. Maybe some Veritas File System parameter? Or maybe I need to compile samba into a 64 bits application? Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] lib/debug.c:reopen_logs(349)
Windows 2000 sp2 with Terminal Services and Citrix 1.8 Metaframe as 'client'.
---
Problem starts at 40 to 50 users logged on. 7-9 shares mapped at login. Effect is
'access denied' on accessing directories restricted by group access even though
user has valid unix /etc/group access.
---
Machine SunFire 880
Samba 2.2.4
Configured with "-without-winbind"
Solaris 8 (release july 2001)
Gcc 3.0.1 from the companion package
Veritas Filesystem
Precompile adjustments done due to W2Ks 'feature' of just making one connection
to the samba server thus making only one process per Terminal Server.
Smbd/conn.c: #define MAX_CONNECTIONS 128
to
Smbd/conn.c: #define MAX_CONNECTIONS 768
#> plimit 17155
17155: /usr/local/samba/bin/smbd -D
resource current maximum
time(seconds) unlimited unlimited
file(blocks) unlimited unlimited
data(kbytes) unlimited unlimited
stack(kbytes) 8192unlimited
coredump(blocks) unlimited unlimited
nofiles(descriptors) 10010 10010
vmemory(kbytes) unlimited unlimited
/etc/system
rlim_fd_max = 4096
rlim_fd_cur = 2048
Log entries possibly related to this problem(?):
When we are in the period when the errors occurs and a user logs in we get this in
the log:
Æ2002/05/08 11:30:03, 0Å lib/debug.c:reopen_logs(349)
Unable to open new log file /usr/local/samba/var/log.smbd: Too many open files
In lib/debug.c
if (append_log)
new_dbf = sys_fopen( debugf, "a" );
else
new_dbf = sys_fopen( debugf, "w" );
if (!new_dbf) æ
log_overflow = True;
DEBUG(0, ("Unable to open new log file %s: %sØn", debugf, strerror(errno)));
log_overflow = False;
Which means that sys_fopen fails. I cant fnd any documentation on sys_fopen.
When users try to access shares where they would need their group-access rights
to get in there is a 'access denied' message. In the log (log level 3) it shows:
Æ2002/05/13 12:52:49, 3Å smbd/sec_ctx.c:set_sec_ctx(319)
1 user groups:
661
This is wrong! There should be at least 10 group Ids in the list for that user. The
group the user need to enter the directory is not in the list somehow!
Note that this error happens only with shares connected with the W2K TS
machine and then only after a certain amount of users have logged on.
Typically some sort of limit has been reached.. but which?
Our migration to W2K depends on this! *grins*
Regards
Per Kjetil Grotnes
---
IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune
Tlf: 22 66 26 61, Fax: 22 66 26 65
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 64 bits or 32 bits program
A program compiled on a solaris 8 SunFire 880 sparc machine with gcc 3.0.1, would it be a 32 bits program or a 64 bits program (in relation to how many file descriptors it can handle)? Is there a ./configure option to force samba to be a 64 bits application? Hardlimit for a 32 bit program is 256 file descriptors while a 64 bits program can handle 2 billion file descriptors. Maybe I am asking a silly question here, but it would be nice to hear an answer to it nevertheless. Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
