access() doesn't work when a file is open

[pshyamsunder]

Hi:

I am facing a strange problem.

I have opened a file "File1" using fopen() and while processing the
records in the file in a loop, I have a call to access() to check
existence of "File2". The reason is to stop processing further records
when the file "File2" exists. But the access() call fails when the file
"File1" is open.

If I close "File1" before making a call to access() on "File2", then it
works. Why is this behavior?

Please help. And please excuse my C ignorance.

Regds..Shyam

[Suman]

CBFalconer wrote:

Suman wrote:
[...]

Did you check for the error? aceess() on failure should set errno.
See if you can find out something. Guessing won't take us any
further.

[...]
Please do not answer off-topic enquiries, other than to suggest an
appropriate newsgroup. One reason is that there is nobody here (in
principle) to criticize an off-topic reply content. Another is
that it clutters the newsgroup.

It was my own way of saying, do the needful before posting, and also
an attempt to make the OP come back with *some* C code. Being rude
and showing him the door, was a possibility, but I did flirt a little
with rules, I suppose.

`fopen()': I believe is on-topic -- thence the gaul to take
such latitude.

Sometimes, the line is far too thin. For me.

[CBFalconer]

ps**********@ya hoo.com wrote:

access() is an api available on Unix to determine accessibility of a
file. It is on all standard Unix flavors.

I don't think you will go far. I gave you explicit instructions
about how to compose a reply in google groups, and you ignored them
and everything else I told you. This shows either an appalling
inability to learn or insufferable rudeness.

--
"If you want to post a followup via groups.google.c om, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson

[Kenny McCormack]

In article <43************ ***@yahoo.com>,
CBFalconer <cb********@wor ldnet.att.net> wrote:

ps**********@y ahoo.com wrote:

access() is an api available on Unix to determine accessibility of a
file. It is on all standard Unix flavors.

I don't think you will go far. I gave you explicit instructions
about how to compose a reply in google groups, and you ignored them
and everything else I told you. This shows either an appalling
inability to learn or insufferable rudeness.

Or, ...

It shows that he just don't kowtow to you!

(And, why should he?)

[Flash Gordon]

Suman wrote:

CBFalconer wrote:

Suman wrote:
[...]

Did you check for the error? aceess() on failure should set errno. ^^^^^^^^
As far as I can see the above says access() NOT fopen()
See if you can find out something. Guessing won't take us any
further.
[...]
Please do not answer off-topic enquiries, other than to suggest an
appropriate newsgroup. One reason is that there is nobody here (in
principle) to criticize an off-topic reply content. Another is
that it clutters the newsgroup.

It was my own way of saying, do the needful before posting, and also
an attempt to make the OP come back with *some* C code.

When the problem, as in the OPs case, is a function that is OFF TOPIC
getting them to post it here is not appropriate.

If the OP can demonstrate a problem with only standard C functions then
*that* would have been on topic.
Being rude
and showing him the door, was a possibility,
Others redirected the OP moderately politely to other groups. Pointing
the OP at where the
but I did flirt a little
with rules, I suppose.
No, you talked about something completely off topic, namely access().
`fopen()': I believe is on-topic -- thence the gaul to take
such latitude.
The problem was access() failing, NOT fopen() failing, and your answer
was talking purely about access() NOT fopen().
Sometimes, the line is far too thin. For me.

I would have said it was rather obvious that if your answer is just
talking about a function outside the scope of this group, namely the
behaviour of access() in this case, that is was off topic.
--
Flash Gordon
Living in interesting times.
Although my email address says spam, it is real and I read it.

[Kenny McCormack]

In article <hj************ @brenda.flash-gordon.me.uk>,
Flash Gordon <sp**@flash-gordon.me.uk> wrote:
(Blah, blah, blah, the typical verbal venting that passes for Flash's sex
life...)
(leading to...)

Sometimes, the line is far too thin. For me.

I would have said it was rather obvious that if your answer is just
talking about a function outside the scope of this group, namely the
behaviour of access() in this case, that is was off topic.

So, be a man! Do what Americans do! Sue him!

(Don't take being off-topic into your own hands. Take him to court!!!)

See ya in court!

[pete]

Suman wrote:

gaul

ITYM gall

http://www.m-w.com/cgi-bin/dictionar...ionary&va=gall

2 : brazen boldness coupled with impudent assurance and insolence

--
pete

[Suman]

pete wrote:

Suman wrote:

gaul

ITYM gall

Trust me, it was a typoe!