mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: vamsi krishna <vamsi.krishnak@gmail.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Quick close of all the open files.
Date: Wed, 07 Jun 2006 10:50:23 +0200	[thread overview]
Message-ID: <1149670223.23078.5.camel@tara.firmix.at> (raw)
In-Reply-To: <3faf05680606061822g25c242ddq58efdb762ca33252@mail.gmail.com>

On Wed, 2006-06-07 at 06:52 +0530, vamsi krishna wrote:
[...]
> > > I checked as follows I did printf("lowest fd = %d",fileno(tmpfile()));
> > > it prints 3
>
> > Which proves that file descriptor 3 was closed, so tmpfile() was able to
> > open it.  This certainly implies that fd 0, 1, 2 (connected to stdin,
> > stdout, and stderr streams of stdio) are still open, contrary to your
> > statement that *all* of them are closed.

And it specifically says absolutely nothing about the file descriptors 4
and larger since open(2) always uses the lowest unused file descriptor.

> I know 0,1,2 are open (I opened it) no need to tell it specifically,
> HOW DO YOU THINK I CAN PRINT SOME THING WITHOUT OPENING THIS
> FILES(stdout,stderr)?

No reason to shout: The trivial solution is to syslog(3) the output like
all of the daemons out there do since ages.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


  parent reply	other threads:[~2006-06-07  8:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 21:45 vamsi krishna
2006-06-06 21:56 ` Valdis.Kletnieks
2006-06-06 22:02   ` vamsi krishna
2006-06-06 22:39     ` Måns Rullgård
2006-06-07  0:33     ` Valdis.Kletnieks
2006-06-07  1:22       ` vamsi krishna
2006-06-07  7:57         ` Måns Rullgård
2006-06-07  8:50         ` Bernd Petrovitsch [this message]
2006-06-07  7:56       ` Måns Rullgård
2006-06-06 22:03   ` Måns Rullgård
2006-06-07 11:12 ` linux-os (Dick Johnson)

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=1149670223.23078.5.camel@tara.firmix.at \
    --to=bernd@firmix.at \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vamsi.krishnak@gmail.com \
    /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

all inboxes | Powered by JetHome®