Wilfred van Velzen
2004-Jun-14 07:10 UTC
[Samba] Samba shares becoming inactive after a while
When a user is not using a samba share, after a while they become "inactive". When a user wants to access the share again, it takes an irritating long time before they get access again. The (windows) application that does the accessing is not responding during that time. There are no drive letters assigned to the shares in a logon script. When I do assign a drive letter to the share (in a test situation), this problem doesn't seem to exist. But how can I prevent this without assigning drive letters to all the shares? Here's the global section of my /etc/samba/smb.conf : [global] workgroup = SERCOM server string = Samba Server encrypt passwords = Yes map to guest = Bad User time server = Yes unix extensions = Yes socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY keepalive = 0 printcap name = CUPS add user script = /usr/sbin/useradd -c Machine -d /dev/null -s /bin/false %m$ domain logons = Yes os level = 65 preferred master = Yes domain master = Yes printing = cups veto files = /*.eml/*.nws/riched20.dll/*.{*}/ I've already experimented with the 'socket options' and 'keepalive' options, but these don't seem to make any difference... Met vriendelijke groet / Best regards, Wilfred van Velzen -- SERCOM Regeltechniek b.v. Heereweg 9 2161 AB Lisse Nederland +31 (0)252 416530 (voice) +31 (0)252 419481 (fax) <http://www.sercom.nl/> Op al onze offertes, op alle opdrachten aan ons en op alle met ons gesloten overeenkomsten zijn toepasselijk de METAALUNIEVOORWAARDEN, gedeponeerd ter Griffie van de Rechtbank te Rotterdam, zoals deze luiden volgens de laatstelijk aldaar neergelegde tekst. De leveringsvoorwaarden worden u op verzoek toegezonden.
On Mon, 2004-06-14 at 03:09, Wilfred van Velzen wrote:> When a user is not using a samba share, after a while they become > "inactive". When a user wants to access the share again, it takes an > irritating long time before they get access again. The (windows) > application that does the accessing is not responding during that > time. There are no drive letters assigned to the shares in a logon > script. When I do assign a drive letter to the share (in a test > situation), this problem doesn't seem to exist. But how can I prevent > this without assigning drive letters to all the shares? > > Here's the global section of my /etc/samba/smb.conf : > > [global] > workgroup = SERCOM > server string = Samba Server > encrypt passwords = Yes > map to guest = Bad User > time server = Yes > unix extensions = Yes > socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY > keepalive = 0 > printcap name = CUPS > add user script = /usr/sbin/useradd -c Machine -d /dev/null -s > /bin/false %m$ > domain logons = Yes > os level = 65 > preferred master = Yes > domain master = Yes > printing = cups > veto files = /*.eml/*.nws/riched20.dll/*.{*}/ > > I've already experimented with the 'socket options' and 'keepalive' > options, but these don't seem to make any difference...From the included docs for Samba: deadtime (G) The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected. The deadtime only takes effect if the number of open files is zero. This is useful to stop a server's resources being exhausted by a large number of inactive connections. Most clients have an auto-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users. Using this parameter with a timeout of a few minutes is recommended for most systems. A deadtime of zero indicates that no auto-disconnection should be performed. Default: deadtime = 0 Example: deadtime = 15 Hope this helps. -- greg@gregfolkert.net REMEMBER ED CURRY! http://www.iwethey.org/ed_curry Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040614/79a6943d/attachment.bin
Wilfred van Velzen
2004-Jun-15 06:22 UTC
[Samba] Samba shares becoming inactive after a while
>>> Greg Folkert <greg@gregfolkert.net> 2004-06-14 17:01:45 >>> > On Mon, 2004-06-14 at 03:09, Wilfred van Velzen wrote: > > When a user is not using a samba share, after a while they become > > "inactive". When a user wants to access the share again, it takesan> > irritating long time before they get access again. The (windows) > > application that does the accessing is not responding during that > > time. There are no drive letters assigned to the shares in a logon > > script. When I do assign a drive letter to the share (in a test > > situation), this problem doesn't seem to exist. But how can Iprevent> > this without assigning drive letters to all the shares? > > > > Here's the global section of my /etc/samba/smb.conf : > > > > [global] > > workgroup = SERCOM > > server string = Samba Server > > encrypt passwords = Yes > > map to guest = Bad User > > time server = Yes > > unix extensions = Yes > > socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY > > keepalive = 0 > > printcap name = CUPS > > add user script = /usr/sbin/useradd -c Machine -d /dev/null -s > > /bin/false %m$ > > domain logons = Yes > > os level = 65 > > preferred master = Yes > > domain master = Yes > > printing = cups > > veto files = /*.eml/*.nws/riched20.dll/*.{*}/ > > > > I've already experimented with the 'socket options' and'keepalive'> > options, but these don't seem to make any difference... > > From the included docs for Samba: > > deadtime (G) > The value of the parameter (a decimal integer) representsthe> number of minutes of inactivity before a connection is > considered dead, and it is disconnected. The deadtime onlytakes> effect if the number of open files is zero. > > This is useful to stop a server's resources being exhaustedby a> large number of inactive connections. > > Most clients have an auto-reconnect feature when a connectionis> broken so in most cases this parameter should be transparentto> users. > > Using this parameter with a timeout of a few minutes is > recommended for most systems. > > A deadtime of zero indicates that no auto-disconnectionshould> be performed. > > Default: deadtime = 0 > > Example: deadtime = 15 > > Hope this helps.Since 'deadtime = 0' is the default, and I haven't specified it explicitly, this should already be in effect. But I have now specified 'deadtime = 540' in my global section, as a test value... We'll see... Met vriendelijke groet / Best regards, Wilfred van Velzen Met vriendelijke groet / Best regards, Wilfred van Velzen -- SERCOM Regeltechniek b.v. Heereweg 9 2161 AB Lisse Nederland +31 (0)252 416530 (voice) +31 (0)252 419481 (fax) <http://www.sercom.nl/> Op al onze offertes, op alle opdrachten aan ons en op alle met ons gesloten overeenkomsten zijn toepasselijk de METAALUNIEVOORWAARDEN, gedeponeerd ter Griffie van de Rechtbank te Rotterdam, zoals deze luiden volgens de laatstelijk aldaar neergelegde tekst. De leveringsvoorwaarden worden u op verzoek toegezonden.