I ran into this a few months ago and it was my own fault. This may or
may not be your issue.

Alkis Georgopoulos found that hosts.allow has a matching precedence
you can read about in 'man hosts.allow'

So if you have clients that have multiple matches, like

ALL: 192.168.
nbdrootd: ALL: keepalive

the nbdrootd will not be applied for a client in 192.168.0.0/16


from man hosts.allow:
...it is important to realize that the allow table is scanned before the
deny table, that ***the search terminates when a match is found***, and
that access is granted when no match is found at all.

So I guess that the search stops at the first match,
 ALL: 192.168.
before reading the nbdrootd line which contains the keepalive option.


Perhaps this is similar to the issue you have? Re-thanks to Alkis.

-Michael



On Mon, Dec 20, 2010 at 9:18 AM, Matthew Wyneken <[email protected]> wrote:
>
> In order to keep track of the clients served by my LTSP server I downloaded 
> nbdstat, a nifty Perl script that shows me the connections on the server. 
> Among other things, the script uses the following line to figure out the 
> active connections:
>
> lsof 2>&1|grep ^nbd-serv |grep '(ESTABLISHED)'
>
> This results in lines like this:
>
> nbd-serve 18572     nobody    0u     IPv4              68920         0t0      
>   TCP 
> teqltsp2.physik.uni-freiburg.de:2001->phyv14.physik.uni-freiburg.de:60362 
> (ESTABLISHED)
> nbd-serve 26941     nobody    0u     IPv4             205271         0t0      
>   TCP 
> teqltsp2.physik.uni-freiburg.de:2001->brehme.physik.uni-freiburg.de:56363 
> (ESTABLISHED)
> nbd-serve 32259     nobody    0u     IPv4             116705         0t0      
>   TCP 
> teqltsp2.physik.uni-freiburg.de:2001->effenberg.physik.uni-freiburg.de:37570 
> (ESTABLISHED)
>
>
> The script does its processing and shows its final results like this:
>
> --- BEGIN ---
> # nbdstat
>                   nbd-connections of Thin Clients
> Nr. ThinClient        PID    Started at           Image/Swap file
> ===========================================================================================
>  1 beckenbauer       6232   2010-12-15 19:26:07  /opt/ltsp/images/i386.img
>  2 brehme            26941  2010-12-19 16:52:46  /opt/ltsp/images/amd64.img
>  3 effenberg         32259  2010-12-17 16:27:53  /opt/ltsp/images/amd64.img
>  4 klinsmann         2919   2010-12-15 13:29:04  /opt/ltsp/images/i386.img
>  5 kohler            2386   2010-12-15 12:32:35  /opt/ltsp/images/i386.img
>  6 netzer            6702   2010-12-20 13:59:43  /opt/ltsp/images/amd64.img
>                      15477  2010-12-16 11:39:41  /opt/ltsp/images/i386.img
>                      15866  2010-12-16 12:01:46  /opt/ltsp/images/amd64.img
>  7 phyp5             2233   2010-12-15 12:19:24  /opt/ltsp/images/amd64.img
>  8 phyp7             2307   2010-12-15 12:25:59  /opt/ltsp/images/amd64.img
>  9 phyv1             2076   2010-12-15 12:07:13  /opt/ltsp/images/amd64.img
>  10 phyv10            2080   2010-12-15 12:07:30  /opt/ltsp/images/amd64.img
>                      2144   2010-12-15 12:12:01  /opt/ltsp/images/amd64.img
>  11 phyv14            18572  2010-12-16 16:11:37  /opt/ltsp/images/amd64.img
>  12 phyv4             18388  2010-12-16 15:54:48  /opt/ltsp/images/amd64.img
>  13 phyv5             2059   2010-12-15 12:07:04  /opt/ltsp/images/amd64.img
>                      3686   2010-12-15 14:51:18  /opt/ltsp/images/amd64.img
>  14 phyv7             1674   2010-12-15 11:51:38  /opt/ltsp/images/amd64.img
>                      2036   2010-12-15 12:06:42  /opt/ltsp/images/amd64.img
>  15 schwarzenbeck     1977   2010-12-15 12:04:08  /opt/ltsp/images/i386.img
>  16 voeller           1931   2010-12-15 12:00:43  /opt/ltsp/images/i386.img
>
>  nbd-images in use:                              Count
> ======================================================
>  1 /opt/ltsp/images/amd64.img                     15
>  2 /opt/ltsp/images/i386.img                       6
>
> --- END ---
>
> What bothers me is that there are a number of clients that show several 
> connections. What's apparently happening is that the connections are not 
> being dropped when the clients are shut off but continue to be marked as 
> "ESTABLISHED".
>
> I've got a second LTSP server that does not exhibit this behavior. The two 
> servers are set up as much alike as I was able to. AAMOF I created the 
> "problem" server by cloning as much as possible from the other server.
>
> I've been looking for places to set NBD timeouts and have found some but as 
> far as I can tell, the ltsp configuration files and scripts do not set any 
> kind of NBD timeouts.
>
> You would think that somewhere the two servers are configured slightly 
> differently but I can't find where that might be. I don't even know if it's 
> an LTSP configuration or a general operating system configuration.
>
> Does anybody have any ideas?
> --
> Matthew
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net



--
Michael Blinn
People Places, Inc.
www.peopleplaces.org
---
CONFIDENTIALITY NOTICE:
This message, and any attachments that may accompany it, contain
information that is intended for the use of the individual or entity
to which it is addressed and may contain information that is
privileged, confidential, or otherwise exempt from disclosure under
applicable law. If the recipient of this message is not the intended
recipient, any disclosure, copying, or other use of this communication
or any of the information, which it contains is unauthorized and
prohibited.  If you have received this message in error, please notify
the original sender by return mail and delete this message, along with
any attachments, from your computer. Thank you.

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to