From: ruler@isolate.net
To: linux-c-programming@vger.kernel.org
Subject: Re: multi threaded file access
Date: Fri, 6 Dec 2002 08:38:33 -0500 [thread overview]
Message-ID: <39265468443.20021206083833@isolate.net> (raw)
In-Reply-To: <3DF08C71.30605@tlabs.ac.za>
Hello Heinrich,
Friday, December 6, 2002, 6:39:29 AM, you wrote:
HdT> Hello
HdT> I have a tcp/ip server which is offcourse multi threaded :-)
HdT> Is it safe to have to threads access the same file descriptor at the
HdT> same time?
HdT> Or should I put a mutex over the file descriptor?
HdT> Thanks for your help
HdT> -Heinrich
HdT> -
HdT> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
HdT> the body of a message to majordomo@vger.kernel.org
HdT> More majordomo info at http://vger.kernel.org/majordomo-info.html
Put a mutex over the writing to file descriptor. Depends on how much
and what you are writing, it could makes lines combine with each other
into a bunch of garbled letters.
Thanks,
--
Best regards,
ruler mailto:ruler@isolate.net
prev parent reply other threads:[~2002-12-06 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 11:39 multi threaded file access Heinrich du Toit
2002-12-06 13:38 ` ruler [this message]
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=39265468443.20021206083833@isolate.net \
--to=ruler@isolate.net \
--cc=linux-c-programming@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 NNTP newsgroup(s).