Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 56721 - K12LTSP: bump loop detection to 250/s
K12LTSP: bump loop detection to 250/s
Product: Red Hat Raw Hide
Classification: Retired
Component: pxe (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-11-26 09:23 EST by Jeff Johnson
Modified: 2007-04-18 12:38 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-06 12:41:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Johnson 2001-11-26 09:23:26 EST
Please bump the loop detection to 250/sec in order to
support PXE boots from thin clients:

Here's the change:

> * Wed Oct 24 2001 Eric Harrison <eharrison@mesd.k12.or.us>
> - LTSP HACK: bumped up loop detection to 250/second: PXE booting
>   can be pretty hard on xinetd.
diff xinetd-7.2/xinetd.sysconf xinetd/xinetd.sysconf
> EXTRAOPTIONS="-loop 250"
Comment 1 Trond Eivind Glomsrxd 2001-11-26 16:33:16 EST
Uh... why? It's a configuration option. It's not impossible to do afterwards,
and if implemented would limit the usefulness of loop detections in the first
place. A special case for use often needs a little configuration.

Comment 2 Jeff Johnson 2001-11-26 16:47:49 EST
Um, please remember I'm just the messanger here.

Because thin clients have different needs, and, particularly in
the case of k12ltsp, removing some of the deeper darker
configuration voo-doo is gonna be neccessary.

Please feel free to suggest a better number than 250 if you wish.
However, understand that the number was arrived at with
Real World PXE booting experience, something we are sorely
lacking in at the moment.
Comment 3 Rob Braun 2001-12-02 20:16:36 EST
The loop detection in 2.3.3 and earlier is clumsy, and duplicates some of the 
functionality in the configuration section.  It's clumsy because the -loop 
option is passed on the command line and can't be overridden in the config 

The current development branch of xinetd removed the -loop option, since the 
per-service 'cps' directive (connections per second) duplicated much of the 
purpose of -loop, but is more configurable.  It still defaults to on, with the 
old compiled defaults, but is at least configurable now.
Comment 4 Trond Eivind Glomsrxd 2001-12-06 12:40:34 EST
The current rawhide version of xinetd is based on that snapshot. Reassigning to
pxe - if there is a desire to change the defaults for that package, it can be done.
Comment 5 Elliot Lee 2002-01-29 17:38:47 EST
Leaving defaults as-is

Note You need to log in before you can comment on or make changes to this bug.