All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Newport <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: booting the T1000
Date: Thu, 29 Jun 2006 21:37:08 +0000	[thread overview]
Message-ID: <44A44804.50001@netunix.com> (raw)
In-Reply-To: <200606290937.49481.rene@exactcode.de>

David S. Miller wrote:

>The default inetd package in Ubuntu, from iputils, is simply buggy,
>because it sets it's sockets to non-blocking and leaves that setting
>on the socket when it passes the connection on to the real application
>from inetd.  Applications expect the socket to be in blocking mode.
>As a result, tftpd craps out because it unexpectedly gets -EAGAIN on a
>read().
>
>To be honest this is a horrible selection of a default inetd
>implementation, netkit-inetd is probably what should be used instead.
>
>  
>
Is this really the root of the issue ?.
For about the last 5 years I have suffered similar issues with tftpd in 
Slackware, Solaris, and NetBSD, all of which use different inetd 
implementations.

Running tftpd standalone has always fixed it.

I could be wrong, but there seem to be generic issues running tftpd via 
inetd, often only intermittently reproduceable. 



  parent reply	other threads:[~2006-06-29 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29  7:37 booting the T1000 Rene Rebe
2006-06-29  9:04 ` David Miller
2006-06-29 11:09 ` Rene Rebe
2006-06-29 20:27 ` Tom 'spot' Callaway
2006-06-29 20:45 ` David S. Miller
2006-06-29 21:03 ` Tom 'spot' Callaway
2006-06-29 21:37 ` Chris Newport [this message]
2006-06-29 21:42 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44A44804.50001@netunix.com \
    --to=crn@netunix.com \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.