linux-gcc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefanos Koutsoutos <koutsoutos@md5sa.com>
To: linux-gcc@vger.kernel.org
Subject: stat() problems.
Date: 01 Aug 2002 10:56:01 +0300	[thread overview]
Message-ID: <1028188562.1091.4.camel@skt.int.local> (raw)

Hi,

I'm facing problems with stat() system call. It seems that it follows
filesystem links! To be more accurate I try:

struct stat buf;
stat("this_is_a_link", &buf);

and then:	S_ISLNK( buf.st_mode )  is false!

More, the mode is the same as the mode of the file it links to! I think
that this is not what it supposed to be done by stat(). Any ideas??

Thanks in advance.
Stefanos.

-- 
____________________
Stefanos Koutsoutos
Developer
MD5 S.A.
koutsoutos@md5sa.com
www.md5sa.com


             reply	other threads:[~2002-08-01  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-01  7:56 Stefanos Koutsoutos [this message]
2002-08-01 11:48 ` stat() problems Alexandre P. Nunes
2002-08-01 12:05   ` Stefanos Koutsoutos
2002-08-28 20:50   ` C Language Reference for @ and : Nate
2002-08-28 22:16     ` Stephen Satchell
2003-01-15 20:00       ` Stack and Heap Nate

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=1028188562.1091.4.camel@skt.int.local \
    --to=koutsoutos@md5sa.com \
    --cc=linux-gcc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).