From: "J . A . Magallon" <jamagallon@able.es>
To: mathieu_dube@videotron.ca
Cc: linux-kernel@vger.kernel.org, davids@webmaster.com
Subject: RE: accept
Date: Sun, 4 Feb 2001 21:27:22 +0100 [thread overview]
Message-ID: <20010204212722.A1029@werewolf.able.es> (raw)
In-Reply-To: <NCBBLIEPOCNJOAEKBEAKGEICNHAA.davids@webmaster.com> <01020411401700.00110@grndctrl>
In-Reply-To: <01020411401700.00110@grndctrl>; from mathieu_dube@videotron.ca on Sun, Feb 04, 2001 at 17:37:43 +0100
On 02.04 Mathieu Dube wrote:
> Ok, but fd 0 cant be a valid socket since its the stdin
>
> I posted that on this mailing list coz I thought that this might be a scaling
> problem since it happens when theres already several clients connected to the
> server
>
It just mean that your stdin was closed some time in the past...
As the prog is a daemon, probably it closed its std{in,out,err} and its
controlling tty.
I do not know if Linux follows the rule that the first fd you get is the
first available. That means that after 'daemonize' you should get the 0
in the first connection. If fd reuse is delayed, you can get the 0 any time
after...
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.4.2-pre1 #1 SMP Sun Feb 4 13:04:30 CET 2001 i686
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 0:42 accept Mathieu Dube
2001-02-04 11:01 ` accept David Schwartz
2001-02-04 16:37 ` accept Mathieu Dube
2001-02-04 20:27 ` J . A . Magallon [this message]
2001-02-05 0:14 ` accept David Schwartz
2001-02-05 12:59 ` accept Richard B. Johnson
[not found] <200102040044.f140i7a473095@saturn.cs.uml.edu>
2001-02-04 16:40 ` accept Mathieu Dube
-- strict thread matches above, loose matches on Subject: below --
2001-02-04 18:00 accept W1012
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=20010204212722.A1029@werewolf.able.es \
--to=jamagallon@able.es \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu_dube@videotron.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox